public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dirtyepic at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libitm/53113] Build fails in x86_avx.cc if AVX disabled but supported by as (Solaris & Linux) Date: Fri, 22 Feb 2013 02:31:00 -0000 [thread overview] Message-ID: <bug-53113-4-wsx5KJh4NX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53113-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53113 --- Comment #9 from Ryan Hill <dirtyepic at gentoo dot org> 2013-02-22 02:31:03 UTC --- Well, the trouble is nowadays that many CPUs are exactly "this, except without that". But anyways, the test is fragile. There is no reason something like -march=core2 -mno-sse3 should cause this to fail (I don't think it should even try to build it in the first place, but I'm sure there must be a reason). So if this code expects and requires -mavx to compile, append it after the user's CFLAGS rather than letting them blow their feet off.
next prev parent reply other threads:[~2013-02-22 2:31 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-25 12:26 [Bug libitm/53113] New: " windward at gmx dot com 2012-06-08 15:22 ` [Bug libitm/53113] " safety0ff.bugz at gmail dot com 2012-06-08 17:20 ` safety0ff.bugz at gmail dot com 2012-06-13 14:40 ` windward at gmx dot com 2012-06-21 9:25 ` windward at gmx dot com 2012-11-05 3:22 ` dirtyepic at gentoo dot org 2013-02-14 11:48 ` szarpaj at grubelek dot pl 2013-02-21 10:49 ` windward at gmx dot com 2013-02-21 21:23 ` jakub at gcc dot gnu.org 2013-02-22 2:31 ` dirtyepic at gentoo dot org [this message] 2013-02-26 14:18 ` windward at gmx dot com 2013-12-24 16:50 ` nheghathivhistha at gmail dot com 2013-12-24 16:54 ` nheghathivhistha at gmail dot com 2013-12-24 17:40 ` nheghathivhistha at gmail dot com 2013-12-25 16:14 ` hjl.tools at gmail dot com 2013-12-25 16:41 ` nheghathivhistha at gmail dot com 2013-12-25 16:46 ` hjl.tools at gmail dot com 2013-12-25 17:59 ` nheghathivhistha at gmail dot com 2013-12-25 18:05 ` hjl.tools at gmail dot com 2013-12-25 18:37 ` [Bug libitm/53113] Build fails in x86_avx.cc if AVX disabled by -mno-avx but supported by as hjl.tools at gmail dot com 2013-12-25 18:43 ` hjl.tools at gmail dot com 2013-12-25 19:50 ` dirtyepic at gentoo dot org 2013-12-25 20:42 ` hjl.tools at gmail dot com 2013-12-25 20:43 ` hjl.tools at gmail dot com 2013-12-25 20:43 ` hjl.tools at gmail dot com 2014-01-13 19:36 ` hjl at gcc dot gnu.org 2014-06-12 13:53 ` rguenth at gcc dot gnu.org 2015-01-23 12:27 ` torvald at gcc dot gnu.org 2015-01-23 12:36 ` hjl.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-53113-4-wsx5KJh4NX@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).