public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/52579] [4.8/4.9/5 regression] i386_w32_fallback_frame_state should care ffi raw-closure stub function
Date: Thu, 12 Mar 2015 15:24:00 -0000	[thread overview]
Message-ID: <bug-52579-4-qQHEgabHRs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52579-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52579

Kai Tietz <ktietz at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-03-12
                 CC|                            |ktietz at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #7 from Kai Tietz <ktietz at gcc dot gnu.org> ---
This issue seems to be fixed in 5.0 by Richard's work on libffi.

Could you please check, if issue is fixed for you?


  parent reply	other threads:[~2015-03-12 15:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 17:05 [Bug libgcj/52579] New: [4.8 " jojelino at gmail dot com
2012-03-14 10:36 ` [Bug libgcj/52579] " rguenth at gcc dot gnu.org
2012-04-19  8:25 ` jojelino at gmail dot com
2012-09-19 12:18 ` rguenth at gcc dot gnu.org
2013-03-22 14:41 ` [Bug libgcj/52579] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:57 ` jakub at gcc dot gnu.org
2013-10-16  9:48 ` jakub at gcc dot gnu.org
2014-05-22  9:00 ` [Bug libgcj/52579] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:36 ` [Bug libgcj/52579] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-03-12 15:24 ` ktietz at gcc dot gnu.org [this message]
2015-03-15 21:26 ` jojelino at gmail dot com

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-52579-4-qQHEgabHRs@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).