From: Jeff Law <jeffreyalaw@gmail.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
gcc-patches@gcc.gnu.org
Cc: Jan Hubicka <hubicka@ucw.cz>,
Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
Subject: Re: [PATCH] cgraph_node: Remove redundant section clearing
Date: Thu, 3 Nov 2022 16:47:11 -0600 [thread overview]
Message-ID: <aa851bca-97aa-9ea3-eb1f-655e5a24afdb@gmail.com> (raw)
In-Reply-To: <20221103204741.516199-1-aldot@gcc.gnu.org>
On 11/3/22 14:47, Bernhard Reutner-Fischer via Gcc-patches wrote:
> Ok for trunk if testing passes?
>
> gcc/ChangeLog:
>
> * cgraph.cc (cgraph_node::make_local): Remove redundant set_section.
> * multiple_target.cc (create_dispatcher_calls): Likewise.
OK after testing passes.
jeff
next prev parent reply other threads:[~2022-11-03 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 20:47 Bernhard Reutner-Fischer
2022-11-03 22:47 ` Jeff Law [this message]
2022-11-04 11:55 ` Jan Hubicka
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=aa851bca-97aa-9ea3-eb1f-655e5a24afdb@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=aldot@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rep.dot.nop@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).