Deepesh Varatharajan 7a98334a8d clang: Upgrade to 21.1.2 release
Brings following bugfixes on top of 21.1.1

b708aea0bc71 [SCEV] Don't perform implication checks with many predicates (#158652)
77a3b0eda361 [RISCV] Refactor RVV builtin code generation for reduce compilation time [NFC] (#154906)
f14551dbc4e8 [RISCV] Reduce ManualCodeGen for RVV intrinsics with rounding mode. NFC
dcc2c1c933be [RISCV] Reduce ManualCodeGen for segment load/store intrinsics. NFC
e625a781211e [LLVM] Update CUDA ELF flags for their new ABI (#149534)
3e93017936b5 MC: Better handle backslash-escaped symbols (#158780)
bc5e9a5e2009 [MC] Add parseSymbol() helper (NFC) (#158106)
e2e5eb2f1cd9 [Loads] Check for overflow when adding MaxPtrDiff + Offset.
661c387fc2f1 release/21.x: [VPlan] Don't narrow op multiple times in narrowInterleaveGroups.
f5c1b5206cbe [PowerPC] Avoid working on deleted node in ext bool trunc combine (#160050)
db70369f400e [Clang] Fix an error-recovery crash after d1a80dea (#159976)
9c8736f348e0 [ELF] -r/--emit-relocs: Fix crash when processing .rela.text before .text (#156354)
15a31832eab7 [RISCV] Re-work how VWADD_W_VL and similar _W_VL nodes are handled in combineOp_VLToVWOp_VL. (#159205)
f089fb21fffa [LoongArch] Fix MergeBaseOffset for constant pool index operand (#159336)
9eedaf5b1001 [VectorCombine] Fix scalarizeExtExtract for big-endian (#157962)
5af5cfb60d9e [clang-format] Handle C digit separators (#158418)
0174263ac214 Bump version to 21.1.2
ff039a98523f [RISCV] Support PreserveMost calling convention (#148214)
1a644bc50948 [X86] Fix assertion in AVX512 setcc combine due to invalid APInt mask width (#155775)
2c8cb316b5d2 [lldb][test] Only assert function name is in user-code on Darwin platforms
f5ba88341e7c [lldb][test] TestTsanBasic.py: fix function name assertion
faedeb1a2420 [lldb][Instrumentation] Set selected frame to outside sanitizer libraries (#133079)
54896838ca5e [lldb][Target] Clear selected frame index after a StopInfo::PerformAction (#133078)
f4907049285c [Clang][Cygwin] Use correct mangling rule (#158404)

(From OE-Core rev: bf15536de8fe99849eef0696455b5679b0f7a9d5)

Signed-off-by: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2025-10-06 23:15:59 +01:00
2025-10-06 23:15:59 +01:00
2024-02-19 11:34:33 +00:00
2021-07-19 18:07:21 +01:00

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/):

BitBake (files in bitbake/):

Documentation (files in documentation/):

meta-yocto (files in meta-poky/, meta-yocto-bsp/):

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.

CII Best Practices

Description
No description provided
Readme 249 MiB