profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/kraj/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

agherzan/meta-raspberrypi 309

Yocto BSP layer for the Raspberry Pi boards

Comcast/rdk-on-raspberrypi 14

Documentation for running RDK profiles ( Video, broadband, Camera ) on Raspberrypi boards

cbrake/oe-build 8

OpenEmbedded build template using oe-core, meta-oe, etc

Comcast/portabledsb 5

A portable c++ version of the AllJoyn Device System Bridge

kraj/binutils-gdb 2

gdb and binutils

cbrake/meta-bec 1

BEC Systems layer for OpenEmbedded recipes

Comcast/WebKitForWayland 1

Unofficial mirror of the WebKit SVN repository

kraj/buildroot 1

Buildroot, making embedded Linux easy. Note that this is not the official repository, but only a mirror. The official Git repository is at http://git.buildroot.net/buildroot/. Do not open issues or file pull requests here.

koansoftware/meta-ada 0

Meta layer for Yocto which adds support for Ada.

push eventkraj/aports

Andy Postnikov

commit sha 97d42346e5f4baf495affdfcbd934bcffcc0b6f0

community/nodejs-current: upgrade to 16.10.0

view details

Bart Ribbers

commit sha 895a0019128162dc9c09da63ec5f053d344be8d9

testing/plank-player: new aport

view details

push time in 2 hours

push eventkraj/llvm-project

Albion Fung

commit sha 840afbde48e90213028174fdba715e10aa39dd85

[PowerPC] SemaChecking for darn family of builtins The __darn family of builtins are only available on Pwr9, and only __darn_32 is available on both 64 and 32 bit, while the rest are only available on 64 bit. The patch adds sema checking for these builtins and separate the __darn_32's 32 bit test cases. Differential revision: https://reviews.llvm.org/D110282

view details

Lang Hames

commit sha 0820fbab99a1f1986a8c6e0a8e5cb4542ec52515

[ORC-RT] Rename ExecutorAddress to ExecutorAddr. This is an ORC-runtime counterpart to LLVM commit ef391df2b63, and the motivation is the same: to move to a shorter name to improve the ergonomics of this type before it's more widely adopted.

view details

Amara Emerson

commit sha 661ab70314008b609dda792e2c9dc57afa1f8864

[AArch64][GlobalISel] Fix crash in the extend(extract_vector_elt) optimization. It was assuming that GPR extends could only have destination sizes of 32 or 64 bits, but for AArch64 we allow < 32 bits even without matching size physregs.

view details

mydeveloperday

commit sha 7890afddecff01119f4d5e8825b43dd2c8361648

[clang-offload-bundler][docs][NFC] invalid indentation cause build issue

view details

Pavel Labath

commit sha cd6893a5a346d1b9c34ba621adad5f881e250695

[lldb] Fix target-symbols-add-unwind.test for clang 7647a841 We need a different flag combination to produce .debug_frame.

view details

mydeveloperday

commit sha 87ab958641fa30ed1e5880aaf43b909c552af0dc

[clang-format] ensure clang-format command-line argument sets up the default left/right qualifier ordering When specifying the alignment direction on the command line ensure we set up the default ordering. Fix spelling mistakes in the command-line argument Reviewed By: HazardyKnusperkeks Differential Revision: https://reviews.llvm.org/D110359

view details

Ludovic Jozeau

commit sha 9e8fff26f374766b76aad9531ee5e6860f67e46c

[clang-format][docs] Fix documentation of clang-format BasedOnStyle type Fix little inconsistency and use `std::string` (which is used everywhere else) instead of `string` Reviewed By: MyDeveloperDay, HazardyKnusperkeks Differential Revision: https://reviews.llvm.org/D108765

view details

Amara Emerson

commit sha 9f773b17c2bc6916f12048a52ae271d1bf0edacf

[GlobalISel][IRTranslator] Fix crash during bit-test switch optimization with odd types. Odd switch case types cause a crash in the conversion to MVT. Instead use a pointer sized scalar type which is what SDAG does in these cases.

view details

push time in 2 hours

push eventkraj/gcc

Aldy Hernandez

commit sha 4a960d548b7d7d942f316c5295f6d849b74214f5

Avoid invalid loop transformations in jump threading registry. My upcoming improvements to the forward jump threader make it thread more aggressively. In investigating some "regressions", I noticed that it has always allowed threading through empty latches and across loop boundaries. As we have discussed recently, this should be avoided until after loop optimizations have run their course. Note that this wasn't much of a problem before because DOM/VRP couldn't find these opportunities, but with a smarter solver, we trip over them more easily. Because the forward threader doesn't have an independent localized cost model like the new threader (profitable_path_p), it is difficult to catch these things at discovery. However, we can catch them at registration time, with the added benefit that all the threaders (forward and backward) can share the handcuffs. This patch is an adaptation of what we do in the backward threader, but it is not meant to catch everything we do there, as some of the restrictions there are due to limitations of the different block copiers (for example, the generic copier does not re-use existing threading paths). We could ideally remove the now redundant bits in profitable_path_p, but I would prefer not to for two reasons. First, the backward threader uses profitable_path_p as it discovers paths to avoid discovering paths in unprofitable directions. Second, I would like to merge all the forward cost restrictions into the profitability class in the backward threader, not the other way around. Alas, that reshuffling will have to wait for the next release. As usual, there are quite a few tests that needed adjustments. It seems we were quite happily threading improper scenarios. With most of them, as can be seen in pr77445-2.c, we're merely shifting the threading to after loop optimizations. Tested on x86-64 Linux. gcc/ChangeLog: * tree-ssa-threadupdate.c (jt_path_registry::cancel_invalid_paths): New. (jt_path_registry::register_jump_thread): Call cancel_invalid_paths. * tree-ssa-threadupdate.h (class jt_path_registry): Add cancel_invalid_paths. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/20030714-2.c: Adjust. * gcc.dg/tree-ssa/pr66752-3.c: Adjust. * gcc.dg/tree-ssa/pr77445-2.c: Adjust. * gcc.dg/tree-ssa/ssa-dom-thread-18.c: Adjust. * gcc.dg/tree-ssa/ssa-dom-thread-7.c: Adjust. * gcc.dg/vect/bb-slp-16.c: Adjust.

view details

push time in 3 hours

push eventkraj/gcc

Aldy Hernandez

commit sha 4a960d548b7d7d942f316c5295f6d849b74214f5

Avoid invalid loop transformations in jump threading registry. My upcoming improvements to the forward jump threader make it thread more aggressively. In investigating some "regressions", I noticed that it has always allowed threading through empty latches and across loop boundaries. As we have discussed recently, this should be avoided until after loop optimizations have run their course. Note that this wasn't much of a problem before because DOM/VRP couldn't find these opportunities, but with a smarter solver, we trip over them more easily. Because the forward threader doesn't have an independent localized cost model like the new threader (profitable_path_p), it is difficult to catch these things at discovery. However, we can catch them at registration time, with the added benefit that all the threaders (forward and backward) can share the handcuffs. This patch is an adaptation of what we do in the backward threader, but it is not meant to catch everything we do there, as some of the restrictions there are due to limitations of the different block copiers (for example, the generic copier does not re-use existing threading paths). We could ideally remove the now redundant bits in profitable_path_p, but I would prefer not to for two reasons. First, the backward threader uses profitable_path_p as it discovers paths to avoid discovering paths in unprofitable directions. Second, I would like to merge all the forward cost restrictions into the profitability class in the backward threader, not the other way around. Alas, that reshuffling will have to wait for the next release. As usual, there are quite a few tests that needed adjustments. It seems we were quite happily threading improper scenarios. With most of them, as can be seen in pr77445-2.c, we're merely shifting the threading to after loop optimizations. Tested on x86-64 Linux. gcc/ChangeLog: * tree-ssa-threadupdate.c (jt_path_registry::cancel_invalid_paths): New. (jt_path_registry::register_jump_thread): Call cancel_invalid_paths. * tree-ssa-threadupdate.h (class jt_path_registry): Add cancel_invalid_paths. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/20030714-2.c: Adjust. * gcc.dg/tree-ssa/pr66752-3.c: Adjust. * gcc.dg/tree-ssa/pr77445-2.c: Adjust. * gcc.dg/tree-ssa/ssa-dom-thread-18.c: Adjust. * gcc.dg/tree-ssa/ssa-dom-thread-7.c: Adjust. * gcc.dg/vect/bb-slp-16.c: Adjust.

view details

push time in 3 hours

PR opened YoeDistro/yoe-distro

update layers
+7 -3

0 comment

3 changed files

pr created time in 4 hours

push eventYoeDistro/yoe-distro

Khem Raj

commit sha 86e1048f88d7870491f20f5771d5d58ad1d50e34

Layer Updates: sources/bitbake sources/openembedded-core * sources/bitbake 36f6dce1...032190aa (3): > build: Fix log flushing race > build: Make exception printing clearer > build: Ensure python stdout/stderr is logged correctly * sources/openembedded-core add36cf853...907ebb5bb3 (17): > lttng-ust: fix do_compile error when PACKAGECONFIG examples is enabled > oeqa/selftest: Add tests for bitbake shell/python task output > ssate: Cleanup directtasks handling > sstate: Avoid deploy_source_date_epoch sstate when unneeded > sstate: Ensure deploy tasks don't pull in toolchains > staging: Mark deploy an sstate task > meta: Drop useless class > buildtools-tarball/uninative-tarball/meta-ide-support: Drop useless meta class > populate_sdk_base/images: Drop use of 'meta' class and hence do_build dependencies > reproducible_build/package_XXX: Ensure SDE task is in dependency chain > package_ipk/deb/rpm: Drop recursive do_build task dependencies > siteinfo/autotools: Ensure task checksums reflect site files > image/qemu: Add explict depends for qemu-helper addto_recipe_sysroot task > site: Drop ORBit2 relared cached variables > site: Drop caching libIDL_cv_long_long_format > connman: add CVE_PRODUCT > scripts/oe-publish-sdk: Disable git gc to avoid build errors Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 49cc0b87d23b4a55be625d88de8cb52e4cd7cfd9

CHANGELOG.md: Document current changes Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 4 hours

PullRequestReviewEvent

push eventYoeDistro/meta-openembedded

Khem Raj

commit sha 1d51730759ae02eeba58ec601ab87cbadb49bc10

rdma-core: Inherit pkgconfig fixes CMake Error at /home/pokybuild/yocto-worker/meta-oe/build/build/tmp/work/core2-64-poky-linux/rdma-core/36.0-r0/recipe-sysroot-native/usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message): | Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 132dab0f2045505880e92e4119a7e20f515e876a

postfix: Add missing dependency on m4 Fixes | extract_cfg.sh: line 42: m4: command not found Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Sakib Sajal

commit sha e7a52e51c7ad1a9e04cf8b882e5380af36d9c988

lmdb: replace tag with commit id in SRCREV Using tag in SRCREV does not work when the git source is added to the PREMIRRORS and set BB_NO_NETWORK = "1". This is because there is no SRCREV, and bitbake needs check the original url to get it. Signed-off-by: Sakib Sajal <sakib.sajal@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Trevor Woerner

commit sha 0b86f2c189fe19fe66dcf113fe15cfbf9d5cda64

vk-gl-cts: allow the user to specify the target When building opengl-es-cts (for example), instead of hard-coding a specific target to build (surfaceless), leave the choice empty by default which instructs the package's build system to search the sysroot and try to determine which target to use (i.e. the "Default" target). Provide overrides (in the form of PACAKGECONFIGs) to allow the user to specify a specific target to build (if they don't want the target selected automatically). Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Trevor Woerner

commit sha a1f60d42898abe5a0ff2e2a9c9c1095d09d0cdc3

vk-gl-cts: fix soname linking The code/build explicitly links to the GL library names instead of their sonames. Update the names that are used for linking so the libraries are found at runtime. Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Bruce Ashfield

commit sha 8618e8a99c16b18d1dcf367e0218eb6c173df7ee

vboxguestdrivers: fix build against 5.14+ The bump of the reference / default kernels and libc-headers to 5.14 in oe-core broke the build of the vbox guest drivers. The upstream SVN already has 5.14 fixes for the issues, so these are SVN exports of the changes. When a new release is available, we can drop the changes. Also in this patch, is a fixup for the source directory for patching. It was broken in the overrides conversion, and since there weren't any active patches at the time, we didn't notice that source wasn't set to a directory where quilt could actually find the files. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 5 hours

push eventYoeDistro/yoe-distro

Khem Raj

commit sha e46c384068445e9f16bf49ee1a6a451f8497864c

Layer Updates: sources/meta-openembedded * sources/meta-openembedded 0be3621c8...77c271b84 (3): > XXX: Add Github actions CI support > vboxguestdrivers: fix build against 5.14+ < XXX: Add Github actions CI support Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 5 hours

push eventYoeDistro/meta-openembedded

Bruce Ashfield

commit sha 8618e8a99c16b18d1dcf367e0218eb6c173df7ee

vboxguestdrivers: fix build against 5.14+ The bump of the reference / default kernels and libc-headers to 5.14 in oe-core broke the build of the vbox guest drivers. The upstream SVN already has 5.14 fixes for the issues, so these are SVN exports of the changes. When a new release is available, we can drop the changes. Also in this patch, is a fixup for the source directory for patching. It was broken in the overrides conversion, and since there weren't any active patches at the time, we didn't notice that source wasn't set to a directory where quilt could actually find the files. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 77c271b844e0cb41464a78c646632a5dc871cb9a

XXX: Add Github actions CI support Add drone build Badge Add yoe.yml for Github actions CI support Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 5 hours

push eventkraj/void-packages

Andrew Benson

commit sha a374a28fd9c605bd4b8aa99b6d53a6a0004db9e0

wavemon: broken, weirdness with curses.h inclusion

view details

Andrew Benson

commit sha b1db5bf6d036610ed73e112af615a879f8474e90

nvidia: update to 470.74.

view details

push time in 5 hours

push eventkraj/aports

Andy Postnikov

commit sha a36435e9cb53c56aed31ffc7548a3a8819c9e31d

community/libcouchbase: upgrade to 3.2.2

view details

push time in 5 hours

push eventkraj/ltp

Zhao Gongyi

commit sha 50dcc734b2b518fb9b4956ee2a6d99a761d5f526

open_posix: Add failure handling of fork() When fork() failed and transfer the return value(-1) to kill(), it would freeze the system, so it is very serious in this cases and should be avoided. Signed-off-by: Zhao Gongyi <zhaogongyi@huawei.com> Reviewed-by: Li Wang <liwang@redhat.com>

view details

Jan Stancek

commit sha 443cbc1039f5348ffb8414eec6e7fcd55a69e235

hugeshmat04: try to find unmapped range for test The test intermittently fails on ppc64le, when heap happens to overlap with segment that the test is trying to attach at 1GB boundary. Try to find unmapped range. In my testing, address above 1GB appears to be needed for reproducer to work. Also add kernel commit that fixed it to metadata. Signed-off-by: Jan Stancek <jstancek@redhat.com> Reviewed-by: Li Wang <liwang@redhat.com> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>

view details

push time in 5 hours

push eventkraj/llvm-project

Matthias Springer

commit sha 2190f8a8b1e01b7bc7429eb490f3001a23f27df1

[mlir][linalg] Support tile+peel with TiledLoopOp Only scf.for was supported until now. Differential Revision: https://reviews.llvm.org/D110220

view details

Mehdi Amini

commit sha 83f3c615dde3fce5c0560c19316b08c1e6aa8c27

Add missing storageType to AttrDef to ODS This is only noticeable when using an attribute across dialects I think. Previously the namespace would be ommited, but it wouldn't matter as long as the generated code stays within a single namespace. Differential Revision: https://reviews.llvm.org/D110367

view details

Michael Kruse

commit sha e470f9268a448fedea25289ec343f82ff52ccc36

[Polly] Implement user-directed loop distribution/fission. This is a simple version without the possibility to define distribute points or followup-transformations. However, it is the first transformation that has to check whether the transformation is correct. It interprets the same metadata as the LoopDistribute pass. Re-apply after revert in c7bcd72a38bcf99e03e4651ed5204d1a1f2bf695 with fix: Take isBand out of #ifndef NDEBUG since it now is used unconditionally.

view details

Fangrui Song

commit sha afab3c488f0c86af87e262cc7454e04de18e3e6a

[Driver] Default Generic_GCC x86 to -fasynchronous-unwind-tables to match GCC and Clang's own x86-64.

view details

Christudasan Devadasan

commit sha 7a62a5b56d670c4e152159740cd7fc4030a9470f

[AMDGPU] Legalize initialized LDS variables We don't allow an initializer for LDS variables and there is an early abort during instruction selection. This patch legalizes them by ignoring the init values. During assembly emission, proper error reporting already exists for such instances. Reviewed By: arsenm Differential Revision: https://reviews.llvm.org/D109901

view details

David Blaikie

commit sha 25ac0d3c73d68c017546eb622ba7632c6b581bfb

DebugInfo: Implement the -gsimple-template-names functionality This excludes certain names that can't be rebuilt from the available DWARF: * Atomic types - no DWARF differentiating int from atomic int. * Vector types - enough DWARF (an attribute on the array type) to do this, but I haven't written the extra code to add the attributes required for this * Lambdas - ambiguous with any other unnamed class * Unnamed classes/enums - would need column info for the type in addition to file/line number * noexcept function types - not encoded in DWARF

view details

Lang Hames

commit sha a2c1cf09dfaaa6d2161fee00f8317005bf955d64

[ORC] Introduce EPCGenericDylibManager / SimpleExecutorDylibManager. EPCGenericDylibManager provides an interface for loading dylibs and looking up symbols in the executor, implemented using EPC-calls to functions in the executor. SimpleExecutorDylibManager is an executor-side service that provides the functions used by EPCGenericDylibManager. SimpleRemoteEPC is updated to use an EPCGenericDylibManager instance to implement the ExecutorProcessControl loadDylib and lookup methods. In a future commit these methods will be removed, and clients updated to use EPCGenericDylibManagers directly.

view details

LLVM GN Syncbot

commit sha 58d9ed2c935d6665da388cd72273360349792281

[gn build] Port a2c1cf09dfaa

view details

Christudasan Devadasan

