public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-1807] add -ltrans-objects lto-plugin debug option
Date: Fri, 25 Jun 2021 06:49:04 +0000 (GMT)	[thread overview]
Message-ID: <20210625064904.356243857432@sourceware.org> (raw)

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

commit r12-1807-gc6c7ac0499c722ad03259013d6dc50e585a71860
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Jun 22 08:43:15 2021 +0200

    add -ltrans-objects lto-plugin debug option
    
    This adds a -ltrans-objects option to lto-plugin that by-passes
    lto-wrapper invocation and instead feeds LD the final LTRANS objects
    directly from the response file given as argument to the option.
    This allows LD issues involving the linker-plugin path to be
    debugged in an easier way with just the IR objects (their symtab)
    and the LTRANS objects as testcase.
    
    I've tested the path re-building stage2 build/genmatch from an
    LTO bootstrap and got a bit-identical executable by adding
    -plugin-opt=-ltrans-objects=y to the original collect2 invocation,
    seeding y with the final objects as printed by building genmatch
    with -save-temps -v.
    
    2021-06-22  Richard Biener  <rguenther@suse.de>
    
    lto-plugin/
            * lto-plugin.c (ltrans_objects): New global.
            (all_symbols_read_handler): If -ltrans-objects was specified,
            add the output files from the specified file directly.
            (process_option): Handle -ltrans-objects.

Diff:
---
 lto-plugin/lto-plugin.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/lto-plugin/lto-plugin.c b/lto-plugin/lto-plugin.c
index ff79f4ac462..6ab9822f369 100644
--- a/lto-plugin/lto-plugin.c
+++ b/lto-plugin/lto-plugin.c
@@ -190,6 +190,8 @@ static int lto_wrapper_num_args;
 static char **pass_through_items = NULL;
 static unsigned int num_pass_through_items;
 
+static char *ltrans_objects = NULL;
+
 static bool debug;
 static bool save_temps;
 static bool verbose;
@@ -739,6 +741,14 @@ all_symbols_read_handler (void)
       return LDPS_OK;
     }
 
+  if (ltrans_objects)
+    {
+      FILE *objs = fopen (ltrans_objects, "r");
+      add_output_files (objs);
+      fclose (objs);
+      return LDPS_OK;
+    }
+
   lto_argv = (char **) xcalloc (sizeof (char *), num_lto_args);
   lto_arg_ptr = (const char **) lto_argv;
   assert (lto_wrapper_argv);
@@ -1345,6 +1355,8 @@ process_option (const char *option)
 	  break;
 	}
     }
+  else if (startswith (option, "-ltrans-objects="))
+    ltrans_objects = xstrdup (option + strlen ("-ltrans-objects="));
   else
     {
       int size;


                 reply	other threads:[~2021-06-25  6:49 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=20210625064904.356243857432@sourceware.org \
    --to=rguenth@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).