public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5660] driver, toplevel: Avoid emitting the version information twice.
Date: Thu,  2 Feb 2023 16:18:26 +0000 (GMT)	[thread overview]
Message-ID: <20230202161826.A21E83858C52@sourceware.org> (raw)

https://gcc.gnu.org/g:f25dd779d44fb75a6c5e1c73e5bf2c85af180026

commit r13-5660-gf25dd779d44fb75a6c5e1c73e5bf2c85af180026
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Sun Jan 22 21:12:15 2023 +0000

    driver, toplevel: Avoid emitting the version information twice.
    
    For a regular compile job, with -v we emit the GCC version information
    twice - once from main() and once from process_options().
    
    We do not need to output the second header.
    
    Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
    
    gcc/ChangeLog:
    
            * toplev.cc (toplev::main): Only print the version information header
            from toplevel main().

Diff:
---
 gcc/toplev.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/toplev.cc b/gcc/toplev.cc
index 42937f0ba00..4c15d4f542e 100644
--- a/gcc/toplev.cc
+++ b/gcc/toplev.cc
@@ -1358,7 +1358,7 @@ process_options (bool no_backend)
      option flags in use.  */
   if (version_flag)
     {
-      print_version (stderr, "", true);
+      /* We already printed the version header in main ().  */
       if (!quiet_flag)
 	{
 	  fputs ("options passed: ", stderr);

                 reply	other threads:[~2023-02-02 16:18 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=20230202161826.A21E83858C52@sourceware.org \
    --to=iains@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).