public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2872] nvptx: forward '-v' command-line option to assembler
Date: Mon, 26 Sep 2022 14:12:38 +0000 (GMT)	[thread overview]
Message-ID: <20220926141238.9A3203858284@sourceware.org> (raw)

https://gcc.gnu.org/g:84072a2615ec1f5f35e994128a6dc22af5bf1322

commit r13-2872-g84072a2615ec1f5f35e994128a6dc22af5bf1322
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Sun May 29 22:31:43 2022 +0200

    nvptx: forward '-v' command-line option to assembler
    
    For example, for offloading compilation with '-save-temps -v', before vs. after
    word-diff then looks like:
    
        [...]
         [...]/build-gcc-offload-nvptx-none/gcc/as {+-v -v+} -o ./a.xnvptx-none.mkoffload.o ./a.xnvptx-none.mkoffload.s
        {+Verifying sm_30 code with sm_35 code generation.+}
        {+ ptxas -c -o /dev/null ./a.xnvptx-none.mkoffload.o --gpu-name sm_35 -O0+}
        [...]
    
    (This depends on <https://github.com/MentorEmbedded/nvptx-tools/pull/37>
    "Put '-v' verbose output onto stderr instead of stdout".)
    
            gcc/
            * config/nvptx/nvptx.h (ASM_SPEC): Define.

Diff:
---
 gcc/config/nvptx/nvptx.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gcc/config/nvptx/nvptx.h b/gcc/config/nvptx/nvptx.h
index dc9cad1aaaf..0b0170d77b3 100644
--- a/gcc/config/nvptx/nvptx.h
+++ b/gcc/config/nvptx/nvptx.h
@@ -27,6 +27,10 @@
 
 /* Run-time Target.  */
 
+/* Assembler supports '-v' option; handle similar to
+   '../../gcc.cc:asm_options', 'HAVE_GNU_AS'.  */
+#define ASM_SPEC "%{v}"
+
 #define STARTFILE_SPEC "%{mmainkernel:crt0.o}"
 
 #define TARGET_CPU_CPP_BUILTINS() nvptx_cpu_cpp_builtins ()

                 reply	other threads:[~2022-09-26 14:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220926141238.9A3203858284@sourceware.org \
    --to=tschwinge@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).