From: Jeff Law <law@redhat.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] reorg.c janitor: remove epilogue_delay_list
Date: Sat, 01 Dec 2012 19:11:00 -0000 [thread overview]
Message-ID: <50BA5673.1010905@redhat.com> (raw)
In-Reply-To: <CABu31nP91GS_9d_63ggizAzpuCdFdXn_b8Bo917GR1BG_E6kNQ@mail.gmail.com>
On 11/30/2012 03:00 PM, Steven Bosscher wrote:
> Hello,
>
> This epilogue_delay_list probably existed only for text epilogues, but
> it is now unused.
>
> Tested by building a set of cc1-i files at -O2 for SPARC with and
> without the patch, and verifying that there are no code gen changes.
>
> OK for trunk?
OK
jeff
prev parent reply other threads:[~2012-12-01 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 22:03 Steven Bosscher
2012-12-01 19:11 ` 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=50BA5673.1010905@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=stevenb.gcc@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).