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/54866] New: gcc.target/i386/long-double-80-7.c FAILs Date: Tue, 09 Oct 2012 08:55:00 -0000 [thread overview] Message-ID: <bug-54866-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54866 Bug #: 54866 Summary: gcc.target/i386/long-double-80-7.c FAILs Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: ro@gcc.gnu.org CC: hjl.tools@gmail.com Host: i386-pc-solaris2.9, i686-unknown-linux-gnu Target: i386-pc-solaris2.9, i686-unknown-linux-gnu Build: i386-pc-solaris2.9, i686-unknown-linux-gnu The new gcc.target/i386/long-double-80-7.c test FAILs on Solaris 9/x86 and 32-bit Linux/x86: FAIL: gcc.target/i386/long-double-80-7.c (test for excess errors) WARNING: gcc.target/i386/long-double-80-7.c compilation failed to produce executable Excess errors: /vol/gcc/src/hg/trunk/local/gcc/testsuite/gcc.target/i386/long-double-80-7.c:1:0 : warning: SSE instruction set disabled, using 387 arithmetics [enabled by defau lt] /var/gcc/regression/trunk/9-gcc/build/gcc/include/xmmintrin.h:32:3: error: #erro r "SSE instruction set not enabled" /vol/gcc/src/hg/trunk/local/gcc/testsuite/gcc.target/i386/m128-check.h:52:3: err or: unknown type name '__m128' No idea what the right fix might be: just adding -msse2? Don't we also need sse2_runtime for a run test? Rainer
next reply other threads:[~2012-10-09 8:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-09 8:55 ro at gcc dot gnu.org [this message] 2012-10-09 8:56 ` [Bug target/54866] " ro at gcc dot gnu.org 2012-10-09 9:45 ` ubizjak at gmail dot com 2012-10-09 13:40 ` ro at gcc dot gnu.org 2012-10-09 13:42 ` ro at gcc dot gnu.org
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-54866-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).