From: "Roland McGrath via gcc-patches" <gcc-patches@gcc.gnu.org>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org, rguenth@gcc.gnu.org
Subject: Re: [PATCH PR other/77609] Let the assembler choose ELF section types for miscellaneous named sections
Date: Fri, 04 May 2018 18:25:00 -0000 [thread overview]
Message-ID: <CAB=4xhrChB51oNt6tGV8EjnNvXJRVwsm-SVv=iKPkRy4yAAKDw@mail.gmail.com> (raw)
In-Reply-To: <CAB=4xhrbMeNOL7TJKnQRf2eOAw6HQ-0COUHGjQZb0Le8gBuYnQ@mail.gmail.com>
ping
On Sat, Apr 28, 2018 at 2:42 AM Roland McGrath <mcgrathr@google.com> wrote:
> I'm back for stage 1!
> The same patch from
https://gcc.gnu.org/ml/gcc-patches/2018-02/msg01549.html
> rebases cleanly and I didn't change anything but the date on the log entry
> since what I posted there. The fresh rebase is on the roland/pr77609 git
> branch for your convenience.
> It has no check-gcc failures on x86_64-linux-gnu.
> OK to commit to trunk now?
> When will be the right time to raise the question of backporting it,
> perhaps shortly after the 8 release?
> Thanks,
> Roland
next prev parent reply other threads:[~2018-05-04 18:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 23:41 Roland McGrath
2016-09-22 20:25 ` Roland McGrath
2018-02-24 9:54 ` Roland McGrath via gcc-patches
2018-02-27 4:11 ` Ian Lance Taylor via gcc-patches
2018-02-28 2:01 ` Roland McGrath via gcc-patches
2018-02-28 4:14 ` Ian Lance Taylor via gcc-patches
2018-02-28 23:56 ` Roland McGrath via gcc-patches
2018-03-01 0:07 ` Ian Lance Taylor via gcc-patches
2018-03-01 0:19 ` Roland McGrath via gcc-patches
2018-04-28 11:58 ` Roland McGrath via gcc-patches
2018-05-04 18:25 ` Roland McGrath via gcc-patches [this message]
2018-05-04 18:44 ` Ian Lance Taylor via gcc-patches
2018-05-05 23:38 ` Roland McGrath via gcc-patches
2018-06-14 0:52 ` Roland McGrath via gcc-patches
2018-06-14 1:05 ` Ian Lance Taylor via gcc-patches
2018-06-14 1:23 ` Roland McGrath via gcc-patches
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='CAB=4xhrChB51oNt6tGV8EjnNvXJRVwsm-SVv=iKPkRy4yAAKDw@mail.gmail.com' \
--to=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=mcgrathr@google.com \
--cc=rguenth@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).