public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jrp at dial dot pipex dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35350] New: FAIL: gcc.target/i386/isa-10.c execution test
Date: Sun, 24 Feb 2008 12:01:00 -0000 [thread overview]
Message-ID: <bug-35350-15715@http.gcc.gnu.org/bugzilla/> (raw)
The above test started to fail over the last few days.
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc/configure -v --enable-languages=c,c++,fortran
--enable-shared --with-system-zlib --without-included-gettext
--enable-threads=posix --enable-nls --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --enable-mpfr --enable-checking=release
--with-arch=core2
Thread model: posix
gcc version 4.4.0 20080224 (experimental) (GCC)
--
Summary: FAIL: gcc.target/i386/isa-10.c execution test
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jrp at dial dot pipex dot com
GCC build triplet: gcc version 4.4.0 20080224 (experimental) (GCC
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35350
next reply other threads:[~2008-02-24 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 12:01 jrp at dial dot pipex dot com [this message]
2008-02-24 19:24 ` [Bug c++/35350] " ubizjak at gmail dot com
2008-02-24 19:24 ` ubizjak at gmail dot com
2008-03-07 7:06 ` hjl dot tools at gmail dot com
2008-03-07 7:08 ` hjl dot tools at gmail dot com
2008-03-07 7:10 ` hjl dot tools at gmail dot com
2008-03-07 17:01 ` hjl dot tools at gmail dot com
2008-03-08 22:35 ` hjl at gcc dot gnu dot org
2008-03-08 22:38 ` hjl at gcc dot gnu dot org
2008-03-09 4:59 ` [Bug testsuite/35350] " hjl dot tools 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-35350-15715@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).