From: Tom de Vries <tdevries@suse.de>
To: Thomas Schwinge <thomas@codesourcery.com>, gcc-patches@gcc.gnu.org
Cc: reply+AAAFJ6N2QCLFB22I4MIOMNGBQUE7HEVBNHHFNHPAMA@reply.github.com
Subject: Re: nvptx: In 'STARTFILE_SPEC', fix 'crt0.o' for '-mmainkernel' (was: [MentorEmbedded/nvptx-tools] Match standard 'ld' "search" behavior (PR #38))
Date: Sat, 19 Nov 2022 07:35:06 +0100 [thread overview]
Message-ID: <7ef9c0d6-b409-7206-bd76-a84de9b78b33@suse.de> (raw)
In-Reply-To: <87iljbalr7.fsf@dem-tschwing-1.ger.mentorg.com>
On 11/19/22 00:25, Thomas Schwinge wrote:
> Hi!
>
> Re
> <https://github.com/MentorEmbedded/nvptx-tools/pull/38#issuecomment-1320419585>:
>
> On 2022-11-18T11:05:23-0800, I wrote:
>> Actually, in GCC/nvptx target testing, this #38's commit 886a95faf66bf66a82fc0fe7d2a9fd9e9fec2820 "ld: Don't search for input files in '-L'directories" is generally causing linking to fail with:
>>
>> ```
>> error opening crt0.o
>> collect2: error: ld returned 1 exit status
>> compiler exited with status 1
>> ```
>>
>> I'm investigating.
>
> OK to push the attached
> GCC "nvptx: In 'STARTFILE_SPEC', fix 'crt0.o' for '-mmainkernel'" to all
> active GCC branches? (... instead of having to restore this "blunder"
> (do "search for input files in '-L'directories") in nvptx-tools...)
>
Hi,
yes, LGTM.
Thanks,
- Tom
>
> Grüße
> Thomas
>
>
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
prev parent reply other threads:[~2022-11-19 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MentorEmbedded/nvptx-tools/pull/38@github.com>
[not found] ` <MentorEmbedded/nvptx-tools/pull/38/c1320419585@github.com>
2022-11-18 23:25 ` Thomas Schwinge
2022-11-19 6:35 ` Tom de Vries [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ef9c0d6-b409-7206-bd76-a84de9b78b33@suse.de \
--to=tdevries@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=reply+AAAFJ6N2QCLFB22I4MIOMNGBQUE7HEVBNHHFNHPAMA@reply.github.com \
--cc=thomas@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).