public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aph at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/40385] new testcases bought in by Revision 148285 fail on ia64
Date: Mon, 15 Jun 2009 09:29:00 -0000	[thread overview]
Message-ID: <20090615092934.28759.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40385-682@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from aph at gcc dot gnu dot org  2009-06-15 09:29 -------
I need to know why it's crashing.  Usually there's some sort of error message. 
If there's not, there's no choice but to debug.

This Darwin problem is clearly not the same bug as 40385, so it needs a new
Bugzilla entry.

I expect that a patch to xfail err_bad_abi.c on *-*-* would be approved.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40385


  parent reply	other threads:[~2009-06-15  9:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 10:32 [Bug boehm-gc/40385] New: [4.5 regression] Revision 148285 caused many failures hjl dot tools at gmail dot com
2009-06-09 10:38 ` [Bug boehm-gc/40385] " aph at gcc dot gnu dot org
2009-06-09 14:19 ` [Bug libffi/40385] " rguenth at gcc dot gnu dot org
2009-06-11 20:46 ` dominiq at lps dot ens dot fr
2009-06-13 19:23 ` [Bug libffi/40385] new testcases bought in by Revision 148285 fail on ia64 pinskia at gcc dot gnu dot org
2009-06-15  9:05 ` dominiq at lps dot ens dot fr
2009-06-15  9:07 ` aph at gcc dot gnu dot org
2009-06-15  9:09 ` aph at gcc dot gnu dot org
2009-06-15  9:19 ` dominiq at lps dot ens dot fr
2009-06-15  9:24 ` dominiq at lps dot ens dot fr
2009-06-15  9:29 ` aph at gcc dot gnu dot org [this message]
2009-06-15  9:42 ` dominiq at lps dot ens dot fr
2010-04-14 22:29 ` sje at cup dot hp 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=20090615092934.28759.qmail@sourceware.org \
    --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).