public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <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:19:00 -0000 [thread overview]
Message-ID: <20090615091930.22530.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40385-682@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from dominiq at lps dot ens dot fr 2009-06-15 09:19 -------
> That probably is my fault. However, I can't do anything about it until I see
> the testsuite log file.
The log file looks like:
...
Executing on host: /opt/gcc/i686-darwin/gcc/xgcc -B/opt/gcc/i686-darwin/gcc/
/opt/gcc/gcc-4.5-work/libffi/testsuite/libffi.call/closure_fn0.c -O0 -W -Wall
-I/opt/gcc/i686-darwin/i686-apple-darwin9/x86_64/libffi/include
-I/opt/gcc/gcc-4.5-work/libffi/testsuite/../include
-I/opt/gcc/i686-darwin/i686-apple-darwin9/x86_64/libffi/include/..
-L/opt/gcc/i686-darwin/i686-apple-darwin9/x86_64/libffi/.libs
-L/opt/gcc/i686-darwin/i686-apple-darwin9/x86_64/libstdc++-v3/src/.libs
-shared-libgcc -lffi -lm -m64 -o ./closure_fn0.exe (timeout = 300)
PASS: libffi.call/closure_fn0.c -O0 -W -Wall (test for excess errors)
Setting LD_LIBRARY_PATH to
.:/opt/gcc/i686-darwin/gcc:/opt/gcc/i686-darwin/i686-apple-darwin9/x86_64/libffi/.libs:/opt/gcc/i686-darwin/i686-apple-darwin9/x86_64/libstdc++-v3/src/.libs:.:/opt/gcc/i686-darwin/gcc:/opt/gcc/i686-darwin/i686-apple-darwin9/x86_64/libffi/.libs:/opt/gcc/i686-darwin/i686-apple-darwin9/x86_64/libstdc++-v3/src/.libs
FAIL: libffi.call/closure_fn0.c -O0 -W -Wall execution test
...
Quite terse, isn't it? What would you need precisely?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40385
next prev parent reply other threads:[~2009-06-15 9:19 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 [this message]
2009-06-15 9:24 ` dominiq at lps dot ens dot fr
2009-06-15 9:29 ` aph at gcc dot gnu dot org
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=20090615091930.22530.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).