public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/58111] New: 32-bit gcc.target/i386/pr55342.c FAILs Date: Fri, 09 Aug 2013 12:52:00 -0000 [thread overview] Message-ID: <bug-58111-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58111 Bug ID: 58111 Summary: 32-bit gcc.target/i386/pr55342.c FAILs Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: vmakarov at gcc dot gnu.org Host: i386-pc-solaris2.*, x86_64-unknown-linux-gnu Target: i386-pc-solaris2.*, x86_64-unknown-linux-gnu Build: i386-pc-solaris2.*, x86_64-unknown-linux-gnu Between 20130705 (r200711) and 20130712 (r200922) there occured a new testsuite failure FAIL: gcc.target/i386/pr55342.c scan-assembler-not notb on both Solaris/x86 and Linux/x86_64, but only for the 32-bit multilib. I suppose this failure existed as long as the testcase exists. Rainer
next reply other threads:[~2013-08-09 12:52 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-09 12:52 ro at gcc dot gnu.org [this message] 2013-08-09 22:57 ` [Bug target/58111] " bernd.edlinger at hotmail dot de 2014-01-17 15:46 ` ro at CeBiTec dot Uni-Bielefeld.DE
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-58111-4@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: linkBe 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).