diff options
author | Thomas Schwinge <thomas@codesourcery.com> | 2022-11-18 23:57:52 +0100 |
---|---|---|
committer | Thomas Schwinge <thomas@codesourcery.com> | 2022-11-19 15:39:34 +0100 |
commit | dda43e1ef0c9f6c32ad022d3a08ce7651e42a129 (patch) | |
tree | fb60b4ba5b71a65e1859bbd4649f80bf1abe6967 /libstdc++-v3/include/std/complex | |
parent | 5a6c698ea31f587151a2fa4a982c8cc43bd9cc45 (diff) | |
download | gcc-dda43e1ef0c9f6c32ad022d3a08ce7651e42a129.zip gcc-dda43e1ef0c9f6c32ad022d3a08ce7651e42a129.tar.gz gcc-dda43e1ef0c9f6c32ad022d3a08ce7651e42a129.tar.bz2 |
nvptx: In 'STARTFILE_SPEC', fix 'crt0.o' for '-mmainkernel'
A recent nvptx-tools change: commit 886a95faf66bf66a82fc0fe7d2a9fd9e9fec2820
"ld: Don't search for input files in '-L'directories" (of
<https://github.com/MentorEmbedded/nvptx-tools/pull/38>
"Match standard 'ld' "search" behavior") in GCC/nvptx target testing
generally causes linking to fail with:
error opening crt0.o
collect2: error: ld returned 1 exit status
compiler exited with status 1
Indeed per GCC '-v' output, there is an undecorated 'crt0.o' on the linker
('collect2') command line:
[...]/build-gcc/./gcc/collect2 -o [...] crt0.o [...]
This is due to:
gcc/config/nvptx/nvptx.h:#define STARTFILE_SPEC "%{mmainkernel:crt0.o}"
..., and the fix, as used by numerous other GCC targets, is to instead use
'crt0.o%s'; for '%s' means, per 'gcc/gcc.cc', "The Specs Language":
%s current argument is the name of a library or startup file of some sort.
Search for that file in a standard list of directories
and substitute the full name found.
With that, we get the expected path to 'crt0.o'.
gcc/
* config/nvptx/nvptx.h (STARTFILE_SPEC): Fix 'crt0.o' for
'-mmainkernel'.
Diffstat (limited to 'libstdc++-v3/include/std/complex')
0 files changed, 0 insertions, 0 deletions