From: Tobias Burnus <tobias@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
<gcc-patches@gcc.gnu.org>, Tom de Vries <tdevries@suse.de>
Subject: Re: nvptx: forward '-v' command-line option to assembler, linker (was: [MentorEmbedded/nvptx-tools] Issue 30: Ignore not-supported sm_* error without --verify (PR #31))
Date: Mon, 30 May 2022 09:06:21 +0200 [thread overview]
Message-ID: <b2aa158a-28b7-04a9-f657-7b5e3d3604ed@codesourcery.com> (raw)
In-Reply-To: <874k185ak4.fsf@dem-tschwing-1.ger.mentorg.com>
Hi Thomas,
On 29.05.22 22:49, Thomas Schwinge wrote:
> Not sure if that's what you had in mind, but what do you think about the
> attached "nvptx: forward '-v' command-line option to assembler, linker"?
> OK to push to GCC master branch (after merging
> <https://github.com/MentorEmbedded/nvptx-tools/pull/37>
> "Put '-v' verbose output onto stderr instead of stdout")?
I was mainly thinking of some way to have it available — which
'-foffload-options=-Wa,-v' already permits on the GCC side. (Once the
nvptx-tools patch actually makes use of the '-v'.)
If I understand your patch correctly, this patch now causes 'gcc -v' to
imply 'gcc -v -Wa,-v'. I think that's okay, since 'gcc -v' already
outputs a lot of lines and those lines can be helpful to understand what
happens and what not.
Tom, your thoughts on this?
Tobias
-----------------
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
next prev parent reply other threads:[~2022-05-30 7:06 UTC|newest]
Thread overview: 11+ 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>
2022-05-29 20:49 ` Thomas Schwinge
2022-05-30 7:06 ` Tobias Burnus [this message]
2022-06-07 15:41 ` [PING] nvptx: forward '-v' command-line option to assembler, linker Thomas Schwinge
2022-07-05 14:58 ` [PING^2] " Thomas Schwinge
2022-07-13 8:41 ` [PING^3] " Thomas Schwinge
2022-07-20 12:44 ` [PING^4] " Thomas Schwinge
2022-07-27 15:48 ` [PING^5] " Thomas Schwinge
2022-08-06 19:20 ` [PING^6] " Thomas Schwinge
2022-08-16 15:12 ` [PING^7] " Thomas Schwinge
2022-08-30 13:44 ` [PING^8] " Thomas Schwinge
2022-09-05 15:02 ` [PING] " Tom de Vries
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=b2aa158a-28b7-04a9-f657-7b5e3d3604ed@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=gcc-patches@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).