From: Andreas Schwab <schwab@linux-m68k.org>
To: Ian Lance Taylor <iant@golang.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"gofrontend-dev\@googlegroups.com"
<gofrontend-dev@googlegroups.com>
Subject: Re: Fwd: libgo patch committed: Use -fgo-c-header to share between Go and C
Date: Fri, 02 Sep 2016 16:32:00 -0000 [thread overview]
Message-ID: <87shtiw9dv.fsf@linux-m68k.org> (raw)
In-Reply-To: <87wpiuw9km.fsf@linux-m68k.org> (Andreas Schwab's message of "Fri, 02 Sep 2016 18:27:53 +0200")
On Sep 02 2016, Andreas Schwab <schwab@linux-m68k.org> wrote:
> On Sep 02 2016, Ian Lance Taylor <iant@golang.org> wrote:
>
>> On Fri, Sep 2, 2016 at 9:14 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>>>
>>> That breaks libgo on ia64. The problem is that _ucontext_t isn't
>>> properly aligned.
>>
>> Interesting. Thanks for looking into it. What is the required
>> alignment? This code should be aligning it to a pointer boundary.
>
> That is too small. It needs at least 16 byte alignment.
And PowerPC has a similar requirement.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-09-02 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOyqgcUb2T0NkeffcN9SwbvQyWA0eqvi+BcAWAU4iiM9qmHb1w@mail.gmail.com>
2016-08-30 21:14 ` Ian Lance Taylor
2016-09-02 16:15 ` Andreas Schwab
2016-09-02 16:18 ` Ian Lance Taylor
2016-09-02 16:28 ` Andreas Schwab
2016-09-02 16:32 ` Andreas Schwab [this message]
2016-09-09 13:52 ` Ian Lance Taylor
2016-09-09 13:59 ` Andreas Schwab
2016-09-09 16:44 ` Ian Lance Taylor
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=87shtiw9dv.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@golang.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).