ac5f388cc8
Brings following fixes * 87f0227cb601 [InstCombine] Avoid folding `select(umin(X, Y), X)` with min/max values in false arm (#143020) * df43f93388b7 [PhaseOrdering] Add test for #139050 (NFC) * 25bcf1145fd7 [RISCV] Fix assertion failure when using -fstack-clash-protection (#135248) * 6fb913d3e2ec [RelLookupTableConverter] Drop unnamed_addr for GVs in entries to avoid generating GOTPCREL relocations (#146068) * 0c9f909b7976 [AArch64][SME] Fix restoring callee-saves from FP with hazard padding (#143371) * fa792cd4c630 [AsmPrinter] Always emit global equivalents if there is non-global uses (#145648) * ce455b382c08 [objcopy][MachO] Revert special handling of encryptable binaries (#144058) * 0de59a293f7a [X86] Ignore NSW when DstSVT is i32 (#131755) * 9af763f038f7 [gtest] Fix building on OpenBSD/sparc64 (#145225) * 1daceb20611f [LoongArch] Pass OptLevel to LoongArchDAGToDAGISel correctly * b21155f97a0a [LoongArch] Precommit test case to show bug in LoongArchISelDagToDag * da18fb9f04ce [LoongArch] Fix xvshuf instructions lowering (#145868) * 65ce78f338cf [LoongArch] Pre-commit test for fixing xvshuf instructions. NFC * 5532d5b745e4 [AArch64] Ensure the LR is preserved if we must call __arm_get_current_vg (#145760) * 5ac3ce819688 [WebAssembly] Fix inline assembly with vector types (#146574) * b83658b7e2c8 Bump version to 20.1.8 (From OE-Core rev: 4c6e132d6e5e49426c911d0fa9215957eb43f186) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@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.