From: Nick Clifton <nickc@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
Tom de Vries <tdevries@suse.de>,
binutils@sourceware.org, gcc@gcc.gnu.org
Subject: Re: Forward GCC '-v' command-line option to binutils assembler, linker (was: [PING] nvptx: forward '-v' command-line option to assembler, linker)
Date: Thu, 22 Sep 2022 12:32:00 +0100 [thread overview]
Message-ID: <887f5ccb-e7b7-50e8-7356-24e4f4415104@redhat.com> (raw)
In-Reply-To: <878rmd84n6.fsf@euler.schwinge.homeip.net>
Hi Thomas,
>>> +/* Linker supports '-v' option. */
>>> +#define LINK_SPEC "%{v}"
>
> ..., Tom rightfully asked:
>
>> [...] I wonder, normally we don't pass -v to ld, and need -Wl,-v for
>> that.
>
> So, on my quest for making things uniform/simple, I now wonder: should we
> also forward GCC '-v' to binutils linker, or is there a reason to not do
> that?
Not really no. Historically of course this has not been done, so changing
it now might surprise a few users. But it should not be that big of an
issue.
>> So, any particular reason why we would do things differently for
>> nvptx?
Nope, none at all.
Harmonizing the effect of the -v option sounds like a good idea to me.
Cheers
Nick
next prev parent reply other threads:[~2022-09-22 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MentorEmbedded/nvptx-tools/pull/31@github.com>
[not found] ` <MentorEmbedded/nvptx-tools/pull/31/c1094932979@github.com>
[not found] ` <874k185ak4.fsf@dem-tschwing-1.ger.mentorg.com>
[not found] ` <b2aa158a-28b7-04a9-f657-7b5e3d3604ed@codesourcery.com>
[not found] ` <871qw08orn.fsf@euler.schwinge.homeip.net>
[not found] ` <820c4820-aca2-29f2-8727-11aa3913ae68@suse.de>
2022-09-21 9:21 ` Thomas Schwinge
2022-09-22 11:32 ` Nick Clifton [this message]
2022-09-22 12:46 ` Richard Earnshaw
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=887f5ccb-e7b7-50e8-7356-24e4f4415104@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=tdevries@suse.de \
--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).