public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/64021] Empty struct vs libffi
Date: Sat, 22 Nov 2014 08:55:00 -0000 [thread overview]
Message-ID: <bug-64021-4-NGT5JsvI68@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64021-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64021
--- Comment #1 from Richard Henderson <rth at gcc dot gnu.org> ---
Oh, that should read "fail after the merge of the new libffi".
Current libffi happens to have nothing interesting in the stack
slot that's incorrectly popped, and to happens not to fail. Not
so with the ffi_call_go rewrite.
next prev parent reply other threads:[~2014-11-22 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 8:51 [Bug go/64021] New: " rth at gcc dot gnu.org
2014-11-22 8:55 ` rth at gcc dot gnu.org [this message]
2014-11-22 13:09 ` [Bug go/64021] " hjl.tools at gmail dot com
2014-11-22 21:56 ` pinskia at gcc dot gnu.org
2014-11-24 7:48 ` rth at gcc dot gnu.org
2014-11-24 9:16 ` jakub at gcc dot gnu.org
2014-11-24 9:58 ` rth at gcc dot gnu.org
2014-11-24 15:40 ` ian at airs dot com
2014-11-24 15:45 ` rth at gcc dot gnu.org
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=bug-64021-4-NGT5JsvI68@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).