commit sha 40ddde5d1fa7e5eadb76f6c3cc37dae2f80a8ca2

[TableGen] Allow targets to entirely ignore Psets for registers Tablegen currently expects targets to have at least one pressure set for every broader register category. AMDGPU's VGPR or AGPR, for instance, seemed to work correctly without any pset, though we have forced one for each type to avoid the assertion in computeRegUnitSets. However, psets can not be entirely empty. At least one set is mandatory for every target. This patch bypasses the assertion for the classes when GeneratePressureSet is zero while ensuring the RegUnitSets are not empty. Reviewed By: arsenm, rampitec Differential Revision: https://reviews.llvm.org/D110305

view details

David Carlier

commit sha 3675e147a1ccbce44ce64a1bc8dd38547aba1443

[Sanitizers] intercept ttyent api on FreeBSD. and ttyentpath separately on NetBSD. Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D109843

view details

Frederic Cambus

commit sha 4ed05312a1557b2f2552298a3aac12c2e224d77e

[docs] Document the --print-passes flag in opt. Reviewed By: aeubanks, asbirlea Differential Revision: https://reviews.llvm.org/D109663

view details

Lang Hames

commit sha ef391df2b63320c9aec61045d8b96917081f0cb2

[ORC] Rename ExecutorAddress to ExecutorAddr. Removing the 'ess' suffix improves the ergonomics without sacrificing clarity. Since this class is likely to be used more frequently in the future it's worth some short term pain to fix this now.

view details

David Blaikie

commit sha e70082e9add7e82e580148fbd4c0a5a832763cb6

Remove non-portable directory separator from test

view details

David Blaikie

commit sha 8d9ddd4f509c54d05a38427d7999c061d88ca35c

DebugInfo: STN: Handle unreconstitutable types in function types

view details

David Blaikie

commit sha 165926aa4ce9f05572cf8828210a1af5ce286bdb

Fix that same path separator issue again...

view details

push time in 5 hours

push eventkraj/llvm-project

David Carlier

commit sha 3675e147a1ccbce44ce64a1bc8dd38547aba1443

[Sanitizers] intercept ttyent api on FreeBSD. and ttyentpath separately on NetBSD. Reviewed By: vitalybuka Differential Revision: https://reviews.llvm.org/D109843

view details

Frederic Cambus

commit sha 4ed05312a1557b2f2552298a3aac12c2e224d77e

[docs] Document the --print-passes flag in opt. Reviewed By: aeubanks, asbirlea Differential Revision: https://reviews.llvm.org/D109663

view details

Lang Hames

commit sha ef391df2b63320c9aec61045d8b96917081f0cb2

[ORC] Rename ExecutorAddress to ExecutorAddr. Removing the 'ess' suffix improves the ergonomics without sacrificing clarity. Since this class is likely to be used more frequently in the future it's worth some short term pain to fix this now.

view details

David Blaikie

commit sha e70082e9add7e82e580148fbd4c0a5a832763cb6

Remove non-portable directory separator from test

view details

Khem Raj

commit sha 6cf733dc9f00c0c5e02ff011ab7e1fa8817f704e

lldb: Add -lxml2 to linker cmdline of xml is found When cross compiling for systems where static libs for libxml are not available cmake's detection mechanism resort to linking with libxml.so but doesnt use -lxml2 liblldbHost.a however requires libxml on linker cmdline _after_ itself so its use of symbols from libxml2 can be resolved. Here check for libxml2 being detected and add it if its found. Fixes | ../../../../lib/liblldbHost.a(XML.cpp.o): In function `lldb_private::XMLDocument::Clear()': | /usr/src/debug/lldb/5.0.0+gitAUTOINC+69edad7913_08d6b47db9_cf6c5b3386-r0/git/tools/lldb/source/Host/common/XML.cpp:29: undefined reference to `xmlFreeDoc' | /usr/src/debug/lldb/5.0.0+gitAUTOINC+69edad7913_08d6b47db9_cf6c5b3386-r0/git/tools/lldb/source/Host/common/XML.cpp:29: undefined reference to `xmlFreeDoc' Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha a0d27a1fe13a0f0fa2a598272a8974fc7f9c9b87

libcxxabi: Find libunwind headers when LIBCXXABI_LIBUNWIND_INCLUDES is set Currently, when LIBCXXABI_LIBUNWIND_INCLUDES is set via CMake arguments then it ends up not searching the specified dir and unwind.h is not found especially for ARM targets This patch makes the searching synthesized directories and then set LIBCXXABI_LIBUNWIND_INCLUDES if its there in environment Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 29ef4f2f9b584ae15b41ce9a4694ee7689b25c03

compiler-rt: support a new embedded linux target Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 418c53ddd26fcb47098f65fbd584cd06c683a43a

compiler-rt: Simplify cross-compilation. Don't use native-compiled llvm-config. Note: AddLLVM.cmake does not expose the LLVM source directory. So if you want to run the test suite, you need to either: 1) set LLVM_MAIN_SRC_DIR explicitly (to find lit.py) 2) change AddLLVM.cmake to point to an installed 'lit'. 3) add_subdirectory(compiler-rt/test) from clang instead of compiler-rt. https://us.codeaurora.org/patches/quic/llvm/50683/compiler-rt-cross-compilation.patch Signed-off-by: Greg Fitzgerald <gregf@codeaurora.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 91f5a97d6f018e0ca0ad502607acd8e9244304c8

llvm: TargetLibraryInfo: Undefine libc functions if they are macros musl defines some functions as macros and not inline functions if this is the case then make sure to undefine them Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Martin Kelly

commit sha 9a93330281b266cec4c64f4c42ce1a285b913774

llvm: allow env override of exe path When using a native llvm-config from inside a sysroot, we need llvm-config to return the libraries, include directories, etc. from inside the sysroot rather than from the native sysroot. Thus provide an env override for calling llvm-config from a target sysroot. Signed-off-by: Martin Kelly <mkelly@xevo.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Dan McGregor

commit sha 9fea0f171075e5ef1c639d937aa30f2d9b36257d

clang: driver: Check sysroot for ldso path OE does not necessarily follow the default path for the dynamic linker, therefore adjust it for OE. Check for the default path, and if it isn't there, check /lib. Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha f9ad01a1c39c9474ec0695bf30a26e011e8d7e65

clang: Driver/tools.cpp: Add -lssp_nonshared on musl musl driver will need to add ssp_nonshared for stack_check_local on the linker cmdline when using stack protector commands on compiler cmdline Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 74eb6df2e75e3e88b2814994269c5d9685b42384

clang: musl/ppc does not support 128-bit long double Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 260651cb1b6727b3b99c32b8b184d058f13a11fa

clang: Prepend trailing '/' to sysroot This is needed to handle a case where clang isntall and target sysroot are perilously same e.g. sysroot = /mnt/clang/recipe-sysroot clang install = /mnt/clang/recipe-sysroot-native in this case it will mistakenly assume that clang is installed under the same sysroot dir and it will try to add relative ../lib paths to linker steps which would then be wrong since they will become relative to clang installation and not sysroot Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 0010f296ddb13c61f17af33fafc9aff8217bb1a0

clang: Look inside the target sysroot for compiler runtime In OE compiler-rt and libc++ are built and staged into target sysroot and not into resourcedir which is relative to clang driver installation where the libraries are not instlled Specific to cross compiling the way yocto/OE works Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha ed45a39df32a9d50dea4e2cdd8766de47416480a

clang: Define / releative gcc installation dir This is required for OE gcc installation to work. Without this its not able to find the paths for libgcc and other standard headers and libraries from gcc installation in OE Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 3dc50967ecdf9c0369315e7d21e182372b93320e

clang: Add -lpthread and -ldl along with -lunwind for static linking When doing static liking with --unwindlib=libunwind -static we encounter undefined symbols libunwind/src/RWMutex.hpp:68: undefined reference to `pthread_rwlock_wrlock' and libunwind/src/AddressSpace.hpp:597: undefined reference to `dladdr' therefore we need to link in libpthread and libdl to fill these symbols Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Anuj Mittal

commit sha b867c9d4c0bc0532aa0dccaaaa3b332f563794aa

Pass PYTHON_EXECUTABLE when cross compiling for native build Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 01607c5796b62a3b8c7564e25ebcc5d39bc8f027

Check for atomic<double> intrinsics On some architectures e.g. x86/32bit gcc decides to inline calls to double atomic variables but clang does not and defers it to libatomic therefore detect if clang can use built-ins for atomic<double> if not then link libatomic, this helps building clangd for x86 on linux systems with gcc runtime Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Evangelos Foutras

commit sha 0ab3f8f19797281024c6d0e5ea183613458b59db

