public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/marxin/heads/experiment-asm-file)] Test it.
Date: Thu, 13 Oct 2022 15:49:59 +0000 (GMT)	[thread overview]
Message-ID: <20221013154959.A3B123857352@sourceware.org> (raw)

https://gcc.gnu.org/g:2eda0612e760d05702bc4d240f429fb697c20538

commit 2eda0612e760d05702bc4d240f429fb697c20538
Author: Martin Liska <mliska@suse.cz>
Date:   Mon Aug 22 13:38:14 2022 +0200

    Test it.

Diff:
---
 gcc/cgraphunit.cc | 1 +
 gcc/lto/lto.cc    | 1 +
 gcc/toplev.cc     | 9 +++++----
 gcc/toplev.h      | 2 ++
 4 files changed, 9 insertions(+), 4 deletions(-)

diff --git a/gcc/cgraphunit.cc b/gcc/cgraphunit.cc
index 7b5be0f1539..5f09e2d8f87 100644
--- a/gcc/cgraphunit.cc
+++ b/gcc/cgraphunit.cc
@@ -2520,6 +2520,7 @@ symbol_table::finalize_compilation_unit (void)
 
       /* Clean up anything that needs cleaning up after initial debug
 	 generation.  */
+      init_asm_output ();
       debuginfo_early_start ();
       (*debug_hooks->early_finish) (main_input_filename);
       debuginfo_early_stop ();
diff --git a/gcc/lto/lto.cc b/gcc/lto/lto.cc
index 3a9147b01b5..4ed11ca2c24 100644
--- a/gcc/lto/lto.cc
+++ b/gcc/lto/lto.cc
@@ -684,6 +684,7 @@ lto_main (void)
 
 	  /* Let the middle end know that we have read and merged all of
 	     the input files.  */
+	  init_asm_output();
 	  symtab->compile ();
 
 	  timevar_stop (TV_PHASE_OPT_GEN);
diff --git a/gcc/toplev.cc b/gcc/toplev.cc
index b53a78bbaf1..7125ad13a2b 100644
--- a/gcc/toplev.cc
+++ b/gcc/toplev.cc
@@ -98,7 +98,6 @@ along with GCC; see the file COPYING3.  If not see
 static void general_init (const char *, bool);
 static void backend_init (void);
 static int lang_dependent_init (const char *);
-static void init_asm_output (const char *);
 static void finalize (bool);
 
 static void crash_signal (int) ATTRIBUTE_NORETURN;
@@ -675,14 +674,16 @@ print_version (FILE *file, const char *indent, bool show_global_state)
 }
 
 
+static const char *asm_name;
 
 /* Open assembly code output file.  Do this even if -fsyntax-only is
    on, because then the driver will have provided the name of a
    temporary file or bit bucket for us.  NAME is the file specified on
    the command line, possibly NULL.  */
-static void
-init_asm_output (const char *name)
+void
+init_asm_output ()
 {
+  const char *name = asm_name;
   if (name == NULL && asm_file_name == 0)
     asm_out_file = stdout;
   else
@@ -1818,7 +1819,7 @@ lang_dependent_init (const char *name)
 
   if (!flag_wpa)
     {
-      init_asm_output (name);
+      asm_name = xstrdup (name);
 
       if (!flag_generate_lto && !flag_compare_debug)
 	{
diff --git a/gcc/toplev.h b/gcc/toplev.h
index a82ef8b8fd3..caedfc616c0 100644
--- a/gcc/toplev.h
+++ b/gcc/toplev.h
@@ -99,4 +99,6 @@ extern void parse_alignment_opts (void);
 
 extern void initialize_rtl (void);
 
+extern void init_asm_output (void);
+
 #endif /* ! GCC_TOPLEV_H */

             reply	other threads:[~2022-10-13 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 15:49 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-13 18:52 Martin Liska
2022-09-09  8:47 Martin Liska

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=20221013154959.A3B123857352@sourceware.org \
    --to=marxin@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).