From: Joseph Myers <joseph@codesourcery.com>
To: Andreas Schwab <schwab@suse.de>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: Use ucontext_t not struct ucontext in linux-unwind.h files
Date: Mon, 10 Jul 2017 10:58:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1707101057410.22173@digraph.polyomino.org.uk> (raw)
In-Reply-To: <mvmvan0d6nw.fsf@suse.de>
On Mon, 10 Jul 2017, Andreas Schwab wrote:
> On Jun 27 2017, Joseph Myers <joseph@codesourcery.com> wrote:
>
> > Testing compilation together with current glibc with glibc's
> > build-many-glibcs.py. OK to commit (mainline and active release
> > branches) if that passes?
>
> This still doesn't work on the gcc-6-branch:
That seems like an issue with a different header, outside the scope of my
patch (but for which it would be natural to apply similar changes to GCC 5
and 6 branches).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-07-10 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 13:57 Joseph Myers
2017-06-27 17:55 ` Joseph Myers
2017-06-28 7:31 ` Richard Biener
2017-07-10 8:42 ` Andreas Schwab
2017-07-10 10:58 ` Joseph Myers [this message]
2017-07-10 11:02 ` Andreas Schwab
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=alpine.DEB.2.20.1707101057410.22173@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@suse.de \
/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).