clang: Enable SSP and PIE by default This is a minimal set of changes needed to make clang use SSP and PIE by default on Arch Linux. Tests that were easy to adjust have been changed accordingly; only test/Driver/linux-ld.c has been marked as "expected failure" due to the number of changes it would require (mostly replacing crtbegin.o with crtbeginS.o). Doing so is needed in order to align clang with the new default GCC behavior in Arch which generates PIE executables by default and also defaults to -fstack-protector-strong. It is not meant to be a long term solution, but a simple temporary fix. Hopefully these changes will be obsoleted by the introduction upstream of a compile-time option (https://bugs.llvm.org/show_bug.cgi?id=13410) Taken from ArchLinux - https://git.archlinux.org/svntogit/packages.git/plain/trunk/enable-SSP-and-PIE-by-default.patch?h=packages/clang Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventkraj/gcc

Feng Xue

commit sha 03a8d9ab4cea24a945bb283c580d53a134221b9b

Fix null-pointer dereference in delete_dead_or_redundant_call [PR102451] 2021-09-23 Feng Xue <fxue@os.amperecomputing.com> gcc/ PR tree-optimization/102451 * tree-ssa-dse.c (delete_dead_or_redundant_call): Record bb of stmt before removal.

view details

Feng Xue

commit sha 210c3901749a245dc45f04da3dac70ef126e6762

Fix value uninitialization in vn_reference_insert_pieces [PR102400] 2021-09-23 Feng Xue <fxue@os.amperecomputing.com> gcc/ PR tree-optimization/102400 * tree-ssa-sccvn.c (vn_reference_insert_pieces): Initialize result_vdef to zero value.

view details

Khem Raj

commit sha 84c7b11a1c71554c893e061181ef388d61e9b965

gcc-4.3.1: ARCH_FLAGS_FOR_TARGET Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [embedded specific]

view details

Khem Raj

commit sha 873c14e44f2ce24d9087c4400ae295cf07f0894f

gcc: poison-system-directories Add /sw/include and /opt/include based on the original zecke-no-host-includes.patch patch. The original patch checked for /usr/include, /sw/include and /opt/include and then triggered a failure and aborted. Instead, we add the two missing items to the current scan. If the user wants this to be a failure, they can add "-Werror=poison-system-directories". Upstream-Status: Pending Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 7c1a80a8d3801734f3d5aa235431dcfde2fc0cec

gcc-4.3.3: SYSROOT_CFLAGS_FOR_TARGET Before committing, I noticed that PR/32161 was marked as a dup of PR/32009, but my previous patch did not fix it. This alternative patch is better because it lets you just use CFLAGS_FOR_TARGET to set the compilation flags for libgcc. Since bootstrapped target libraries are never compiled with the native compiler, it makes little sense to use different flags for stage1 and later stages. And it also makes little sense to use a different variable than CFLAGS_FOR_TARGET. Other changes I had to do include: - moving the creation of default CFLAGS_FOR_TARGET from Makefile.am to configure.ac, because otherwise the BOOT_CFLAGS are substituted into CFLAGS_FOR_TARGET (which is "-O2 -g $(CFLAGS)") via $(CFLAGS). It is also cleaner this way though. - passing the right CFLAGS to configure scripts as exported environment variables I also stopped passing LIBCFLAGS to configure scripts since they are unused in the whole src tree. And I updated the documentation as H-P reminded me to do. Bootstrapped/regtested i686-pc-linux-gnu, will commit to 4.4 shortly. Ok for 4.3? Signed-off-by: Paolo Bonzini <bonzini@gnu.org> Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha e9e2ce4d661d1688ca2f6d16dd5bb3f0ac6f741b

64-bit multilib hack. GCC has internal multilib handling code but it assumes a very specific rigid directory layout. The build system implementation of multilib layout is very generic and allows complete customisation of the library directories. This patch is a partial solution to allow any custom directories to be passed into gcc and handled correctly. It forces gcc to use the base_libdir (which is the current directory, "."). We need to do this for each multilib that is configured as we don't know which compiler options may be being passed into the compiler. Since we have a compiler per mulitlib at this point that isn't an issue. The one problem is the target compiler is only going to work for the default multlilib at this point. Ideally we'd figure out which multilibs were being enabled with which paths and be able to patch these entries with a complete set of correct paths but this we don't have such code at this point. This is something the target gcc recipe should do and override these platform defaults in its build config. Do same for riscv64, aarch64 & arc RP 15/8/11 Upstream-Status: Inappropriate[OE-Specific] Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Elvis Dowson <elvis.dowson@gmail.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 7d02419d40c1e4cc3f43994b612d64aea91b8900

optional libstdc gcc-runtime builds libstdc++ separately from gcc-cross-*. Its configure tests using g++ will not run correctly since by default the linker will try to link against libstdc++ which shouldn't exist yet. We need an option to disable -lstdc++ option whilst leaving -lc, -lgcc and other automatic library dependencies added by gcc driver. This patch adds such an option which only disables the -lstdc++. A "standard" gcc build uses xgcc and hence avoids this. We should ask upstream how to do this officially, the likely answer is don't build libstdc++ separately. RP 29/6/10 Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [embedded specific]

view details

Khem Raj

commit sha 33fc83f5d233f472693f09297f86bd4dab8c5f02

COLLECT_GCC_OPTIONS This patch adds --sysroot into COLLECT_GCC_OPTIONS which is used to invoke collect2. Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha 05dadb5e515aff6d1f82616cc11770dcad173c00

Use the defaults.h in ${B} instead of ${S}, and t-oe in ${B} Use the defaults.h in ${B} instead of ${S}, and t-oe in ${B}, so that the source can be shared between gcc-cross-initial, gcc-cross-intermediate, gcc-cross, gcc-runtime, and also the sdk build. Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending While compiling gcc-crosssdk-initial-x86_64 on some host, there is occasionally failure that test the existance of default.h doesn't work, the reason is tm_include_list='** defaults.h' rather than tm_include_list='** ./defaults.h' So we add the test condition for this situation. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>

view details

Khem Raj

commit sha 748c43bf7982f5ff4d2a7d2139aabad0f25030cd

fortran cross-compile hack. * Fortran would have searched for arm-angstrom-gnueabi-gfortran but would have used used gfortan. For gcc_4.2.2.bb we want to use the gfortran compiler from our cross directory. Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [embedded specific]

view details

Khem Raj

commit sha a95ea6b07a7f62724625c42a4a4ab87831486cba

cpp: honor sysroot. Currently, if the gcc toolchain is relocated and installed from sstate, then you try and compile preprocessed source (.i or .ii files), the compiler will try and access the builtin sysroot location rather than the --sysroot option specified on the commandline. If access to that directory is permission denied (unreadable), gcc will error. This happens when ccache is in use due to the fact it uses preprocessed source files. The fix below adds %I to the cpp-output spec macro so the default substitutions for -iprefix, -isystem, -isysroot happen and the correct sysroot is used. [YOCTO #2074] RP 2012/04/13 Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha 3f81255d176cb26b4f2944d110e1f86fb8397b2e

MIPS64: Default to N64 ABI MIPS64 defaults to n32 ABI, this patch makes it so that it defaults to N64 ABI Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [OE config specific]

view details

Khem Raj

commit sha 845af5462ba94fc16a5f203da2d52674d7803342

Define GLIBC_DYNAMIC_LINKER and UCLIBC_DYNAMIC_LINKER relative to SYSTEMLIBS_DIR This patch defines GLIBC_DYNAMIC_LINKER and UCLIBC_DYNAMIC_LINKER relative to SYSTEMLIBS_DIR which can be set in generated headers This breaks the assumption of hardcoded multilib in gcc Change is only for the supported architectures in OE including SH, sparc, alpha for possible future support (if any) Removes the do_headerfix task in metadata Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [OE configuration]

view details

Khem Raj

commit sha 79586b48c3012fd7e41ce6f1cb2273a2d51c4a53

gcc: Fix argument list too long error. There would be an "Argument list too long" error when the build directory is longer than 200, this is caused by: headers=`echo $(PLUGIN_HEADERS) | tr ' ' '\012' | sort -u` The PLUGIN_HEADERS is too long before sort, so the "echo" can't handle it, use the $(sort list) of GNU make which can handle the too long list would fix the problem, the header would be short enough after sorted. The "tr ' ' '\012'" was used for translating the space to "\n", the $(sort list) doesn't need this. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> RP: gcc then added *.h and *.def additions to this list, breaking the original fix. Add the sort to the original gcc code, leaving the tr+sort to fix the original issue but include the new files too as reported by Zhuang <qiuguang.zqg@alibaba-inc.com> Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha e60f32f4415ebcc985ca2226ab99523075d39c7b

Disable sdt. We don't list dtrace in DEPENDS so we shouldn't be depending on this header. It may or may not exist from preivous builds though. To be determinstic, disable sdt.h usage always. This avoids build failures if the header is removed after configure but before libgcc is compiled for example. RP 2012/8/7 Signed-off-by: Khem Raj <raj.khem@gmail.com> Disable sdt for libstdc++-v3. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Upstream-Status: Inappropriate [hack]

view details

Khem Raj

commit sha 383868668abbe41bf18848d96e4f91fcc3ea155c

libtool libstdc++ from gcc-runtime gets created with -rpath=/usr/lib/../lib for qemux86-64 when running on am x86_64 build host. This patch stops this speading to libdir in the libstdc++.la file within libtool. Arguably, it shouldn't be passing this into libtool in the first place but for now this resolves the nastiest problems this causes. func_normal_abspath would resolve an empty path to `pwd` so we need to filter the zero case. RP 2012/8/24 Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha 7aa8b9adb554594d1152a7ac991a95109c304e5b

gcc: armv4: pass fix-v4bx to linker to support EABI. The LINK_SPEC for linux gets overwritten by linux-eabi.h which means the value of TARGET_FIX_V4BX_SPEC gets lost and as a result the option is not passed to linker when chosing march=armv4 This patch redefines this in linux-eabi.h and reinserts it for eabi defaulting toolchains. We might want to send it upstream. Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha 0e14a7751b3b81e3222e0903580bc76e248dea18

Use the multilib config files from ${B} instead of using the ones from ${S} Use the multilib config files from ${B} instead of using the ones from ${S} so that the source can be shared between gcc-cross-initial, gcc-cross-intermediate, gcc-cross, gcc-runtime, and also the sdk build. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Upstream-Status: Inappropriate [configuration]

view details

Khem Raj

commit sha 4fd65384ee722abf50929591640ac73404cb7025

Avoid using libdir from .la which usually points to a host path Upstream-Status: Inappropriate [embedded specific] Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 83dcaf65e3cdd186e35bdce5408fc535c000c23d

export CPP The OE environment sets and exports CPP as being the target gcc. When building gcc-cross-canadian for a mingw targetted sdk, the following can be found in build.x86_64-pokysdk-mingw32.i586-poky-linux/build-x86_64-linux/libiberty/config.log: configure:3641: checking for _FILE_OFFSET_BITS value needed for large files configure:3666: gcc -c -isystem/media/build1/poky/build/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe conftest.c >&5 configure:3666: $? = 0 configure:3698: result: no configure:3786: checking how to run the C preprocessor configure:3856: result: x86_64-pokysdk-mingw32-gcc -E --sysroot=/media/build1/poky/build/tmp/sysroots/x86_64-nativesdk-mingw32-pokysdk-mingw32 configure:3876: x86_64-pokysdk-mingw32-gcc -E --sysroot=/media/build1/poky/build/tmp/sysroots/x86_64-nativesdk-mingw32-pokysdk-mingw32 conftest.c configure:3876: $? = 0 Note this is a *build* target (in build-x86_64-linux) so it should be using the host "gcc", not x86_64-pokysdk-mingw32-gcc. Since the mingw32 headers are very different, using the wrong cpp is a real problem. It is leaking into configure through the CPP variable. Ultimately this leads to build failures related to not being able to include a process.h file for pem-unix.c. The fix is to ensure we export a sane CPP value into the build environment when using build targets. We could define a CPP_FOR_BUILD value which may be the version which needs to be upstreamed but for now, this fix is good enough to avoid the problem. RP 22/08/2013 Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventkraj/gcc

Hongyu Wang

commit sha ea0f450e98db5f18d3363679db4cd82961f44642

AVX512FP16: Support cond_op for HFmode gcc/ChangeLog: * config/i386/sse.md (cond_<insn><mode>): Extend to support vector HFmodes. (cond_mul<mode>): Likewise. (cond_div<mode>): Likewise. (cond_<code><mode>): Likewise. (cond_fma<mode>): Likewise. (cond_fms<mode>): Likewise. (cond_fnma<mode>): Likewise. (cond_fnms<mode>): Likewise. gcc/testsuite/ChangeLog: * gcc.target/i386/cond_op_addsubmuldiv__Float16-1.c: New test. * gcc.target/i386/cond_op_addsubmuldiv__Float16-2.c: Ditto. * gcc.target/i386/cond_op_fma__Float16-1.c: Ditto. * gcc.target/i386/cond_op_fma__Float16-2.c: Ditto. * gcc.target/i386/cond_op_maxmin__Float16-1.c: Ditto. * gcc.target/i386/cond_op_maxmin__Float16-2.c: Ditto.

view details

Feng Xue

commit sha f91b11eb8891f3ae910eb3b2e4a48e2d7d670d2d

Fix null-pointer dereference in delete_dead_or_redundant_call [PR102451] 2021-09-23 Feng Xue <fxue@os.amperecomputing.com> gcc/ PR tree-optimization/102451 * tree-ssa-dse.c (delete_dead_or_redundant_call): Record bb of stmt before removal.

view details

Feng Xue

commit sha 29c92857039d0a105281be61c10c9e851aaeea4a

Fix value uninitialization in vn_reference_insert_pieces [PR102400] 2021-09-23 Feng Xue <fxue@os.amperecomputing.com> gcc/ PR tree-optimization/102400 * tree-ssa-sccvn.c (vn_reference_insert_pieces): Initialize result_vdef to zero value.

view details

push time in 6 hours

push eventkraj/gcc

Feng Xue

commit sha 03a8d9ab4cea24a945bb283c580d53a134221b9b

Fix null-pointer dereference in delete_dead_or_redundant_call [PR102451] 2021-09-23 Feng Xue <fxue@os.amperecomputing.com> gcc/ PR tree-optimization/102451 * tree-ssa-dse.c (delete_dead_or_redundant_call): Record bb of stmt before removal.

view details

Feng Xue

commit sha 210c3901749a245dc45f04da3dac70ef126e6762

Fix value uninitialization in vn_reference_insert_pieces [PR102400] 2021-09-23 Feng Xue <fxue@os.amperecomputing.com> gcc/ PR tree-optimization/102400 * tree-ssa-sccvn.c (vn_reference_insert_pieces): Initialize result_vdef to zero value.

view details

push time in 6 hours

push eventkraj/gcc

Hongyu Wang

commit sha ea0f450e98db5f18d3363679db4cd82961f44642

AVX512FP16: Support cond_op for HFmode gcc/ChangeLog: * config/i386/sse.md (cond_<insn><mode>): Extend to support vector HFmodes. (cond_mul<mode>): Likewise. (cond_div<mode>): Likewise. (cond_<code><mode>): Likewise. (cond_fma<mode>): Likewise. (cond_fms<mode>): Likewise. (cond_fnma<mode>): Likewise. (cond_fnms<mode>): Likewise. gcc/testsuite/ChangeLog: * gcc.target/i386/cond_op_addsubmuldiv__Float16-1.c: New test. * gcc.target/i386/cond_op_addsubmuldiv__Float16-2.c: Ditto. * gcc.target/i386/cond_op_fma__Float16-1.c: Ditto. * gcc.target/i386/cond_op_fma__Float16-2.c: Ditto. * gcc.target/i386/cond_op_maxmin__Float16-1.c: Ditto. * gcc.target/i386/cond_op_maxmin__Float16-2.c: Ditto.

view details

Feng Xue

commit sha f91b11eb8891f3ae910eb3b2e4a48e2d7d670d2d

Fix null-pointer dereference in delete_dead_or_redundant_call [PR102451] 2021-09-23 Feng Xue <fxue@os.amperecomputing.com> gcc/ PR tree-optimization/102451 * tree-ssa-dse.c (delete_dead_or_redundant_call): Record bb of stmt before removal.

view details

Feng Xue

commit sha 29c92857039d0a105281be61c10c9e851aaeea4a

Fix value uninitialization in vn_reference_insert_pieces [PR102400] 2021-09-23 Feng Xue <fxue@os.amperecomputing.com> gcc/ PR tree-optimization/102400 * tree-ssa-sccvn.c (vn_reference_insert_pieces): Initialize result_vdef to zero value.

view details

push time in 6 hours

push eventkraj/llvm-project

wlei

commit sha c2be2d3284d2b0d76eacbe3e3999fb0843ef65a6

[llvm-profgen] Fix a bug of assertion The assertion should work on the entire context. Reviewed By: hoy, wenlei Differential Revision: https://reviews.llvm.org/D110268

view details

wlei

commit sha 686cc0006793b06fd15d08cc0188b071f49ae990

[llvm-profgen] Fix an out-of-range error during unwinding It happened that the LBR entry target can be the first address of text section which causes an out-of-range crash. So here add a boundary check. Reviewed By: hoy, wenlei Differential Revision: https://reviews.llvm.org/D110271

view details

wlei

commit sha 1ed69bb86eb188ab23f62c266d2d23846588e768

[llvm-profgen] Fix a dangling vector reference in CS line number based generator It seems we missed one spot to persist `SampleContextFrameVector` into the global table (CSProfileGenerator::populateFunctionBoundarySamples:340) which causes a crash. This change tried to fix it in a centralized way i. e. where we generate the `FunctionSamples`. Reviewed By: hoy, wenlei Differential Revision: https://reviews.llvm.org/D110275

view details

Hsiangkai Wang

commit sha ebc5feb4ed6b1f59a000669030f9639bf1763403

[RISCV] Update mir tests.

view details

Freddy Ye

commit sha 13207a21a64d3a0f1537cc99efe91d757d51f46c

[NFC] Remove redundant setOperationAction. [FROUND,FROUNDEVEN][f32, f64, f128] are set Expand twice. Differential Revision: https://reviews.llvm.org/D110302

view details

John Demme

commit sha 47cc166bc023b497bdffe0964d80f15eaee8b7da

[MLIR] [Python] Make Attribute and Type hashable Enables putting types and attributes in sets and in dicts as keys. Reviewed By: stellaraccident Differential Revision: https://reviews.llvm.org/D110301

view details

Wang, Pengfei

commit sha ebec077e07f5d35a870f075fb665c006978d49ea

[X86][FP16] Change the order of the operands in complex FMA intrinsics to allow swap between the mul operands. Reviewed By: craig.topper Differential Revision: https://reviews.llvm.org/D109658

view details

Pengfei Wang

commit sha 1873f3be78a5255df8c36c195f4c778f9f47fc5c

[demangle] Support for ISO/IEC TS 18661 binary floating point type Reviewed By: #libc_abi, ldionne Differential Revision: https://reviews.llvm.org/D105278

view details

Usman Nadeem

commit sha 3b12282b0ed738f138229993505fbba23cd534a2

[AArch64][SVE][InstCombine] Eliminate redundant chains of tuple get/set Differential Revision: https://reviews.llvm.org/D109667 Change-Id: I06a3c28e3658ecda109a3a1b73265828274ab2ea

view details

Johannes Doerfert

commit sha 94c177e6b29e7ea1211d1650ca6fd98c87cd2b05

[OpenMP][NFC] Clang format OMPIRBuilder These files should be kept clang-formatted but diverge sometimes.

view details

Johannes Doerfert

commit sha 0a16c560102212f5b317e646486b6826847334ca

[OpenMP][NFC] Improve debug output

view details

Johannes Doerfert

commit sha 5e835ecb6d43eade0cbd0a91df7c22412481d264

[OpenMP][NFC] Precommit test that exposes a bug in our optnone handling

view details

Johannes Doerfert

commit sha 92280ae3d83d4c1436167fa05fc8292628062250

[OpenMP][NFC] Rerun the test check update script on all OpenMP-Opt tests

view details

Johannes Doerfert

commit sha 57822c3f4f36b81635da98707cf149747a754a6b

[OpenMP][NFC] Repair test that contained nested kernels The benchmark contained (partially) nested kernels, something we do not generate nor support.

view details

Johannes Doerfert

commit sha c6457dcae88043cbd07dedc61b602b66b26f1ddf

[OpenMP][FIX] Be more deliberate about invalidating the AAKernelInfo state This patch fixes a problem when the AAKernelInfo state was invalidated, e.g., due to `optnone` for a kernel, but not all parts indicated the invalidation properly. We further eliminate most full state invalidations as they should never be necessary. Differential Revision: https://reviews.llvm.org/D109468

view details

Kent Ross

commit sha f4abdb0c074bd7b7b89d9828d449078d16d0e1c3

[libc++][spaceship] Implement std::pair::operator<=> Implements parts of P1614, including synth-three-way and three way comparison for std::pair. Reviewed By: #libc, Quuxplusone, Mordante Differential Revision: https://reviews.llvm.org/D107721

view details

Mikael Holmen

commit sha e7b169a8ae99b0cef1e5262f18b35e0abcc69ef8

[AMDGPU] Fix gcc warnings about unused variables [NFC]

view details

Diana Picus

commit sha b7050c791d8951c0a099bf162f9ab3a696611b7d

[mlir] Fix build on Windows on Arm clang-cl errors out while handling the templated version of tgfmt. This patch works around the issue by explicitly choosing the non-templated version of tgfmt, which takes an ArrayRef<std::string>. More details in this thread: https://lists.llvm.org/pipermail/cfe-dev/2021-September/068936.html Thanks @Mehdi Amini for suggesting the fix :) Differential Revision: https://reviews.llvm.org/D110223

view details

Jan Svoboda

commit sha 352a2e67162541efe79a1e144b40a054751e7d5c

[clang][tooling] NFC: Refactor command-line diagnostic tests This patch uses a different command-line arguments to test `clang::tooling::ToolInvocation` that are not specific to Darwin. Reviewed By: dexonsmith Differential Revision: https://reviews.llvm.org/D110160

view details

Liu, Chen3

commit sha 76656ec8ec535bd17afc998112a83c7c55ad7719

[X86][FP16] Combine the FADD(A, FMA(B, C, 0)) to FMA(B, C, A) This patch is to support transform something like _mm512_add_ph(acc, _mm512_fmadd_pch(a, b, _mm512_setzero_ph())) to _mm512_fmadd_pch(a, b, acc). Differential Revision: https://reviews.llvm.org/D109953

view details

push time in 6 hours

push eventkraj/llvm-project

Kristóf Umann

commit sha ee6913cc8317c08b603daed64b07a17a95ec926a

[analyzer] Add 13.0.0 release notes Differential Revision: https://reviews.llvm.org/D108912

view details

Khem Raj

commit sha 8aef7041c51823df1c2fd184cf5fc4e2bf394a7f

lldb: Add -lxml2 to linker cmdline of xml is found When cross compiling for systems where static libs for libxml are not available cmake's detection mechanism resort to linking with libxml.so but doesnt use -lxml2 liblldbHost.a however requires libxml on linker cmdline _after_ itself so its use of symbols from libxml2 can be resolved. Here check for libxml2 being detected and add it if its found. Fixes | ../../../../lib/liblldbHost.a(XML.cpp.o): In function `lldb_private::XMLDocument::Clear()': | /usr/src/debug/lldb/5.0.0+gitAUTOINC+69edad7913_08d6b47db9_cf6c5b3386-r0/git/tools/lldb/source/Host/common/XML.cpp:29: undefined reference to `xmlFreeDoc' | /usr/src/debug/lldb/5.0.0+gitAUTOINC+69edad7913_08d6b47db9_cf6c5b3386-r0/git/tools/lldb/source/Host/common/XML.cpp:29: undefined reference to `xmlFreeDoc' Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha a0c225aaf875487a9750583bfe7927a63cdda94d

libcxxabi: Find libunwind headers when LIBCXXABI_LIBUNWIND_INCLUDES is set Currently, when LIBCXXABI_LIBUNWIND_INCLUDES is set via CMake arguments then it ends up not searching the specified dir and unwind.h is not found especially for ARM targets This patch makes the searching synthesized directories and then set LIBCXXABI_LIBUNWIND_INCLUDES if its there in environment Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha b6e529842df06e08cdabc2b7d24caa0307fb85f5

compiler-rt: support a new embedded linux target Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 098c9710da2fbc5b43d30396f27139e21b28642e

compiler-rt: Simplify cross-compilation. Don't use native-compiled llvm-config. Note: AddLLVM.cmake does not expose the LLVM source directory. So if you want to run the test suite, you need to either: 1) set LLVM_MAIN_SRC_DIR explicitly (to find lit.py) 2) change AddLLVM.cmake to point to an installed 'lit'. 3) add_subdirectory(compiler-rt/test) from clang instead of compiler-rt. https://us.codeaurora.org/patches/quic/llvm/50683/compiler-rt-cross-compilation.patch Signed-off-by: Greg Fitzgerald <gregf@codeaurora.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha f9874ff692b118ff6b6b78ad99d6dda690169b0a

llvm: TargetLibraryInfo: Undefine libc functions if they are macros musl defines some functions as macros and not inline functions if this is the case then make sure to undefine them Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Martin Kelly

commit sha 848fdfb0adcd97d8bf637bba2251b67d63b33377

llvm: allow env override of exe path When using a native llvm-config from inside a sysroot, we need llvm-config to return the libraries, include directories, etc. from inside the sysroot rather than from the native sysroot. Thus provide an env override for calling llvm-config from a target sysroot. Signed-off-by: Martin Kelly <mkelly@xevo.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Dan McGregor

commit sha 094f5915f4a435c5d53287a7a5f37ba61bac442b

clang: driver: Check sysroot for ldso path OE does not necessarily follow the default path for the dynamic linker, therefore adjust it for OE. Check for the default path, and if it isn't there, check /lib. Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 52943649f8eb57af2003660a983a585afcf77300

clang: Driver/tools.cpp: Add -lssp_nonshared on musl musl driver will need to add ssp_nonshared for stack_check_local on the linker cmdline when using stack protector commands on compiler cmdline Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha fb4e5ac04990576f1cecd7cc0704294902b33520

clang: musl/ppc does not support 128-bit long double Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha f7c050b8e4ef3fa5965926fd6aced0c6c2128fea

clang: Prepend trailing '/' to sysroot This is needed to handle a case where clang isntall and target sysroot are perilously same e.g. sysroot = /mnt/clang/recipe-sysroot clang install = /mnt/clang/recipe-sysroot-native in this case it will mistakenly assume that clang is installed under the same sysroot dir and it will try to add relative ../lib paths to linker steps which would then be wrong since they will become relative to clang installation and not sysroot Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha ab8f79f9843a46d96d01b02437c77177fc9cf5bb

clang: Look inside the target sysroot for compiler runtime In OE compiler-rt and libc++ are built and staged into target sysroot and not into resourcedir which is relative to clang driver installation where the libraries are not instlled Specific to cross compiling the way yocto/OE works Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 129b7975137c7c3459bdb7a148496439527613ff

clang: Define / releative gcc installation dir This is required for OE gcc installation to work. Without this its not able to find the paths for libgcc and other standard headers and libraries from gcc installation in OE Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 91fa5e7f218b96db9a3d19560ba6fa11e10d2061

clang: Add -lpthread and -ldl along with -lunwind for static linking When doing static liking with --unwindlib=libunwind -static we encounter undefined symbols libunwind/src/RWMutex.hpp:68: undefined reference to `pthread_rwlock_wrlock' and libunwind/src/AddressSpace.hpp:597: undefined reference to `dladdr' therefore we need to link in libpthread and libdl to fill these symbols Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Anuj Mittal

commit sha c889ae82e713c44110960e87dad8ca2e4a403023

Pass PYTHON_EXECUTABLE when cross compiling for native build Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 3fc3dc7aadbbabbfab7c2ee916b460c0531ea0ca

Check for atomic<double> intrinsics On some architectures e.g. x86/32bit gcc decides to inline calls to double atomic variables but clang does not and defers it to libatomic therefore detect if clang can use built-ins for atomic<double> if not then link libatomic, this helps building clangd for x86 on linux systems with gcc runtime Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Evangelos Foutras

commit sha b74ee6671a1a1329bcaafd2853b66f412c12837a

clang: Enable SSP and PIE by default This is a minimal set of changes needed to make clang use SSP and PIE by default on Arch Linux. Tests that were easy to adjust have been changed accordingly; only test/Driver/linux-ld.c has been marked as "expected failure" due to the number of changes it would require (mostly replacing crtbegin.o with crtbeginS.o). Doing so is needed in order to align clang with the new default GCC behavior in Arch which generates PIE executables by default and also defaults to -fstack-protector-strong. It is not meant to be a long term solution, but a simple temporary fix. Hopefully these changes will be obsoleted by the introduction upstream of a compile-time option (https://bugs.llvm.org/show_bug.cgi?id=13410) Taken from ArchLinux - https://git.archlinux.org/svntogit/packages.git/plain/trunk/enable-SSP-and-PIE-by-default.patch?h=packages/clang Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Jeremy Puhlman

commit sha 9862e75d638776d71419e044df6d58c5600ca87c

libcxx: Add compiler runtime library to link step for libcxx This corrects "undefined reference to __divti3" Upstream-Status: Inappropriate [configuration] Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Ovidiu Panait

commit sha 4dfb712bbc692a0baaaaddc04c423ec70457c474

clang,llvm: cmake: Fix configure for packages using find_package() Currently, when a package (i.e. bcc [https://github.com/iovisor/bcc.git]) that depends on LLVM/Clang tries to run cmake find_package() during do_configure, it will fail with a similar error: | The imported target "llvm-tblgen" references the file | ".../recipe-sysroot/usr/bin/llvm-tblgen" | | but this file does not exist. Possible reasons include: | * The file was deleted, renamed, or moved to another location. | * An install or uninstall procedure did not complete successfully. | * The installation package was faulty and contained | ".../recipe-sysroot/usr/lib/cmake/LLVMExports.cmake" | but not all the files it references. This is due to the fact that currently the cmake scripts look for target binaries in sysroot. Work around this by not exporting the target binaries in Exports-* cmake files. Upstream-Status: Innapropriate [oe-specific] Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>

view details

Jim Broadus

commit sha f2b9968d1d1d85dff36a6891bad3e5e72a6a6b9d

clang: Fix resource dir location for cross toolchains When clang looks for the resources directory, it does so based on the binary location and assumes that the containing directory is a sibling to lib. The Yocto cross.bbclass defines the default bindir as ${exec_prefix}/bin/${CROSS_TARGET_SYS_DIR}. ex: /usr/bin/aarch64-poky-linux/. This causes clang to form a path that looks like /usr/bin/lib/clang/... As a fix for this, check the parent directory name. If that is "bin", then use that directory's parent. Signed-off-by: Jim Broadus <jbroadus@xevo.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventkraj/glibc

Florian Weimer

commit sha 2849e2f53311b66853cb5159b64cba2bddbfb854

nptl: Avoid setxid deadlock with blocked signals in thread exit [BZ #28361] As part of the fix for bug 12889, signals are blocked during thread exit, so that application code cannot run on the thread that is about to exit. This would cause problems if the application expected signals to be delivered after the signal handler revealed the thread to still exist, despite pthread_kill can no longer be used to send signals to it. However, glibc internally uses the SIGSETXID signal in a way that is incompatible with signal blocking, due to the way the setxid handshake delays thread exit until the setxid operation has completed. With a blocked SIGSETXID, the handshake can never complete, causing a deadlock. As a band-aid, restore the previous handshake protocol by not blocking SIGSETXID during thread exit. The new test sysdeps/pthread/tst-pthread-setuid-loop.c is based on a downstream test by Martin Osvald. Reviewed-by: Carlos O'Donell <carlos@redhat.com> Tested-by: Carlos O'Donell <carlos@redhat.com>

view details

Florian Weimer

commit sha 0a5e270bd16f2df5c72a1524c71b057e774a4942

vfprintf: Handle floating-point cases outside of process_arg macro A lot of the code is unique to the positional and non-positional code. Also unify the decimal and hexadecimal cases via the new helper function __printf_fp_spec.

view details

Florian Weimer

commit sha 475b0b92e079c67ea8a25ec05fe0b17fdd935e12

vfprintf: Unify argument handling in process_arg Instead of checking a pointer argument for NULL, use helper macros defined differently in the non-positional and positional cases. This avoids frequent conditional checks and a GCC 12 warning about comparing pointers against NULL which cannot be NULL.

view details

Joseph Myers

commit sha 4ed7a383f9a8468194ccaebba3f0fa659003888d

Fix ffma use of round-to-odd on x86 On 32-bit x86 with -mfpmath=sse, and on x86_64 with --disable-multi-arch, the tests of ffma and its aliases (fma narrowing from binary64 to binary32) fail. This is probably the issue reported by H.J. in <https://sourceware.org/pipermail/libc-alpha/2021-September/131277.html>. The problem is the use of fenv_private.h macros in the round-to-odd implementation. Those macros are set up to manipulate only one of the SSE and 387 floating-point state, whichever is relevant for the type indicated by the suffix on the macro name. But x86 configurations sometimes use the ldbl-96 implementation of binary64 fma (that's where --disable-multi-arch is relevant for x86_64: it causes the ldbl-96 implementation to be used, instead of an IFUNC implementation that falls back to the dbl-64 version), contrary to the expectations of those macros for functions operating on double when __SSE2_MATH__ is defined. This can be addressed by using the default versions of those macros (giving x86 its own version of s_ffma.c), as is done for the *f128 macro variants where it depends on the details of how GCC was configured when building libgcc which floating-point state is affected by _Float128 arithmetic. The issue only applies when __SSE2_MATH__ is defined, and doesn't apply when __FP_FAST_FMA is defined (because in that case, fma will be inlined by the compiler, meaning it's definitely an SSE operation; for the same reason, this is not an issue for narrowing sqrt, as hardware sqrt is always inlined in that implementation for x86), but in other cases it's safest to use the default versions of the fenv_private.h macros to ensure things work whichever fma implementation is used. Tested for x86_64 (with and without --disable-multi-arch) and x86 (with and without -mfpmath=sse).

view details

Tulio Magno Quites Machado Filho

commit sha 54ff4f1e39067bfd04fb2141710637a11ef88862

powerpc64le: Avoid conflicting types for f64xfmaf128 when IFUNC is not used Avoid defining f64xfmaf128 twice when building s_fmaf128.c. This can be reproduced on powerpc64le whenever f128 functions do not have IFUNC enabled, e.g. using "--with-cpu=power8 --disable-multi-arch", or when using "-with-cpu=power9". Fixes: b3f27d8150d4f ("Add narrowing fma functions")

view details

Jason Wessel

commit sha fa4a46a840c56abc05f676eec82613af61cb2555

localedef: Add hardlink resolver from util-linux The hard link resolver that is built into localedef cannot be run in parallel. It will search sibling directories (which are be processed in parallel) and perform a creation of a .tmp file and remove the original and move the .tmp file in. The problem is that if a probe occurs a hard link can be requested to the file that is being removed. This will lead to a stray copy or potentially, on a loaded system cause race condition which pseudo cannot deal with, where it is left with a hard link request to a file that no longer exists. In this situation psuedo will inherit the permissions of what ever the target inode had to offer. In short, there are two problems: 1) You will be left with stray copies when using the hard link resolution that is built in while running in parallel with localedef. 2) When running under pseudo the possibility exists for uid/gid leakage when the source file is removed before the hard link can be completed. The solution is to call localedef with --no-hard-links and separately process the hardlinks at a later point. To do this requires the inclusion of the hardlink utility found in modern versions of util-linux. Most host systems do not have this, so it will be included with the cross-localedef binary. [YOCTO #11299] [YOCTO #12434] Upstream-Status: Pending Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Jason Wessel

commit sha ecd49e939d850902fa00435999f7ff0973438a57

localedef: fix-ups hardlink to make it compile Upstream-Status: Pending Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha f05d6f40b05679f6624764f2389c06d1376fbed2

nativesdk-glibc: Look for host system ld.so.cache as well Upstream-Status: Inappropriate [embedded specific] The default lib search path order is: 1) LD_LIBRARY_PATH 2) RPATH from the binary 3) ld.so.cache 4) default search paths embedded in the linker For nativesdk binaries which are being used alongside binaries on a host system, we need the search paths to firstly search the shipped nativesdk libs but then also cover the host system. For example we want the host system's libGL and this may be in a non-standard location like /usr/lib/mesa. The only place the location is know about is in the ld.so.cache of the host system. Since nativesdk has a simple structure and doesn't need to use a cache itself, we repurpose the cache for use as a last resort in finding host system binaries. This means we need to switch the order of 3 and 4 above to make this work effectively. RP 14/10/2010 Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 2abb7f7b9ecb9e0837fdf4a535238b927d682a00

nativesdk-glibc: Fix buffer overrun with a relocated SDK When ld-linux-*.so.2 is relocated to a path that is longer than the original fixed location, the dynamic loader will crash in open_path because it implicitly assumes that max_dirnamelen is a fixed size that never changes. The allocated buffer will not be large enough to contain the directory path string which is larger than the fixed location provided at build time. Upstream-Status: Inappropriate [OE SDK specific] Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha da9e0c0a12d984ff348a157e29a0ab36ffa2684f

nativesdk-glibc: Raise the size of arrays containing dl paths This patch puts the dynamic loader path in the binaries, SYSTEM_DIRS strings and lengths as well as ld.so.cache path in the dynamic loader to specific sections in memory. The sections that contain paths have been allocated a 4096 byte section, which is the maximum path length in linux. This will allow the relocating script to parse the ELF binary, detect the section and easily replace the strings in a certain path. Upstream-Status: Inappropriate [SDK specific] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 5d8eb52a2a4498f514f6e1f208eb8008d6dceca8

nativesdk-glibc: Allow 64 bit atomics for x86 The fix consist of allowing 64bit atomic ops for x86. This should be safe for i586 and newer CPUs. It also makes the synchronization more efficient. Upstream-Status: Inappropriate [OE-Specific] Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 9f5b1c790698407f788a5cb5d909f670af43de3f

nativesdk-glibc: Make relocatable install for locales The glibc locale path is hard-coded to the install prefix, but in SDKs we need to be able to relocate the binaries. Expand the strings to 4K and put them in a magic segment that we can relocate at install time. Upstream-Status: Inappropriate (OE-specific) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 3bcdbfee99705363e47aab458e18b899c23c819f

nativesdk-glibc: Fall back to faccessat on faccess2 returns EPERM Fedora-specific workaround for systemd-nspawn Upstream-Status: Inappropriate [Distro Specific] Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 86676637b60f489ccfe30f3c6dab375bebbcbbce

fsl e500/e5500/e6500/603e fsqrt implementation Upstream-Status: Pending Signed-off-by: Edmar Wienskoski <edmar@freescale.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 0b052dae7a76a20733936883f1acc4545282dc2d

ppc/sqrt: Fix undefined reference to `__sqrt_finite' on ppc fixes the errors like below | ./.libs/libpulsecore-1.1.so: undefined reference to `__sqrt_finite' | collect2: ld returned 1 exit status Upstream-Status: Pending ChangeLog 2012-01-06 Khem Raj <raj.khem@gmail.com> * sysdeps/powerpc/powerpc64/e5500/fpu/e_sqrtf.c: Add __*_finite alias. Remove cruft. * sysdeps/powerpc/powerpc64/e5500/fpu/e_sqrt.c: Ditto. * sysdeps/powerpc/powerpc32/603e/fpu/e_sqrt.c: Ditto. * sysdeps/powerpc/powerpc32/603e/fpu/e_sqrtf.c: Ditto. Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 13a38b3d1beca1cfdad341eca8b7c40c84023f04

__ieee754_sqrt{,f} are now inline functions and call out __slow versions Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 65d3fae3a7c23fdb2a35825b133d2205a7200da5

Quote from bug 1443 which explains what the patch does : We build some random program and link it with -lust. When we run it, it dies with a SIGSEGV before reaching main(). Libust.so depends on liburcu-bp.so from the usermode-rcu package. Although libust.so is not prelinked, liburcu-bp.so IS prelinked; this is critical. Libust.so uses a TLS / __thread variable that is defined in liburcu- bp.so. There are special ARM-specific relocation types that allow two shared libraries to share thread-specific data. This is critical too. One more critical issue: although liburcu-bp.so is prelinked, we can't load it at its prelinked address, because we also link against librt.so, and librt.so uses that address. The dynamic linker is forced to relink liburcu-bp.so at a different address. In the course of relinking, it processes the special ARM relocation record mentioned above. The prelinker has already filled in the information, which is a short offset into a table of thread- specific data that is allocated per-thread for each library that uses TLS. Because the normal behavior of a relocation is to add the symbol value to an addend stored at the address being relocated, we end up adding the short offset to itself, doubling it. Now we have an awkward situation. The libust.so library doesn't know about the addend, so its TLS data for this element is correct. The liburcu-bp.so library has a different offset for the element. When we go to initialize the element for the first time in liburcu-bp.so, we write the address of the result at the doubled (broken) offset. Later, when we refer to the address from libust.so, we check the value at the correct offset, but it's NULL, so we eat hot SIGSEGV. Upstream-Status: Pending Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Ting Liu

commit sha 1935858952136c5267dce59d06442a2d8ff9d146

eglibc: run libm-err-tab.pl with specific dirs in ${S} libm-err-tab.pl will parse all the files named "libm-test-ulps" in the given dir recursively. To avoid parsing the one in ${S}/.pc/ (it does exist after eglibc adds aarch64 support, ${S}/.pc/aarch64-0001-glibc-fsf-v1-eaf6f205.patch/ports/sysdeps/ aarch64/libm-test-ulps), run libm-err-tab.pl with specific dirs in ${S}. Upstream-Status: inappropriate [OE specific] Signed-off-by: Ting Liu <b28495@freescale.com>

view details

Khem Raj

commit sha 8144221e94687775a9332afaad915a74677b03e3

__ieee754_sqrt{,f} are now inline functions and call out __slow versions Upstream-Status: Pending Signed-off-by: chunrong guo <B40290@freescale.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 529e45c069b2848daea37752334d912912454eab

sysdeps/gnu/configure.ac: handle correctly $libc_cv_rootsbindir Upstream-Status:Pending Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventkraj/gcc

Aldy Hernandez

commit sha 4c0c43623efe2900dd0feb3abf8b611023362c43

Overhaul jump thread state in forward threader. I've been pulling state from across the forward jump threader into the jt_state class, but it it still didn't feel right. The ultimate goal was to keep track of candidate threading paths so that the simplifier could simplify statements with the path as context. This patch completes the transition, while cleaning up a lot of things in the process. I've revamped both state and the simplifier such that a base state class contains only the blocks as they're registered, and any pass specific knowledge is where it belongs... in the pass. This allows VRP to keep its const and copies business, and DOM to keep this as well as its evrp client. This makes the threader cleaner, as it will now have no knowledge of either const/copies or evrp. This also paves the wave for the upcoming hybrid threader, which will just derive the state class and provide almost nothing, since the ranger doesn't need to register any equivalences or ranges as it folds. There is some code duplication in the simplifier, since both the DOM and VRP clients use a vr_values based simplifier, but this is temporary as the VRP client is about to be replaced with a hybrid ranger. For a better view of what this patch achieves, here are the base classes: class jt_state { public: virtual ~jt_state () { } virtual void push (edge); virtual void pop (); virtual void register_equiv (tree dest, tree src, bool update_range = false); virtual void register_equivs_edge (edge e); virtual void register_equivs_stmt (gimple *, basic_block, class jt_simplifier *); virtual void record_ranges_from_stmt (gimple *stmt, bool temporary); void get_path (vec<basic_block> &); void append_path (basic_block); void dump (FILE *); void debug (); private: auto_vec<basic_block> m_blocks; }; class jt_simplifier { public: virtual ~jt_simplifier () { } virtual tree simplify (gimple *, gimple *, basic_block, jt_state *) = 0; }; There are no functional changes. gcc/ChangeLog: * tree-ssa-dom.c (class dom_jump_threader_simplifier): Rename... (class dom_jt_state): ...this and provide virtual overrides. (dom_jt_state::register_equiv): New. (class dom_jt_simplifier): Rename from dom_jump_threader_simplifier. (dom_jump_threader_simplifier::simplify): Rename... (dom_jt_simplifier::simplify): ...to this. (pass_dominator::execute): Use dom_jt_simplifier and dom_jt_state. * tree-ssa-threadedge.c (jump_threader::jump_threader): Clean-up. (jt_state::register_equivs_stmt): Abstract out... (jump_threader::record_temporary_equivalences_from_stmts_at_dest): ...from here. (jump_threader::thread_around_empty_blocks): Update state. (jump_threader::thread_through_normal_block): Same. (jt_state::jt_state): Remove. (jt_state::push): Remove pass specific bits. Keep block vector updated. (jt_state::append_path): New. (jt_state::pop): Remove pass specific bits. (jt_state::register_equiv): Same. (jt_state::record_ranges_from_stmt): Same. (jt_state::register_equivs_on_edge): Same. Rename... (jt_state::register_equivs_edge): ...to this. (jt_state::dump): New. (jt_state::debug): New. (jump_threader_simplifier::simplify): Remove. (jt_state::get_path): New. * tree-ssa-threadedge.h (class jt_simplifier): Make into a base class. Expose common functionality as virtual methods. (class jump_threader_simplifier): Same. Rename... (class jt_simplifier): ...to this. * tree-vrp.c (class vrp_jump_threader_simplifier): Rename... (class vrp_jt_simplifier): ...to this. Provide pass specific overrides. (class vrp_jt_state): New. (vrp_jump_threader_simplifier::simplify): Rename... (vrp_jt_simplifier::simplify): ...to this. Inline code from what used to be the base class. (vrp_jump_threader::vrp_jump_threader): Use vrp_jt_state and vrp_jt_simplifier.

view details

Jakub Jelinek

commit sha 0d39eb28fd2ab00306bd7c0a87b6c0ed615b5d12

openmp: Diagnose omp::directive attribute without balanced token argument [PR102413] If omp::directive attribute argument starting with the opening ( is not a balanced token sequence, then cp_parser_skip_balanced_tokens (parser, 1) returns 1, but the code was subtracting 2 from it and iterating until it was 0, so for the non-balanced case it iterated from (size_t) -1 down to 0. The following patch just diagnoses that as an error. 2021-09-23 Jakub Jelinek <jakub@redhat.com> PR c++/102413 * parser.c (cp_parser_omp_directive_args): Diagnose if omp::directive is not followed by a balanced token sequence starting with open paren. * g++.dg/gomp/attrs-14.C: New test.

view details

liuhongt

commit sha cb8d916eef53327d922f5301bc2ce29735fb7e24

AVX512FP16: Add expander for rint/nearbyinthf2. gcc/ChangeLog: * config/i386/i386.md (rinthf2): New expander. (nearbyinthf2): New expander. gcc/testsuite/ChangeLog: * gcc.target/i386/avx512fp16-builtin-round-1.c: Add new testcase.

view details

liuhongt

commit sha 1041111f19849da29117a0e962ce7ad5262a4403

AVX512FP16: Add expander for fmahf4 gcc/ChangeLog: * config/i386/sse.md (FMAMODEM): extend to handle FP16. (VFH_SF_AVX512VL): Extend to handle HFmode. (VF_SF_AVX512VL): Deleted. gcc/testsuite/ChangeLog: * gcc.target/i386/avx512fp16-fma-1.c: New test. * gcc.target/i386/avx512fp16vl-fma-1.c: New test. * gcc.target/i386/avx512fp16vl-fma-vectorize-1.c: New test.

view details

Hongyu Wang

commit sha fccd8855ed4ed9d1cc0e55fc1758b3288468657e

AVX512FP16: Add expander for smin/maxhf3. gcc/ChangeLog: * config/i386/i386.md (<code>hf3): New expander. gcc/testsuite/ChangeLog: * gcc.target/i386/avx512fp16-builtin-minmax-1.c: New test.

view details

Hongyu Wang

commit sha 60698a19c77aef8c96d14238975e12fad653e7fb

AVX512FP16: Add fix(uns)?_truncmn2 for HF scalar and vector modes NB: 64bit/32bit vectorize for HFmode is not supported for now, will adjust this patch when V2HF/V4HF operations supported. gcc/ChangeLog: * config/i386/i386.md (fix<fixunssuffix>_trunchf<mode>2): New expander. (fixuns_trunchfhi2): Likewise. (*fixuns_trunchfsi2zext): New define_insn. * config/i386/sse.md (ssePHmodelower): New mode_attr. (fix<fixunssuffix>_trunc<ssePHmodelower><mode>2): New expander for same element vector fix_truncate. (fix<fixunssuffix>_trunc<ssePHmodelower><mode>2): Likewise for V4HF to V4SI/V4DI fix_truncate. (fix<fixunssuffix>_truncv2hfv2di2): Likeise for V2HF to V2DI fix_truncate. gcc/testsuite/ChangeLog: * gcc.target/i386/avx512fp16-trunchf.c: New test. * gcc.target/i386/avx512fp16-truncvnhf.c: Ditto.

view details

Hongyu Wang

commit sha 25faed6f37969a72ea8257736a6821a5c3a54bba

AVX512FP16: Add float(uns)?mn2 expander gcc/ChangeLog: * config/i386/sse.md (float<floatunssuffix><mode><ssePHmodelower>2): New expander. (avx512fp16_vcvt<floatsuffix><sseintconvert>2ph_<mode>): Rename to ... (float<floatunssuffix><mode>v4hf2): ... this, and drop constraints. (avx512fp16_vcvt<floatsuffix>qq2ph_v2di): Rename to ... (float<floatunssuffix>v2div2hf2): ... this, and likewise. gcc/testsuite/ChangeLog: * gcc.target/i386/avx512fp16-floatvnhf.c: New test.

view details

Hongyu Wang

commit sha 3829793c50e44a524757020cebf23c54c016d5af

AVX512FP16: add truncmn2/extendmn2 expanders gcc/ChangeLog: * config/i386/sse.md (extend<ssePHmodelower><mode>2): New expander. (extendv4hf<mode>2): Likewise. (extendv2hfv2df2): Likewise. (trunc<mode><ssePHmodelower>2): Likewise. (avx512fp16_vcvt<castmode>2ph_<mode>): Rename to ... (trunc<mode>v4hf2): ... this, and drop constraints. (avx512fp16_vcvtpd2ph_v2df): Rename to ... (truncv2dfv2hf2): ... this, and likewise. gcc/testsuite/ChangeLog: * gcc.target/i386/avx512fp16-trunc-extendvnhf.c: New test.

view details

Hongyu Wang

commit sha 9ce500289a69d48cf7b2ea633e4d99565fed5a64

AVX512FP16: Enable vec_cmpmn/vcondmn expanders for HF modes. gcc/ChangeLog: * config/i386/i386-expand.c (ix86_use_mask_cmp_p): Enable HFmode mask_cmp. * config/i386/sse.md (sseintvecmodelower): Add HF vector modes. (<avx512>_store<mode>_mask): Extend to support HF vector modes. (vec_cmp<mode><avx512fmaskmodelower>): Likewise. (vcond_mask_<mode><avx512fmaskmodelower>): Likewise. (vcond<mode><mode>): New expander. (vcond<mode><sseintvecmodelower>): Likewise. (vcond<sseintvecmodelower><mode>): Likewise. (vcondu<mode><sseintvecmodelower>): Likewise. gcc/testsuite/ChangeLog: * g++.target/i386/avx512fp16-vcondmn-vec.C: New test. * g++.target/i386/avx512fp16-vcondmn-minmax.C: Ditto. * gcc.target/i386/avx512fp16-vcondmn-loop-1.c: Ditto. * gcc.target/i386/avx512fp16-vcondmn-loop-2.c: Ditto. * gcc.target/i386/avx512fp16-vec_cmpmn.c: Ditto.

view details

Richard Biener

commit sha c0cc62b32d95caca25a8854e0d2b6f11f5674d30

tree-optimization/102448 - clear copied alignment info from vect This fixes the previous change which removed setting alignment info from the vectorizers idea of how a pointer is being used but left in place the copied info from DR_PTR_INFO without realizing that this is in fact _not_ the alignment of the access but the alignment of a base pointer contained in it. The following makes sure to not use that info. 2021-09-23 Richard Biener <rguenther@suse.de> PR tree-optimization/102448 * tree-vect-data-refs.c (vect_duplicate_ssa_name_ptr_info): Clear alignment info copied from DR_PTR_INFO.

view details

Jonathan Wakely

commit sha d917742fe27ad9cc28db777c11059b6c1c1ac816

configure: Update --help output for --with-multilib-list The list of architectures that support the option is incomplete. Signed-off-by: Jonathan Wakely <jwakely@redhat.com> Reviewed-by: Jim Wilson <jimw@sifive.com> gcc/ChangeLog: * configure.ac: Fix --with-multilib-list description. * configure: Regenerate.

view details

Aldy Hernandez

commit sha f3d357bab357abcbe4d8fc82898c68fd3a4c3471

Hoist edge calculations in precompute_relations. Tested on x86-64 Linux. gcc/ChangeLog: * gimple-range-path.cc (path_range_query::precompute_relations): Hoist edge calculations before using EDGE_SUCC.

view details

Aldy Hernandez

commit sha 00446916206cbf9812a92b418090919515289a20

Remove dominator check in fold_using_range::range_of_phi. Revert the following patch, as it was an artifact of diagnostic code being run with improper IL. commit 64b80b8819f9ea74712625bceb0ec4388e25f67d Author: Aldy Hernandez <aldyh@redhat.com> Date: Tue Sep 21 08:28:28 2021 +0200 Do not query SCEV in range_of_phi unless dominators are available. SCEV won't work without dominators and we can get called without dominators from debug_ranger. gcc/ChangeLog: * gimple-range-fold.cc (fold_using_range::range_of_phi): Remove dominator check.

view details

Bill Schmidt

commit sha 16e3d6b8b2b5168ebc773833f0e7ccf2191932c1

rs6000: Add psabi diagnostic for C++ zero-width bit field ABI change Previously zero-width bit fields were removed from structs, so that otherwise homogeneous aggregates were treated as such and passed in FPRs and VSRs. This was incorrect behavior per the ELFv2 ABI. Now that these fields are no longer being removed, we generate the correct parameter passing code. Alert the unwary user in the rare cases where this behavior changes. 2021-09-23 Bill Schmidt <wschmidt@linux.ibm.com> gcc/ PR target/102024 * config/rs6000/rs6000-call.c (rs6000_aggregate_candidate): Detect zero-width bit fields and return indicator. (rs6000_discover_homogeneous_aggregate): Diagnose when the presence of a zero-width bit field changes parameter passing in GCC 12. gcc/testsuite/ PR target/102024 * g++.target/powerpc/pr102024.C: New.

view details

Steve Baird

commit sha 62e66ee5bfe93de637f9ea9849a73807894936e0

[Ada] Update "Implementation Defined Characteristics" documentation. gcc/ada/ * doc/gnat_rm/implementation_defined_characteristics.rst: Update this section to reflect the current version of Ada RM M.2. * gnat_rm.texi: Regenerate.

view details

Piotr Trojanek

commit sha 37a3df0d9a849c912735124ec0b156c229fb308a

[Ada] Remove global parameter in Global contracts of Ada.Strings.Bounded gcc/ada/ * libgnat/a-strbou.ads (Generic_Bounded_Length): Remove non-null Global contracts.

view details

Yannick Moy

commit sha 7165704bfaae012cb28e5411619218da6fb8320d

[Ada] Minimize parts of Ada.Strings.Fixed marked SPARK_Mode => Off gcc/ada/ * libgnat/a-strfix.adb (Delete, Insert, Overwrite, Replace_Slice): Remove SPARK_Mode Off. * libgnat/a-strfix.ads (Insert, Overwrite, Replace_Slice): Strengthen precondition.

view details

Bob Duff

commit sha 99e30ba8c01f80a81891223069d47d8a611082c4

[Ada] Cleanup and efficiency improvements gcc/ada/ * gen_il-gen.adb: Generate getters and setters with much of the code inlined. Generate code for storing a few fields in the node header, to avoid the extra level of indirection for those fields. We generate the header type, so we don't have to duplicate hand-written Ada and C code to depend on the number of header fields. Declare constants for slot size. Use short names because these are used all over. Remove Put_Low_Level_Accessor_Instantiations, Put_Low_Level_C_Getter, which are no longer needed. Rename Put_High_Level_C_Getter-->Put_C_Getter. * atree.ads, atree.adb: Take into account the header slots. Take into account the single Node_Or_Entity_Field type. Remove "pragma Assertion_Policy (Ignore);", because the routines in this package are no longer efficiency critical. * atree.h: Remove low-level getters, which are no longer used by sinfo.h and einfo.h. * einfo-utils.adb: Avoid crash in Known_Alignment. * live.adb, sem_eval.adb: Remove code that prevents Node_Id from having a predicate. We don't actually add a predicate to Node_Id, but we want to be able to for temporary debugging. * sinfo-utils.adb: Remove code that prevents Node_Id from having a predicate. Take into account the single Node_Or_Entity_Field type. * sinfo-utils.ads: Minor. * table.ads (Table_Type): Make the components aliased, because low-level setters in Atree need to take 'Access. * treepr.adb: Take into account the single Node_Or_Entity_Field type. Make some code more robust, so we can print out half-baked nodes. * types.ads: Move types here for visibility purposes. * gcc-interface/gigi.h, gcc-interface/trans.c: Take into account the Node_Header change in the GNAT front end. * gcc-interface/cuintp.c, gcc-interface/targtyps.c: Add because gigi.h now refers to type Node_Header, which is in sinfo.h.

view details

Piotr Trojanek

commit sha e2b2f629da02f9b2549db7297133166f721953ae

[Ada] Remove Initializes contracts from Ada.Strings.Bounded gcc/ada/ * libgnat/a-strbou.ads (Generic_Bounded_Length): Remove explicit Initializes contract.

view details

Richard Kenner

commit sha fb3f21a3df8062a7a209b385aae377de2d8c093e

[Ada] If unnesting and relocating subprogram call, make new Parameter_Associations gcc/ada/ * atree.adb (Relocate_Node): If relocating a subprgram call and we're doing unnesting, make a new Parameter_Associations, if any.

view details

push time in 6 hours

push eventkraj/gcc

GCC Administrator

commit sha 23f129487e62c6fc3384aae53c22fe7c61d1f3d7

Daily bump.

view details

Khem Raj

commit sha 412282aae8ec869efac1d34f90b3b3fcc2679e03

gcc-4.3.1: ARCH_FLAGS_FOR_TARGET Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [embedded specific]

view details

Khem Raj

commit sha 15eb54644cfc2b5bbb4da4935abf8bf7ae39a466

gcc: poison-system-directories Add /sw/include and /opt/include based on the original zecke-no-host-includes.patch patch. The original patch checked for /usr/include, /sw/include and /opt/include and then triggered a failure and aborted. Instead, we add the two missing items to the current scan. If the user wants this to be a failure, they can add "-Werror=poison-system-directories". Upstream-Status: Pending Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha a01fbf464f057a0e02ead8a752fc0f4631a122f6

gcc-4.3.3: SYSROOT_CFLAGS_FOR_TARGET Before committing, I noticed that PR/32161 was marked as a dup of PR/32009, but my previous patch did not fix it. This alternative patch is better because it lets you just use CFLAGS_FOR_TARGET to set the compilation flags for libgcc. Since bootstrapped target libraries are never compiled with the native compiler, it makes little sense to use different flags for stage1 and later stages. And it also makes little sense to use a different variable than CFLAGS_FOR_TARGET. Other changes I had to do include: - moving the creation of default CFLAGS_FOR_TARGET from Makefile.am to configure.ac, because otherwise the BOOT_CFLAGS are substituted into CFLAGS_FOR_TARGET (which is "-O2 -g $(CFLAGS)") via $(CFLAGS). It is also cleaner this way though. - passing the right CFLAGS to configure scripts as exported environment variables I also stopped passing LIBCFLAGS to configure scripts since they are unused in the whole src tree. And I updated the documentation as H-P reminded me to do. Bootstrapped/regtested i686-pc-linux-gnu, will commit to 4.4 shortly. Ok for 4.3? Signed-off-by: Paolo Bonzini <bonzini@gnu.org> Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha 420f71a75c16106eacac090afa538e5fe49a3105

64-bit multilib hack. GCC has internal multilib handling code but it assumes a very specific rigid directory layout. The build system implementation of multilib layout is very generic and allows complete customisation of the library directories. This patch is a partial solution to allow any custom directories to be passed into gcc and handled correctly. It forces gcc to use the base_libdir (which is the current directory, "."). We need to do this for each multilib that is configured as we don't know which compiler options may be being passed into the compiler. Since we have a compiler per mulitlib at this point that isn't an issue. The one problem is the target compiler is only going to work for the default multlilib at this point. Ideally we'd figure out which multilibs were being enabled with which paths and be able to patch these entries with a complete set of correct paths but this we don't have such code at this point. This is something the target gcc recipe should do and override these platform defaults in its build config. Do same for riscv64, aarch64 & arc RP 15/8/11 Upstream-Status: Inappropriate[OE-Specific] Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Elvis Dowson <elvis.dowson@gmail.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 2a013edccc02568c7b3d7f0d14423aa4f11bebe2

optional libstdc gcc-runtime builds libstdc++ separately from gcc-cross-*. Its configure tests using g++ will not run correctly since by default the linker will try to link against libstdc++ which shouldn't exist yet. We need an option to disable -lstdc++ option whilst leaving -lc, -lgcc and other automatic library dependencies added by gcc driver. This patch adds such an option which only disables the -lstdc++. A "standard" gcc build uses xgcc and hence avoids this. We should ask upstream how to do this officially, the likely answer is don't build libstdc++ separately. RP 29/6/10 Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [embedded specific]

view details

Khem Raj

commit sha ab66e49231d2de6841a3b830abede9e8a75cd6a5

COLLECT_GCC_OPTIONS This patch adds --sysroot into COLLECT_GCC_OPTIONS which is used to invoke collect2. Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha d0d16cc78291d01b216207bb0cdd098abcdbb757

Use the defaults.h in ${B} instead of ${S}, and t-oe in ${B} Use the defaults.h in ${B} instead of ${S}, and t-oe in ${B}, so that the source can be shared between gcc-cross-initial, gcc-cross-intermediate, gcc-cross, gcc-runtime, and also the sdk build. Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending While compiling gcc-crosssdk-initial-x86_64 on some host, there is occasionally failure that test the existance of default.h doesn't work, the reason is tm_include_list='** defaults.h' rather than tm_include_list='** ./defaults.h' So we add the test condition for this situation. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>

view details

Khem Raj

commit sha 2a07947541f97c98fb800898001466c07fac3d7b

fortran cross-compile hack. * Fortran would have searched for arm-angstrom-gnueabi-gfortran but would have used used gfortan. For gcc_4.2.2.bb we want to use the gfortran compiler from our cross directory. Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [embedded specific]

view details

Khem Raj

commit sha b39aabfe82bb0462c3b8e7a26bc00e30634e8c2c

cpp: honor sysroot. Currently, if the gcc toolchain is relocated and installed from sstate, then you try and compile preprocessed source (.i or .ii files), the compiler will try and access the builtin sysroot location rather than the --sysroot option specified on the commandline. If access to that directory is permission denied (unreadable), gcc will error. This happens when ccache is in use due to the fact it uses preprocessed source files. The fix below adds %I to the cpp-output spec macro so the default substitutions for -iprefix, -isystem, -isysroot happen and the correct sysroot is used. [YOCTO #2074] RP 2012/04/13 Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha 0c043eeac259851e62a73e410d5dbc1d600b75b8

MIPS64: Default to N64 ABI MIPS64 defaults to n32 ABI, this patch makes it so that it defaults to N64 ABI Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [OE config specific]

view details

Khem Raj

commit sha c9b65d5f817f67b81ce3a706d9d57b0d33c4db2e

Define GLIBC_DYNAMIC_LINKER and UCLIBC_DYNAMIC_LINKER relative to SYSTEMLIBS_DIR This patch defines GLIBC_DYNAMIC_LINKER and UCLIBC_DYNAMIC_LINKER relative to SYSTEMLIBS_DIR which can be set in generated headers This breaks the assumption of hardcoded multilib in gcc Change is only for the supported architectures in OE including SH, sparc, alpha for possible future support (if any) Removes the do_headerfix task in metadata Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Inappropriate [OE configuration]

view details

Khem Raj

commit sha f411708df3d4fedb3db548fffc71bce77b172c73

gcc: Fix argument list too long error. There would be an "Argument list too long" error when the build directory is longer than 200, this is caused by: headers=`echo $(PLUGIN_HEADERS) | tr ' ' '\012' | sort -u` The PLUGIN_HEADERS is too long before sort, so the "echo" can't handle it, use the $(sort list) of GNU make which can handle the too long list would fix the problem, the header would be short enough after sorted. The "tr ' ' '\012'" was used for translating the space to "\n", the $(sort list) doesn't need this. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> RP: gcc then added *.h and *.def additions to this list, breaking the original fix. Add the sort to the original gcc code, leaving the tr+sort to fix the original issue but include the new files too as reported by Zhuang <qiuguang.zqg@alibaba-inc.com> Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha ce1db5549b298af40b3b6fbaa1d4543e42b2546f

Disable sdt. We don't list dtrace in DEPENDS so we shouldn't be depending on this header. It may or may not exist from preivous builds though. To be determinstic, disable sdt.h usage always. This avoids build failures if the header is removed after configure but before libgcc is compiled for example. RP 2012/8/7 Signed-off-by: Khem Raj <raj.khem@gmail.com> Disable sdt for libstdc++-v3. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Upstream-Status: Inappropriate [hack]

view details

Khem Raj

commit sha 75bac8d4d994f81b9774f3eb66949600800bde0c

libtool libstdc++ from gcc-runtime gets created with -rpath=/usr/lib/../lib for qemux86-64 when running on am x86_64 build host. This patch stops this speading to libdir in the libstdc++.la file within libtool. Arguably, it shouldn't be passing this into libtool in the first place but for now this resolves the nastiest problems this causes. func_normal_abspath would resolve an empty path to `pwd` so we need to filter the zero case. RP 2012/8/24 Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha e12b933c07db9f0b7ca6d1f9e02d33648d35bcdf

gcc: armv4: pass fix-v4bx to linker to support EABI. The LINK_SPEC for linux gets overwritten by linux-eabi.h which means the value of TARGET_FIX_V4BX_SPEC gets lost and as a result the option is not passed to linker when chosing march=armv4 This patch redefines this in linux-eabi.h and reinserts it for eabi defaulting toolchains. We might want to send it upstream. Signed-off-by: Khem Raj <raj.khem@gmail.com> Upstream-Status: Pending

view details

Khem Raj

commit sha fd74384bb95294d33ab85456e8ebf5e816e2ad77

Use the multilib config files from ${B} instead of using the ones from ${S} Use the multilib config files from ${B} instead of using the ones from ${S} so that the source can be shared between gcc-cross-initial, gcc-cross-intermediate, gcc-cross, gcc-runtime, and also the sdk build. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Upstream-Status: Inappropriate [configuration]

view details

Khem Raj

commit sha 9cd01734bfd3573d15eaa690e97fe9876ad29864

Avoid using libdir from .la which usually points to a host path Upstream-Status: Inappropriate [embedded specific] Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha cdc67534fc41c2b86a79d777e7dae00447b36b76

export CPP The OE environment sets and exports CPP as being the target gcc. When building gcc-cross-canadian for a mingw targetted sdk, the following can be found in build.x86_64-pokysdk-mingw32.i586-poky-linux/build-x86_64-linux/libiberty/config.log: configure:3641: checking for _FILE_OFFSET_BITS value needed for large files configure:3666: gcc -c -isystem/media/build1/poky/build/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe conftest.c >&5 configure:3666: $? = 0 configure:3698: result: no configure:3786: checking how to run the C preprocessor configure:3856: result: x86_64-pokysdk-mingw32-gcc -E --sysroot=/media/build1/poky/build/tmp/sysroots/x86_64-nativesdk-mingw32-pokysdk-mingw32 configure:3876: x86_64-pokysdk-mingw32-gcc -E --sysroot=/media/build1/poky/build/tmp/sysroots/x86_64-nativesdk-mingw32-pokysdk-mingw32 conftest.c configure:3876: $? = 0 Note this is a *build* target (in build-x86_64-linux) so it should be using the host "gcc", not x86_64-pokysdk-mingw32-gcc. Since the mingw32 headers are very different, using the wrong cpp is a real problem. It is leaking into configure through the CPP variable. Ultimately this leads to build failures related to not being able to include a process.h file for pem-unix.c. The fix is to ensure we export a sane CPP value into the build environment when using build targets. We could define a CPP_FOR_BUILD value which may be the version which needs to be upstreamed but for now, this fix is good enough to avoid the problem. RP 22/08/2013 Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha e891ddb594cc71afe9684e2471f9cc8d913bf8be

Ensure target gcc headers can be included There are a few headers installed as part of the OpenEmbedded gcc-runtime target (omp.h, ssp/*.h). Being installed from a recipe built for the target architecture, these are within the target sysroot and not cross/nativesdk; thus they weren't able to be found by gcc with the existing search paths. Add support for picking up these headers under the sysroot supplied on the gcc command line in order to resolve this. Extend target gcc headers search to musl too Upstream-Status: Pending Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventkraj/binutils-gdb

Tom Tromey

commit sha 334381ea466c4735fe533a9864991b862c094b60

Style the "XXX" text in ptype/o This patch changes gdb to use the 'highlight' style on the "XXX" text in the output of ptype/o.

view details

Tom Tromey

commit sha 184ea2f7316c54dd5e0fa84f1fe07a222e8fb44c

Remove defaulted 'tid' parameter to ptid_t constructor I wanted to find, and potentially modify, all the spots where the 'tid' parameter to the ptid_t constructor was used. So, I temporarily removed this parameter and then rebuilt. In order to make it simpler to search through the "real" (nonzero) uses of this parameter, something I knew I'd have to do multiple times, I removed any ", 0" from constructor calls. Co-Authored-By: John Baldwin <jhb@FreeBSD.org>

view details

Tom Tromey

commit sha 96bbe3ef9653e23a17b2315627e0cab441815f2d

Change ptid_t::tid to ULONGEST The ptid_t 'tid' member is normally used as an address in gdb -- both bsd-uthread and ravenscar-thread use it this way. However, because the type is 'long', this can cause problems with sign extension. This patch changes the type to ULONGEST to ensure that sign extension does not occur.

view details

Tom Tromey

commit sha c80e29dba968beca5eee7210d2030d27fe7790c3

Change get_ada_task_ptid parameter type get_ada_task_ptid currently takes a 'long' as its 'thread' parameter type. However, on some platforms this is actually a pointer, and using 'long' can sometimes end up with the value being sign-extended. This sign extension can cause problems later, if the tid is then later used as an address again. This patch changes the parameter type to ULONGEST and updates all the uses. This approach preserves sign extension on the targets where it is apparently intended, while avoiding it on others. Co-Authored-By: John Baldwin <jhb@FreeBSD.org>

view details

Pedro Alves

commit sha 9b8efa2cd14410cb23d8873fd8f0665155569523

Test that frame info/IDs are stable/consistent This adds a testcase that tests that the unwinder produces consistent frame info and frame IDs by making sure that "info frame" shows the same result when stopped at a function (level == 0), compared to when we find the same frame in the stack at a level > 0. E.g., on x86-64, right after running to main, we see: (gdb) info frame Stack level 0, frame at 0x7fffffffd340: rip = 0x555555555168 in main (gdb.base/backtrace.c:41); saved rip = 0x7ffff7dd90b3 source language c. Arglist at 0x7fffffffd330, args: Locals at 0x7fffffffd330, Previous frame's sp is 0x7fffffffd340 Saved registers: rbp at 0x7fffffffd330, rip at 0x7fffffffd338 (gdb) and then after continuing to a function called by main, and selecting the "main" frame again, we see: (gdb) info frame Stack level 3, frame at 0x7fffffffd340: rip = 0x555555555172 in main (gdb.base/backtrace.c:41); saved rip = 0x7ffff7dd90b3 caller of frame at 0x7fffffffd330 source language c. Arglist at 0x7fffffffd330, args: Locals at 0x7fffffffd330, Previous frame's sp is 0x7fffffffd340 Saved registers: rbp at 0x7fffffffd330, rip at 0x7fffffffd338 (gdb) The only differences should be in the stack level, the 'rip = ' address, and the presence of the "caller of frame at" info. All the rest should be the same. If it isn't, it probably means that the frame base, the frame ID, etc. aren't stable & consistent. The testcase exercises both the DWARF and the heuristic unwinders, using "maint set dwarf unwinder on/off". Tested on {x86-64 -m64, x86-64 -m32, Aarch64, Power8} GNU/Linux. Change-Id: I795001c82cc70d543d197415e3f80ce5dc7f3452

view details

Tom de Vries

commit sha 04739cc7ce5a5c67d8d841541a4aaef706c53a79

[gdb/testsuite] Use early-out style in gdb.base/break-probes.exp Reduce indentation and improve readability in test-case gdb.base/break-probes.exp by replacing: ... if { <cond> } { <lots-of-code> } ... with: ... if { ! <cond> } { return -1 } <lots-of-code> ... Tested on x86_64-linux.

view details

Tom de Vries

commit sha 108e60844c6c517895011f46b74db6b10273be56

[gdb/testsuite] Handle failing probe detection in gdb.base/break-probes.exp When running test-case gdb.base/break-probes.exp on ubuntu 18.04.5, we have: ... (gdb) bt^M #0 0x00007ffff7dd6e12 in ?? () from /lib64/ld-linux-x86-64.so.2^M #1 0x00007ffff7dedf50 in ?? () from /lib64/ld-linux-x86-64.so.2^M #2 0x00007ffff7dd5128 in ?? () from /lib64/ld-linux-x86-64.so.2^M #3 0x00007ffff7dd4098 in ?? () from /lib64/ld-linux-x86-64.so.2^M #4 0x0000000000000001 in ?? ()^M #5 0x00007fffffffdaac in ?? ()^M #6 0x0000000000000000 in ?? ()^M (gdb) FAIL: gdb.base/break-probes.exp: ensure using probes ... The test-case intends to emit an UNTESTED in this case, but fails to do so because it tries to do it in a regexp clause in a gdb_test_multiple, which doesn't trigger. Instead, a default clause triggers which produces the FAIL. Also the use of UNTESTED is not appropriate, and we should use UNSUPPORTED instead. Fix this by silencing the FAIL, and emitting an UNSUPPORTED after the gdb_test_multiple: ... if { ! $using_probes } { + unsupported "probes not present on this system" return -1 } ... Tested on x86_64-linux.

view details

Tom de Vries

commit sha d264c39e8b3eba663c8f09f228ca44eb36eac778

[gdb/testsuite] Improve probe detection in gdb.base/break-probes.exp When running test-case gdb.base/break-probes.exp on ubuntu 18.04.5, we have: ... (gdb) run^M Starting program: break-probes^M Stopped due to shared library event (no libraries added or removed)^M (gdb) bt^M #0 0x00007ffff7dd6e12 in ?? () from /lib64/ld-linux-x86-64.so.2^M #1 0x00007ffff7dedf50 in ?? () from /lib64/ld-linux-x86-64.so.2^M #2 0x00007ffff7dd5128 in ?? () from /lib64/ld-linux-x86-64.so.2^M #3 0x00007ffff7dd4098 in ?? () from /lib64/ld-linux-x86-64.so.2^M #4 0x0000000000000001 in ?? ()^M #5 0x00007fffffffdaac in ?? ()^M #6 0x0000000000000000 in ?? ()^M (gdb) UNSUPPORTED: gdb.base/break-probes.exp: probes not present on this system ... Using the backtrace, the test-case tries to establish that we're stopped in dl_main, which is used as proof that we're using probes. However, the backtrace only shows an address, because: - the dynamic linker contains no minimal symbols and no debug info, and - gdb is build without --with-separate-debug-dir so it can't find the corresponding .debug file, which does contain the mimimal symbols and debug info. Fix this by instead printing the pc and grepping for the value in the info probes output: ... (gdb) p /x $pc^M $1 = 0x7ffff7dd6e12^M (gdb) info probes^M Type Provider Name Where Object ^M ... stap rtld init_start 0x00007ffff7dd6e12 /lib64/ld-linux-x86-64.so.2 ^M ... (gdb) ... Tested on x86_64-linux.

view details

Tom de Vries

commit sha 508109612f99513f523e2295d86133a71418c010

[gdb/testsuite] Fix probe test in gdb.base/break-interp.exp When running test-case gdb.base/break-interp.exp on ubuntu 18.04.5, we have: ... (gdb) bt^M #0 0x00007eff7ad5ae12 in ?? () from break-interp-LDprelinkNOdebugNO^M #1 0x00007eff7ad71f50 in ?? () from break-interp-LDprelinkNOdebugNO^M #2 0x00007eff7ad59128 in ?? () from break-interp-LDprelinkNOdebugNO^M #3 0x00007eff7ad58098 in ?? () from break-interp-LDprelinkNOdebugNO^M #4 0x0000000000000002 in ?? ()^M #5 0x00007fff505d7a32 in ?? ()^M #6 0x00007fff505d7a94 in ?? ()^M #7 0x0000000000000000 in ?? ()^M (gdb) FAIL: gdb.base/break-interp.exp: ldprelink=NO: ldsepdebug=NO: \ first backtrace: dl bt ... Using the backtrace, the test-case tries to establish that we're stopped in dl_main. However, the backtrace only shows an address, because: - the dynamic linker contains no minimal symbols and no debug info, and - gdb is build without --with-separate-debug-dir so it can't find the corresponding .debug file, which does contain the mimimal symbols and debug info. As in "[gdb/testsuite] Improve probe detection in gdb.base/break-probes.exp", fix this by doing info probes and grepping for the address. Tested on x86_64-linux.

view details

Tom de Vries

commit sha 6ef69a3ff3f5b2483893c6ce611977a1418de2f6

[gdb/testsuite] Use pie instead of -fPIE -pie Replace {additional_flags=-fPIE ldflags=-pie} with {pie}. This makes sure that the test-cases properly error out when using target board unix/-fno-PIE/-no-pie. Tested on x86_64-linux.

view details

Tom de Vries

commit sha 0086a91ceef5207463a10c875ed85c40eb066722

[gdb/testsuite] Support -fPIE/-fno-PIE/-pie/-no-pie in gdb_compile_rust When running gdb.rust/*.exp test-cases with target board unix/-fPIE/-pie, I run into: ... builtin_spawn -ignore SIGHUP rustc --color never gdb.rust/watch.rs \ -g -lm -fPIE -pie -o outputs/gdb.rust/watch/watch^M error: Unrecognized option: 'f'^M ^M compiler exited with status 1 ... The problem is that -fPIE and -fpie are gcc options, but for rust we use rustc, which has different compilation options. Fix this by translating the gcc options to rustc options in gdb_compile_rust, similar to how that is done for ada in target_compile_ada_from_dir. Likewise for unix/-fno-PIE/-no-pie. Tested on x86_64-linux, with: - native - unix/-fPIE/-pie - unix/-fno-PIE/-no-pie specifically, on openSUSE Leap 15.2 both with package gcc-PIE: - installed (making gcc default to PIE) - uninstalled (making gcc default to non-PIE). and rustc 1.52.1.

view details

Tom Tromey

commit sha 809f3be12c0621cbf071c585da5638f6841c38b1

Change pointer_type to a method of struct type I noticed that pointer_type is declared in language.h and defined in language.c. However, it really has to do with types, so it should have been in gdbtypes.h all along. This patch changes it to be a method on struct type. And, I went through uses of TYPE_IS_REFERENCE and updated many spots to use the new method as well. (I didn't update ones that were in arch-specific code, as I couldn't readily test that.)

view details

GDB Administrator

commit sha 3814a9e1fe77c01c7e872c25afa198537d4ac780

Automatic date update in version.in

view details

Khem Raj

commit sha 79767f7d91c8d0761c5d7c22af9cc62c3aa9b5e0

make man install relative to DESTDIR Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha a8f8306698330c15fbde98eacdfb31de529740c5

mips-linux-nat: Define _ABIO32 if not defined This helps building gdb on mips64 on musl, since musl does not provide sgidefs.h this define is only defined when GCC is using o32 ABI, in that case gcc emits it as built-in define and hence it works ok for mips32 Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 18634cf94d41f6f559e7cb20eb421d0496f193bb

ppc/ptrace: Define pt_regs uapi_pt_regs on !GLIBC systems Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 89ce6f020c8ba10dfd210db96f0a6ddcab06e641

Add support for Renesas SH (sh4) architecture. gdb (7.4-1~cvs20111117.2) experimental; urgency=low . * Add Renesas SH (sh4) support (Closes: #576242) - Thanks Nobuhiro Iwamatsu, Takashi Yoshii. Author: Hector Oron <zumbi@debian.org> Bug-Debian: http://bugs.debian.org/576242 Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha ab6ed8a49f43e552f4894c45a2e8a905ff757e96

Dont disable libreadline.a when using --disable-static If gdb is configured with --disable-static then this is dutifully passed to readline which then disables libreadline.a, which causes a problem when gdb tries to link against that. To ensure that readline always builds static libraries, pass --enable-static to the sub-configure. Upstream-Status: Pending Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Andre McCurdy

commit sha cedbbd5a3b89d3e54c3041112824cc8c7918670e

use <asm/sgidefs.h> Build fix for MIPS with musl libc The MIPS specific header <sgidefs.h> is provided by glibc and uclibc but not by musl. Regardless of the libc, the kernel headers provide <asm/sgidefs.h> which provides the same definitions, so use that instead. Upstream-Status: Pending Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha c6bdfc2a3ca587ff7f46ae51bbe10847c0c4bcd0

Change order of CFLAGS Lets us override Werror if need be Upstream-Status: Inappropriate Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventkraj/binutils-gdb

GDB Administrator

commit sha ca0a5bdccf4941660cdb23f1f910c17160dca128

Automatic date update in version.in

view details

Khem Raj

commit sha 85a96addc899bd28c8c8faceccfba55db75b7527

binutils-crosssdk: Generate relocatable SDKs This patch will modify the ELF linker scripts so that the crosssdk linker will generate binaries with a 4096 bytes PT_INTERP section. When the binaries will be relocated, at SDK install time, the interpreter path can be easily changed by the relocating script. generate larger .interp section for gold linker as well Upstream-Status: Inappropriate [SDK specific] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 5d8ddc0100b2eb8e27096fefe1ba91d2f5bfd7fa

binutils-cross: Do not generate linker script directories We don't place target libraries within ${exec_prefix}, we'd always place these within the target sysroot within the standard library directories. Worse, the append_to_lib_path code prefixes these paths with the sysroot which makes even less sense. These directories therefore don't make sense in our case and mean we have to relocate all the linker scripts if they're present. Dropping them gives a reasonable performance improvement/simplification. Upstream-Status: Inappropriate RP 2017/01/30 Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Richard Purdie

commit sha 633ea518fef1e1b4773a005c9ec0d881ee546f6b

binutils-nativesdk: Search for alternative ld.so.conf in SDK installation We need binutils to look at our ld.so.conf file within the SDK to ensure we search the SDK's libdirs as well as those from the host system. We therefore pass in the directory to the code using a define, then add it to a section we relocate in a similar way to the way we relocate the gcc internal paths. This ensures that ld works correctly in our buildtools tarball. Standard sysroot relocation doesn't work since we're not in a sysroot, we want to use both the host system and SDK libs. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020/1/17 Upstream-Status: Inappropriate [OE specific tweak] Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 10d3281e1e1d0508d3172db30f63fe9faf961aff

configure: widen the regexp for SH architectures gprof needs to know about uclibc Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 9a1d498c734d949c940c9d31bfbde2fff740f09a

Point scripts location to libdir Upstream-Status: Inappropriate [debian patch] Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 83a5648ae42f650a66df9a2b6883e70a078bb181

Only generate an RPATH entry if LD_RUN_PATH is not empty for cases where -rpath isn't specified. debian (#151024) Upstream-Status: Pending Signed-off-by: Chris Chimelis <chris@debian.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 491148e065a8ea1c91429e813ceceb7fedea4444

don't let the distro compiler point to the wrong installation location Thanks to RP for helping find the source code causing the issue. 2010/08/13 Nitin A Kamble <nitin.a.kamble@intel.com> Upstream-Status: Inappropriate [embedded specific] Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 3f3b4196edf5102ccb0e59d5c7ccd9982dfd91d3

warn for uses of system directories when cross linking 2008-07-02 Joseph Myers <joseph@codesourcery.com> ld/ * ld.h (args_type): Add error_poison_system_directories. * ld.texinfo (--error-poison-system-directories): Document. * ldfile.c (ldfile_add_library_path): Check command_line.error_poison_system_directories. * ldmain.c (main): Initialize command_line.error_poison_system_directories. * lexsup.c (enum option_values): Add OPTION_ERROR_POISON_SYSTEM_DIRECTORIES. (ld_options): Add --error-poison-system-directories. (parse_args): Handle new option. 2007-06-13 Joseph Myers <joseph@codesourcery.com> ld/ * config.in: Regenerate. * ld.h (args_type): Add poison_system_directories. * ld.texinfo (--no-poison-system-directories): Document. * ldfile.c (ldfile_add_library_path): Check command_line.poison_system_directories. * ldmain.c (main): Initialize command_line.poison_system_directories. * lexsup.c (enum option_values): Add OPTION_NO_POISON_SYSTEM_DIRECTORIES. (ld_options): Add --no-poison-system-directories. (parse_args): Handle new option. 2007-04-20 Joseph Myers <joseph@codesourcery.com> Merge from Sourcery G++ binutils 2.17: 2007-03-20 Joseph Myers <joseph@codesourcery.com> Based on patch by Mark Hatle <mark.hatle@windriver.com>. ld/ * configure.in (--enable-poison-system-directories): New option. * configure, config.in: Regenerate. * ldfile.c (ldfile_add_library_path): If ENABLE_POISON_SYSTEM_DIRECTORIES defined, warn for use of /lib, /usr/lib, /usr/local/lib or /usr/X11R6/lib. Upstream-Status: Pending Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 145d6ce99100b632fcc98baea98820741e359368

Change default emulation for mips64*-*-linux we change the default emulations to be N64 instead of N32 Upstream-Status: Inappropriate [ OE configuration Specific] Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 9d889c4dbd0a559bdda8acbabeac7fd7a6ffd62a

Add support for Netlogic XLP Patch From: Nebu Philips <nphilips@netlogicmicro.com> Using the mipsisa64r2nlm target, add support for XLP from Netlogic. Also, update vendor name to NLM wherever applicable. Use 0x00000080 for INSN_XLP, the value 0x00000040 has already been assigned to INSN_OCTEON3 Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Baoshan Pang <baoshan.pang@windriver.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>

view details

Zhenhua Luo

commit sha f304a0b7382096cb9e836c034b55c670cd415564

fix the incorrect assembling for ppc wait mnemonic Signed-off-by: Zhenhua Luo <zhenhua.luo@nxp.com> Upstream-Status: Pending

view details

Khem Raj

commit sha b657e995d8323babdc73aadc391aa3c5e7b29ac2

Detect 64-bit MIPS targets Add mips64 target triplets and default to N64 Upstream-Status: Submitted https://sourceware.org/ml/binutils/2016-08/msg00048.html Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 1316fd575f0da4e07c6cbe2ed1ae46f8217f67d3

Use libtool 2.4 get libtool sysroot support Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 928214291c9f7e0938b1534fb3d796d61440fd3e

Fix rpath in libtool when sysroot is enabled Enabling sysroot support in libtool exposed a bug where the final library had an RPATH encoded into it which still pointed to the sysroot. This works around the issue until it gets sorted out upstream. Fix suggested by Richard Purdie <richard.purdie@linuxfoundation.org> Upstream-Status: Inappropriate [embedded specific] Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Ross Burton

commit sha 127842c94bd86bc6c571c8ca93fcca7bae980b68

sync with OE libtool changes Apply these patches from our libtool patches as not only are redundant RPATHs a waste of space but they can cause incorrect linking when native packages are restored from sstate. fix-rpath.patch: We don't want to add RPATHS which match default linker search paths, they're a waste of space. This patch filters libtools list and removes the ones we don't need. norm-rpath.patch: Libtool may be passed link paths of the form "/usr/lib/../lib", which fool its detection code into thinking it should be included as an RPATH in the generated binary. Normalize before comparision. Upstream-Status: Inappropriate Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 332a69c8421217b2e8f0d6ef8ff50d9de6434c0e

Check for clang before checking gcc version Clang advertises itself to be gcc 4.2.1, so when compiling this test here fails since gcc < 4.4.5 did not support -static-libstdc++ but thats not true for clang, so its better to make an additional check for clang before resorting to gcc version check. This should let clang enable static libstdc++ linking Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventkraj/binutils-gdb

Tom Tromey

commit sha 334381ea466c4735fe533a9864991b862c094b60

Style the "XXX" text in ptype/o This patch changes gdb to use the 'highlight' style on the "XXX" text in the output of ptype/o.

view details

Tom Tromey

commit sha 184ea2f7316c54dd5e0fa84f1fe07a222e8fb44c

Remove defaulted 'tid' parameter to ptid_t constructor I wanted to find, and potentially modify, all the spots where the 'tid' parameter to the ptid_t constructor was used. So, I temporarily removed this parameter and then rebuilt. In order to make it simpler to search through the "real" (nonzero) uses of this parameter, something I knew I'd have to do multiple times, I removed any ", 0" from constructor calls. Co-Authored-By: John Baldwin <jhb@FreeBSD.org>

view details

Tom Tromey

commit sha 96bbe3ef9653e23a17b2315627e0cab441815f2d

Change ptid_t::tid to ULONGEST The ptid_t 'tid' member is normally used as an address in gdb -- both bsd-uthread and ravenscar-thread use it this way. However, because the type is 'long', this can cause problems with sign extension. This patch changes the type to ULONGEST to ensure that sign extension does not occur.

view details

Tom Tromey

commit sha c80e29dba968beca5eee7210d2030d27fe7790c3

Change get_ada_task_ptid parameter type get_ada_task_ptid currently takes a 'long' as its 'thread' parameter type. However, on some platforms this is actually a pointer, and using 'long' can sometimes end up with the value being sign-extended. This sign extension can cause problems later, if the tid is then later used as an address again. This patch changes the parameter type to ULONGEST and updates all the uses. This approach preserves sign extension on the targets where it is apparently intended, while avoiding it on others. Co-Authored-By: John Baldwin <jhb@FreeBSD.org>

view details

Pedro Alves

commit sha 9b8efa2cd14410cb23d8873fd8f0665155569523

Test that frame info/IDs are stable/consistent This adds a testcase that tests that the unwinder produces consistent frame info and frame IDs by making sure that "info frame" shows the same result when stopped at a function (level == 0), compared to when we find the same frame in the stack at a level > 0. E.g., on x86-64, right after running to main, we see: (gdb) info frame Stack level 0, frame at 0x7fffffffd340: rip = 0x555555555168 in main (gdb.base/backtrace.c:41); saved rip = 0x7ffff7dd90b3 source language c. Arglist at 0x7fffffffd330, args: Locals at 0x7fffffffd330, Previous frame's sp is 0x7fffffffd340 Saved registers: rbp at 0x7fffffffd330, rip at 0x7fffffffd338 (gdb) and then after continuing to a function called by main, and selecting the "main" frame again, we see: (gdb) info frame Stack level 3, frame at 0x7fffffffd340: rip = 0x555555555172 in main (gdb.base/backtrace.c:41); saved rip = 0x7ffff7dd90b3 caller of frame at 0x7fffffffd330 source language c. Arglist at 0x7fffffffd330, args: Locals at 0x7fffffffd330, Previous frame's sp is 0x7fffffffd340 Saved registers: rbp at 0x7fffffffd330, rip at 0x7fffffffd338 (gdb) The only differences should be in the stack level, the 'rip = ' address, and the presence of the "caller of frame at" info. All the rest should be the same. If it isn't, it probably means that the frame base, the frame ID, etc. aren't stable & consistent. The testcase exercises both the DWARF and the heuristic unwinders, using "maint set dwarf unwinder on/off". Tested on {x86-64 -m64, x86-64 -m32, Aarch64, Power8} GNU/Linux. Change-Id: I795001c82cc70d543d197415e3f80ce5dc7f3452

view details

Tom de Vries

commit sha 04739cc7ce5a5c67d8d841541a4aaef706c53a79

[gdb/testsuite] Use early-out style in gdb.base/break-probes.exp Reduce indentation and improve readability in test-case gdb.base/break-probes.exp by replacing: ... if { <cond> } { <lots-of-code> } ... with: ... if { ! <cond> } { return -1 } <lots-of-code> ... Tested on x86_64-linux.

view details

Tom de Vries

commit sha 108e60844c6c517895011f46b74db6b10273be56

[gdb/testsuite] Handle failing probe detection in gdb.base/break-probes.exp When running test-case gdb.base/break-probes.exp on ubuntu 18.04.5, we have: ... (gdb) bt^M #0 0x00007ffff7dd6e12 in ?? () from /lib64/ld-linux-x86-64.so.2^M #1 0x00007ffff7dedf50 in ?? () from /lib64/ld-linux-x86-64.so.2^M #2 0x00007ffff7dd5128 in ?? () from /lib64/ld-linux-x86-64.so.2^M #3 0x00007ffff7dd4098 in ?? () from /lib64/ld-linux-x86-64.so.2^M #4 0x0000000000000001 in ?? ()^M #5 0x00007fffffffdaac in ?? ()^M #6 0x0000000000000000 in ?? ()^M (gdb) FAIL: gdb.base/break-probes.exp: ensure using probes ... The test-case intends to emit an UNTESTED in this case, but fails to do so because it tries to do it in a regexp clause in a gdb_test_multiple, which doesn't trigger. Instead, a default clause triggers which produces the FAIL. Also the use of UNTESTED is not appropriate, and we should use UNSUPPORTED instead. Fix this by silencing the FAIL, and emitting an UNSUPPORTED after the gdb_test_multiple: ... if { ! $using_probes } { + unsupported "probes not present on this system" return -1 } ... Tested on x86_64-linux.

view details

Tom de Vries

commit sha d264c39e8b3eba663c8f09f228ca44eb36eac778

[gdb/testsuite] Improve probe detection in gdb.base/break-probes.exp When running test-case gdb.base/break-probes.exp on ubuntu 18.04.5, we have: ... (gdb) run^M Starting program: break-probes^M Stopped due to shared library event (no libraries added or removed)^M (gdb) bt^M #0 0x00007ffff7dd6e12 in ?? () from /lib64/ld-linux-x86-64.so.2^M #1 0x00007ffff7dedf50 in ?? () from /lib64/ld-linux-x86-64.so.2^M #2 0x00007ffff7dd5128 in ?? () from /lib64/ld-linux-x86-64.so.2^M #3 0x00007ffff7dd4098 in ?? () from /lib64/ld-linux-x86-64.so.2^M #4 0x0000000000000001 in ?? ()^M #5 0x00007fffffffdaac in ?? ()^M #6 0x0000000000000000 in ?? ()^M (gdb) UNSUPPORTED: gdb.base/break-probes.exp: probes not present on this system ... Using the backtrace, the test-case tries to establish that we're stopped in dl_main, which is used as proof that we're using probes. However, the backtrace only shows an address, because: - the dynamic linker contains no minimal symbols and no debug info, and - gdb is build without --with-separate-debug-dir so it can't find the corresponding .debug file, which does contain the mimimal symbols and debug info. Fix this by instead printing the pc and grepping for the value in the info probes output: ... (gdb) p /x $pc^M $1 = 0x7ffff7dd6e12^M (gdb) info probes^M Type Provider Name Where Object ^M ... stap rtld init_start 0x00007ffff7dd6e12 /lib64/ld-linux-x86-64.so.2 ^M ... (gdb) ... Tested on x86_64-linux.

view details

Tom de Vries

commit sha 508109612f99513f523e2295d86133a71418c010

[gdb/testsuite] Fix probe test in gdb.base/break-interp.exp When running test-case gdb.base/break-interp.exp on ubuntu 18.04.5, we have: ... (gdb) bt^M #0 0x00007eff7ad5ae12 in ?? () from break-interp-LDprelinkNOdebugNO^M #1 0x00007eff7ad71f50 in ?? () from break-interp-LDprelinkNOdebugNO^M #2 0x00007eff7ad59128 in ?? () from break-interp-LDprelinkNOdebugNO^M #3 0x00007eff7ad58098 in ?? () from break-interp-LDprelinkNOdebugNO^M #4 0x0000000000000002 in ?? ()^M #5 0x00007fff505d7a32 in ?? ()^M #6 0x00007fff505d7a94 in ?? ()^M #7 0x0000000000000000 in ?? ()^M (gdb) FAIL: gdb.base/break-interp.exp: ldprelink=NO: ldsepdebug=NO: \ first backtrace: dl bt ... Using the backtrace, the test-case tries to establish that we're stopped in dl_main. However, the backtrace only shows an address, because: - the dynamic linker contains no minimal symbols and no debug info, and - gdb is build without --with-separate-debug-dir so it can't find the corresponding .debug file, which does contain the mimimal symbols and debug info. As in "[gdb/testsuite] Improve probe detection in gdb.base/break-probes.exp", fix this by doing info probes and grepping for the address. Tested on x86_64-linux.

view details

Tom de Vries

commit sha 6ef69a3ff3f5b2483893c6ce611977a1418de2f6

[gdb/testsuite] Use pie instead of -fPIE -pie Replace {additional_flags=-fPIE ldflags=-pie} with {pie}. This makes sure that the test-cases properly error out when using target board unix/-fno-PIE/-no-pie. Tested on x86_64-linux.

view details

Tom de Vries

commit sha 0086a91ceef5207463a10c875ed85c40eb066722

[gdb/testsuite] Support -fPIE/-fno-PIE/-pie/-no-pie in gdb_compile_rust When running gdb.rust/*.exp test-cases with target board unix/-fPIE/-pie, I run into: ... builtin_spawn -ignore SIGHUP rustc --color never gdb.rust/watch.rs \ -g -lm -fPIE -pie -o outputs/gdb.rust/watch/watch^M error: Unrecognized option: 'f'^M ^M compiler exited with status 1 ... The problem is that -fPIE and -fpie are gcc options, but for rust we use rustc, which has different compilation options. Fix this by translating the gcc options to rustc options in gdb_compile_rust, similar to how that is done for ada in target_compile_ada_from_dir. Likewise for unix/-fno-PIE/-no-pie. Tested on x86_64-linux, with: - native - unix/-fPIE/-pie - unix/-fno-PIE/-no-pie specifically, on openSUSE Leap 15.2 both with package gcc-PIE: - installed (making gcc default to PIE) - uninstalled (making gcc default to non-PIE). and rustc 1.52.1.

view details

Tom Tromey

commit sha 809f3be12c0621cbf071c585da5638f6841c38b1

Change pointer_type to a method of struct type I noticed that pointer_type is declared in language.h and defined in language.c. However, it really has to do with types, so it should have been in gdbtypes.h all along. This patch changes it to be a method on struct type. And, I went through uses of TYPE_IS_REFERENCE and updated many spots to use the new method as well. (I didn't update ones that were in arch-specific code, as I couldn't readily test that.)

view details

GDB Administrator

commit sha 3814a9e1fe77c01c7e872c25afa198537d4ac780

Automatic date update in version.in

view details

Khem Raj

commit sha 66a9cbe42d6610a263838f00a58dae20066ae166

binutils-crosssdk: Generate relocatable SDKs This patch will modify the ELF linker scripts so that the crosssdk linker will generate binaries with a 4096 bytes PT_INTERP section. When the binaries will be relocated, at SDK install time, the interpreter path can be easily changed by the relocating script. generate larger .interp section for gold linker as well Upstream-Status: Inappropriate [SDK specific] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 18f5a1ce44d52a5881057bd2f9e2b953d3aee9f2

binutils-cross: Do not generate linker script directories We don't place target libraries within ${exec_prefix}, we'd always place these within the target sysroot within the standard library directories. Worse, the append_to_lib_path code prefixes these paths with the sysroot which makes even less sense. These directories therefore don't make sense in our case and mean we have to relocate all the linker scripts if they're present. Dropping them gives a reasonable performance improvement/simplification. Upstream-Status: Inappropriate RP 2017/01/30 Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Richard Purdie

commit sha fb8a9836a2be50c925744a288998545c7a27d987

binutils-nativesdk: Search for alternative ld.so.conf in SDK installation We need binutils to look at our ld.so.conf file within the SDK to ensure we search the SDK's libdirs as well as those from the host system. We therefore pass in the directory to the code using a define, then add it to a section we relocate in a similar way to the way we relocate the gcc internal paths. This ensures that ld works correctly in our buildtools tarball. Standard sysroot relocation doesn't work since we're not in a sysroot, we want to use both the host system and SDK libs. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2020/1/17 Upstream-Status: Inappropriate [OE specific tweak] Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 70bdbb623765d39b2414aa1d43c070aa99d0f56f

configure: widen the regexp for SH architectures gprof needs to know about uclibc Upstream-Status: Pending Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha cc1d4f6a6658867640e46c84e08983a830252080

Point scripts location to libdir Upstream-Status: Inappropriate [debian patch] Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha c104ab1487cbeba953aac97987ef6951ce237587

Only generate an RPATH entry if LD_RUN_PATH is not empty for cases where -rpath isn't specified. debian (#151024) Upstream-Status: Pending Signed-off-by: Chris Chimelis <chris@debian.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 74e472ac9fd23aa4dbdc48b8f8a1f7229033a2ef

don't let the distro compiler point to the wrong installation location Thanks to RP for helping find the source code causing the issue. 2010/08/13 Nitin A Kamble <nitin.a.kamble@intel.com> Upstream-Status: Inappropriate [embedded specific] Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventYoeDistro/yoe-distro

Khem Raj

commit sha 11b1273da23fdf0e8710c9f6ae6695cb8b19e451

Layer Updates: sources/meta-openembedded sources/openembedded-core * sources/meta-openembedded cf3def588...0be3621c8 (10): > XXX: Add Github actions CI support > vk-gl-cts: fix soname linking > vk-gl-cts: allow the user to specify the target > lmdb: replace tag with commit id in SRCREV > postfix: Add missing dependency on m4 > rdma-core: Inherit pkgconfig < XXX: Add Github actions CI support < postfix: Add missing dependency on m4 < rdma-core: Inherit pkgconfig < vk-gl-cts: allow the user to specify the target * sources/openembedded-core 72d2769061...4a604a2839 (24): > pkgconfig: Update to latest > libseccomp: Upgrade to 2.5.2 and beyond > weston: wrapper for weston modules argument > esdk: locked sig mismatch warnings when build from esdk env > qemux86: Add identical qemux86copy variant for tests > create-spdx: Don't collect natives sources > conf/machine: bump qemu preferred versions to 5.14 > systemtap: update to 4.5-latest > linux-yocto: introduce 5.14 reference kernel > libc-headers: bump to v5.14 > layer.conf: Extend recipes not to install without explict dependencies > lttng-ust: fix do_compile error when PACKAGECONFIG examples is enabled < pkgconfig: Update to latest < libseccomp: Upgrade to 2.5.2 and beyond < weston: wrapper for weston modules argument < esdk: locked sig mismatch warnings when build from esdk env < qemux86: Add identical qemux86copy variant for tests < lttng-ust: fix do_compile error when PACKAGECONFIG examples is enabled < create-spdx: Don't collect natives sources < conf/machine: bump qemu preferred versions to 5.14 < systemtap: update to 4.5-latest < linux-yocto: introduce 5.14 reference kernel < libc-headers: bump to v5.14 < layer.conf: Extend recipes not to install without explict dependencies Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 6 hours

push eventYoeDistro/openembedded-core

Changqing Li

commit sha 907ebb5bb3d44dd5f68deb238098fb6f6413e2d4

lttng-ust: fix do_compile error when PACKAGECONFIG examples is enabled when PACKAGECONFIG enabled examples, compile failed with error: fix below compile error during PACKGAGECONFIG examples is enabled: tmp/work/corei7-64-wrs-linux/lttng-ust/2_2.13.0-r0/recipe-sysroot-native/usr/bin/x86_64-wrs-linux/../../libexec/x86_64-wrs-linux/gcc/x86_64-wrs-linux/11.2.0/ld: warning: liblttng-ust-common.so.1, needed by ../../../src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link) tmp/work/corei7-64-wrs-linux/lttng-ust/2_2.13.0-r0/recipe-sysroot-native/usr/bin/x86_64-wrs-linux/../../libexec/x86_64-wrs-linux/gcc/x86_64-wrs-linux/11.2.0/ld: warning: liblttng-ust-tracepoint.so.1, needed by ../../../src/lib/lttng-ust/.libs/liblttng-ust.so, not found (try using -rpath or -rpath-link) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

view details

Richard Purdie

commit sha abe477d47e4fd85154f05ad3fdc4e9d31a4208fb

layer.conf: Extend recipes not to install without explict dependencies There are several dependencies which recipes have which are not needed at runtime, only at build time. Extend the list of these from bison to include quilt, patch, meson, autoconf, automake and ninja which should reduce the amount of data being included in native sysroots. This speeds up and reduces the sstate needed for image builds for example. If this change breaks recipes, it probably means they're missing an explicit DEPENDS on something in this list which is a bug in the recipe. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

view details

Bruce Ashfield

commit sha d0358ac30fe7c5bfed16d0a202ccd44be72de15a

libc-headers: bump to v5.14 The reference kernel is moving to 5.14, and 5.13 is EOL upstream, so we update the libc-headers to match. No patch issues were found for musl or glibc. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

view details

Bruce Ashfield

commit sha c85fd779de9cbd812d1c498de548550c761960ee

linux-yocto: introduce 5.14 reference kernel Each release of the kernel is not typically used as a versioned reference kernel, but since 5.13 has gone EOL upstream and was never part of a release, we take the opportunity to udpate our reference to 5.14. 5.13 will be removed in subsequent commits, once all dependent BSPs and layers have been updated. No issues were found across all architectures, images in qemu boot testing. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

view details

Bruce Ashfield

commit sha 94f003ab33e12e3722b43b1ea1ce35b2f6d84a39

systemtap: update to 4.5-latest To fix issues with 5.14+ kernels, we bump to the latest 4.5 systemtap. This means that we can drop a backported patch, and we pickup the following changes: 7f6992539 Correct RISC-V handling of SDT markers and document their format. 2dfd140fd Fix races in perf probe task finder callback f463f6053 The /* pc=0x... */ is no longer printed by "stap -v -L 'kernel.function("*")' 0bd97a806 Use task_state tapset function to avoid task_struct changes 4996a29c6 tapset: start adopting kernel netif_* tracepoints in netdev.* tapset fb0851e62 dwflpp.h: add conditional EM_RISCV define c5599df8e Add dwarfless register access for RISC-V 33d861435 Add bactrace support for RISC-V 2ae3fc866 RISC-V dwarf register number to pt_reg mappings 3df603720 Eliminate the sa_restorer field in sigaction struct for RISC-V. a6aff9d33 Avoid generating problematic asynchronous unwind tables on RISC-V a463860c3 Add RISC-V 64-bit processor support 8486fd78d Add the actual RISC-V syscall-number mappings to the tapsets. 1e383aa38 Add creation of mappings between syscall names and numbers for RISC-V aedb2dbe7 RISC-V doesn't have crash available, disable it for rpmbuilds. 33a9bf1a1 Update to newer config.guess to support RISC-V 3bca17469 Use lex_cast instead of to_string when shortening function names. 0b5bc934a Revert "runtime: unregister the control channel before cleaning up" 166a95089 runtime: fix panics when polling on the control channel while unloading e6a1b008b Shorten function names that will exceed the kernel's objtool limit of 128 4f54ba033 runtime/transport: add a comment blurb for ordering invariant at shutdown dbe08f1ac runtime: unregister the control channel before cleaning up 798a67290 bpf pr23478 :: test non-unique key/val iteration 079f5d708 bpf pr23478 :: test multi-key associative array iteration 70b24879d rhbz1938312: un-disable bpf.exp after kernel bugfix 2896d6f5a pr23478 WIP: fixes for existing foreach testcases 0d1a38dbc pr23478 WIP: rework bpf foreach to handle multi-key array 14a2c8f54 Run task_fd_lookup.exp with --compatible 4.0 f2c147767 PR28184: Adapt to kernel rename __fcheck_files to files_lookup_fd_raw 0581a6560 PR28184: Adapt to kernel rename __fcheck_files to files_lookup_fd_raw 559fd51fe testsuite: time-limit auxiliary child processes 5d89bb03e stapbpf bugfix: missing in_block() in try-catch code 04b43f48f releng: ditch custom pie/ssp CFLAGS engine in configure.ac b47d03c20 PR28079: Adapt to kernel 5.14 task_struct.__state change e66f3a83b runtime: adapt to -Werror=implicit-fallthrough=5, dyninst runtime ea00c1070 PR28140: kernel 5.14-rc adaptation, jump_label_patch ffb0a38ea runtime: adapt to -Werror=implicit-fallthrough=5 efba2178f Revert to using test_tsk_thread_flag for uprobes2 23db8b29f PR27984: Adjust the address so dwfl_module_addrinfo finds correct function name a29f65d57 PR28079: Adapt to kernel 5.14 task_struct.__state change 2f7e966c0 testsuite item typo fix 5abb4d130 PR27934: give fuller diagnosis for pass-5 probe-registration errors 371805aa0 PR27820 tapset/bpf/logging.stp: implement abort() tapset function ee361f183 PR27820 tapset/bpf/logging.stp: move bpf versions of functions 968173f7f runtime: linux 5.14 compat: <linux/panic_notifier.h> ef5a8b9ed runtime: fix unintended compile error with autoconf-x86-uniregs.c 84ef6bd9f Revert "systemtap.spec: don't buildrequire emacs" 65fc44163 spin-rawhide: ok tweak the git-archive top level path too c7f1c12e1 spin-rawhide: switch to ~ versioning for Source: file names too bff2b2ff5 spin-rawhide: switch to ~ versioning for n-v-r 7c2751e37 task_finder_vma: add autoconf check for hlist_add_tail_rcu() ea7c27bbe Don't fail vma tracking mmap callback if module is already known. 2eb7fdfdb Use the path instead of the module for vma tracking mmap callback. a5104a612 update READMEs + man pages for freenode -> oftc move 23c351645 Update list of reasons for latencytap.stp example 5409ddea1 rhbz1972805: add basic syscall-in-ptregs support for s390x 0fc73fc4e systemtap.spec: don't Require: libvirt 515a6a2d6 rhbz1972828: tapsets: iommu tracepoints eaf63df6a ppc64 runtime: FULL_REGS() gone 757d4f654 c++ buildability: util.cxx - unique_ptr 1a6e7aea7 systemtap.spec: don't buildrequire emacs 5ff28c970 Allow for adjacent segments belonging to different modules. b1e8cd5de Note that Python is a requirement. 27115ab4c Get the enumerator's enumeration type 1288bee31 testsuite/systemtap.base/perf.sh drop bashism 4755bc453 Add hlist macros for use by hlist_add_tail_rcu bccf5123f parse.cxx: Initialize functioncall synthetic field 9bbee6518 Add hlist_add_tail_rcu for rhel 6. 630e406b8 Don't assume ISO C99 4a3ad3532 Extend vma mapped entries when the address is adjacent. 294b7a53e stap-prep: switch to using main vmlinuz file as debuginfod test download 643351d22 PR27903: grok more glibc dwarf 3a843482a c++11 hygiene: use cxx_override macro for pre-4.7 g++ 3e9bcd7b1 Fix more -Wformat-nonliteral and -Wmismatched-tags when compiling with clang 8e5145ae4 dtrace: Use -o option to specify output file for CPP b3a392975 Fix -Wformat-nonliteral and -Wformat warnings with clang 545535f82 Fix -Woverloaded-virtual warnings when building with clang 0f4bd3219 set2: Return this from assignment operator 6de815bca Add missing copy constructors to set1_ref and set1_const_ref 930b54119 Add some override specifiers where missing 14f04522b util.cxx: Use abs() instead of labs() 13016e9dd systemtap.spec: python3 tweaks 494ece199 PR27864: tolerate loc_unavailable during loc2c transform e8f5c058f autoconf: version bumps for the next release-4.6 77abac91d version bumps for the next release-4.6 0eba8a46b NEWS: release-4.5 Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

view details

Bruce Ashfield

commit sha 2987f5afb258728daccc3a1e421530e7f32e2553

conf/machine: bump qemu preferred versions to 5.14 5.14 is the latest reference kernel, so let's make it the default. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

view details

Saul Wold

commit sha bfd5087bfc40e10fc5eb911b2cf47878a45c146c

create-spdx: Don't collect natives sources When the collect_dep_sources() runs, it collects sources from both native and non-native recipes. Later when the GENERATED_FROM matching occurs it may find the file (via checksum) from the native recipe since it's the same checksum as the target file. The that are generated DocumentRefs point to the native recipe rather than the target recipe DocumentRef. Signed-off-by: Saul Wold <saul.wold@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

view details

Martin Jansa

commit sha b0765d75881301e16efd44320d7688ec6ec9737a

qemux86: Add identical qemux86copy variant for tests Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>

view details

Mani Selvaraj

commit sha a9bcf61c69389c3cc670c85a6d14e75080ba9c17

esdk: locked sig mismatch warnings when build from esdk env A repo with multiple layers are placed under /layers/ and a repo with single layer is placed under /layers/openembedded-core in esdk. This tiggered locked sig mismatch warnings when building image from esdk environment. ----- TOPDIR=/Code/build corebase=/Code/openembedded-core ----- /Code/meta-java /Code/meta-gplv2 /Code/meta-openembedded/meta-webserver /Code/meta-openembedded/meta-oe /Code/openembedded-core/meta Are moved to /sdk_org/layers/openembedded-core/meta-gplv2 /sdk_org/layers/openembedded-core/meta-java /sdk_org/layers/meta-openembedded/meta-webserver /sdk_org/layers/meta-openembedded/meta-oe /sdk_org/layers/openembedded-core/meta here fix it to move all layers under /layers dir. to check this fix build image from esdk environment and check for sig mismatch warnings. Signed-off-by: Mani Selvaraj <mani_selvaraj@comcast.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Pavel Zhukov

commit sha f5574689e148cbc4f9ad979918bd25f165a6256f

weston: wrapper for weston modules argument Due to custom option parser implementation weston accepts only one argument of a given type. As the result if multiple modules add multiple --modules agruments only last will be used. This fix introduces wrapper around modules in terms of weston-init to prepare proper modules argument for weston and adds systemd-notify module into weston-init module to support Type=notify in systemd service file. Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha b12176965f774bc9afa56cf4368f543d029e4597

libseccomp: Upgrade to 2.5.2 and beyond Forward port the rv32 port Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 4a604a28390a24081de1cf621fabd0e477c3c308

pkgconfig: Update to latest Brings following change * d97db4f Update URL for bug reporting * eb866ad Spelling and grammar in pkg.m4 * 1f81c80 Fix spelling of rra's name * 350515e Use https for developer.gnome.org URL * 834ecc2 Update bug reporting URL to point to gitlab * 38936b2 Call setlocale in main function * 2ad16fa pkg: Make ordering of output from print_package_list() deterministic * 2dd2b19 parse: Don't emit unknown keyword warning for Libs.private Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 7 hours

push eventYoeDistro/meta-openembedded

Khem Raj

commit sha 1d51730759ae02eeba58ec601ab87cbadb49bc10

rdma-core: Inherit pkgconfig fixes CMake Error at /home/pokybuild/yocto-worker/meta-oe/build/build/tmp/work/core2-64-poky-linux/rdma-core/36.0-r0/recipe-sysroot-native/usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message): | Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 132dab0f2045505880e92e4119a7e20f515e876a

postfix: Add missing dependency on m4 Fixes | extract_cfg.sh: line 42: m4: command not found Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Sakib Sajal

commit sha e7a52e51c7ad1a9e04cf8b882e5380af36d9c988

lmdb: replace tag with commit id in SRCREV Using tag in SRCREV does not work when the git source is added to the PREMIRRORS and set BB_NO_NETWORK = "1". This is because there is no SRCREV, and bitbake needs check the original url to get it. Signed-off-by: Sakib Sajal <sakib.sajal@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Trevor Woerner

commit sha 0b86f2c189fe19fe66dcf113fe15cfbf9d5cda64

vk-gl-cts: allow the user to specify the target When building opengl-es-cts (for example), instead of hard-coding a specific target to build (surfaceless), leave the choice empty by default which instructs the package's build system to search the sysroot and try to determine which target to use (i.e. the "Default" target). Provide overrides (in the form of PACAKGECONFIGs) to allow the user to specify a specific target to build (if they don't want the target selected automatically). Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Trevor Woerner

commit sha a1f60d42898abe5a0ff2e2a9c9c1095d09d0cdc3

vk-gl-cts: fix soname linking The code/build explicitly links to the GL library names instead of their sonames. Update the names that are used for linking so the libraries are found at runtime. Signed-off-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

Khem Raj

commit sha 0be3621c843596a64c4595e14b01fbf1f582ff59

XXX: Add Github actions CI support Add drone build Badge Add yoe.yml for Github actions CI support Signed-off-by: Khem Raj <raj.khem@gmail.com>

view details

push time in 7 hours