public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Nathan Sidwell <nathan@acm.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	Richard Guenther <richard.guenther@gmail.com>
Subject: Re: [patch] Allow plugin-specific dumps
Date: Fri, 19 May 2023 11:56:35 -0600	[thread overview]
Message-ID: <f47ca677-40a3-88fa-e88d-3b1a02c763ba@gmail.com> (raw)
In-Reply-To: <17c8e37e-0748-5333-002a-026348b19627@acm.org>



On 5/17/23 17:38, Nathan Sidwell via Gcc-patches wrote:
> PR 99451 is about the inability to name tree and rtl dumps by plugin 
> name.  And includes a patch.  But then I worked around the problem and 
> forgot about it. Here it is again, retested against trunk.
> 
> ok?
> 
> nathan
> -- 
> Nathan Sidwell
> 
> 0001-Allow-plugin-dumps.patch
> 
>  From e54518bc5e59ef5cdc21c652ceac41bd0c0f436c Mon Sep 17 00:00:00 2001
> From: Nathan Sidwell<nathan@acm.org>
> Date: Wed, 17 May 2023 19:27:13 -0400
> Subject: [PATCH] Allow plugin dumps
> 
> Defer dump option parsing until plugins are initialized.  This allows one to
> use plugin names for dumps.
> 
> 	PR other/99451
> 	gcc/
> 	* opts.h (handle_deferred_dump_options): Declare.
> 	* opts-global.cc (handle_common_deferred_options): Do not handle
> 	dump options here.
> 	(handle_deferred_dump_options): New.
> 	* toplev.cc (toplev::main): Call it after plugin init.
OK.
jeff

      reply	other threads:[~2023-05-19 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 23:38 Nathan Sidwell
2023-05-19 17:56 ` Jeff Law [this message]

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=f47ca677-40a3-88fa-e88d-3b1a02c763ba@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nathan@acm.org \
    --cc=richard.guenther@gmail.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).