From: Andreas Schwab <schwab@suse.de>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: Use ucontext_t not struct ucontext in linux-unwind.h files
Date: Mon, 10 Jul 2017 11:02:00 -0000 [thread overview]
Message-ID: <mvmk23gd06y.fsf@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1707101057410.22173@digraph.polyomino.org.uk> (Joseph Myers's message of "Mon, 10 Jul 2017 10:58:34 +0000")
On Jul 10 2017, Joseph Myers <joseph@codesourcery.com> wrote:
> 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
It's the same error.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2017-07-10 11:02 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
2017-07-10 11:02 ` Andreas Schwab [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=mvmk23gd06y.fsf@suse.de \
--to=schwab@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).