91359fd407
Brings following changes/fixes * 309d55140c46 [AArch64][GlobalISel] Fix incorrect ABI when tail call not supported (#70215) * 9477268e4247 [AArch64] Add test for #70207 (NFC) * c2eab59e622c [GVN] Fix use-after-free in load PRE with select available value (#69314) * 586481468a07 [clang-tidy] Fix crash in modernize-use-trailing-return-type (#70709) * 9d0ca259eed6 [OpenMP] Fix building for 32-bit DragonFly, NetBSD, OpenBSD (#70527) * a8046f72bfb3 [OpenMP] record-replay use static-cast (#70516) * 12bbcd627f60 [flang] Add comdats to functions with linkonce linkage (#66516) * bdb1553c7639 [mlir] Add pass to add comdat to all linkonce functions (#65270) * 3347c8441588 Update release note for the fix * f6fb6a996c7f [clang][ExprConst] Fix crash on uninitialized array subobject (#67817) * 8c8abe6b93c0 [RISCV] Correct copyPhysReg for GPRPF64. (#70419) * 615beaec04f9 [SVE] Fix incorrect offset calculation when rewriting an instruction's frame index. (#70315) * bb29e1ead22f [MemCpyOpt] Combine alias metadatas when replacing byval arguments (#70580) * 2b82ec7947fe [OpenMP] Use the more appropriate function to retrieve the thread id on OpenBSD (#65553) * 8909a24d0af1 [libc++] Encode additional ODR-affecting properties in the ABI tag (#69669) * e9dcc15f514a [AArch64] Prevent argument promotion of vector with size > 128 bits (#70034) * 4b7f4152a8d1 [LoongArch] Implement COPY instruction between CFRs (#69300) * fb62a201a199 Revert "[clang-format] Fix align consecutive declarations over function pointers" * 1f6d35b36681 Fix tests for c23 <-> c2x * 030d68ef2cd7 Fix a c23 -> c2x think-o * 2a41d978b4fa [C23] Use thread_local semantics (#70107) * afbe3549af4d [clangd] Disable crashy unchecked-optional-access tidy check (#69427) * 7f790f9a39e3 [ConstraintElim] Don't decompose values wider than 64 bits (#68803) * a1c67ffd0a1f [ConstraintElim] Add test for #68751 (NFC) * ef50a367e3d5 [mlir] Avoid including <alloca.h> on DragonFly * a7101379d75e [LVI][CVP] Treat undef like a full range on abs(x, false) (#68711) * aa03fba83b17 [libcxx] [test] Add a test parameter for disabling memory intensive tests (#68214) * 71f408bc3623 workflows/release-tasks: Fix release note artifact upload (#69522) * 9ab3ce1d7a06 Bump version to 17.0.4 * 880a282a40e3 workflows/release-lit: Pass correct build directory to pypa/gh-action-pypi-publish (#69438) * 8719ee0cb39a workflows/release-lit: Fix dev suffix removal (#69397) (From OE-Core rev: 198f10d12eea50942acb60cdf8c7bc0700065df1) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.