aa83bdc439
Below commits on glibc-2.35 development branch are updated. glibc: 0e5b239f45 malloc: Simplify implementation of __malloc_assert dc2d843045 Update syscall-names.list for Linux 5.18 d56c7e0965 Apply asm redirections in stdio.h before first use [BZ #27087] c4050b2552 x86: Add missing IS_IN (libc) check to strncmp-sse4_2.S fdf699edea x86: Move mem{p}{mov|cpy}_{chk_}erms to its own file de6f7bb873 x86: Move and slightly improve memset_erms 210e9728ff x86: Add definition for __wmemset_chk AVX2 RTM in ifunc impl list c77cde8172 x86: Put wcs{n}len-sse4.1 in the sse4.1 text section 3eb17048c4 x86: Align entry for memrchr to 64-bytes. dd3b6857ee x86: Add BMI1/BMI2 checks for ISA_V3 check ce32ad91eb x86: Cleanup bounds checking in large memcpy case 863987a6ef x86: Add bounds `x86_non_temporal_threshold` 232b7adb14 x86: Add sse42 implementation to strcmp's ifunc 7f7a728b71 x86: Fix misordered logic for setting `rep_movsb_stop_threshold` 6b4a2ab7e0 x86: Align varshift table to 32-bytes e74385736c x86: ZERO_UPPER_VEC_REGISTERS_RETURN_XTEST expect no transactions b4744d4414 x86: Shrink code size of memchr-evex.S 5321a217cf x86: Shrink code size of memchr-avx2.S c536b318f0 x86: Optimize memrchr-avx2.S f8ba0e0452 x86: Optimize memrchr-evex.S 7001d558a0 x86: Optimize memrchr-sse2.S 54486f520a x86: Add COND_VZEROUPPER that can replace vzeroupper if no `ret` 82560fe43e x86: Create header for VEC classes in x86 strings library b1f23b6128 x86_64: Add strstr function with 512-bit EVEX f9f0fbbf7b x86-64: Ignore r_addend for R_X86_64_GLOB_DAT/R_X86_64_JUMP_SLOT 650bf51c78 x86_64: Implement evex512 version of strlen, strnlen, wcslen and wcsnlen e0cb101d1b x86_64: Remove bzero optimization 51e2d3b53b nptl: Fix ___pthread_unregister_cancel_restore asynchronous restore cd4f43be3d linux: Fix mq_timereceive check for 32 bit fallback code (BZ 29304) (From OE-Core rev: 7d70ccb320459faf356b51d38e62c5dc3955393b) Signed-off-by: Sundeep KOKKONDA <sundeep.kokkonda@gmail.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
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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.