From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2114 invoked by alias); 25 Dec 2013 19:50:55 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 2081 invoked by uid 48); 25 Dec 2013 19:50:51 -0000 From: "dirtyepic at gentoo dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libitm/53113] Build fails in x86_avx.cc if AVX disabled by -mno-avx but supported by as Date: Wed, 25 Dec 2013 19:50:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libitm X-Bugzilla-Version: 4.7.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dirtyepic at gentoo dot org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg02166.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53113 --- Comment #21 from Ryan Hill --- Well in practice we've had to have users build GCC with -mno-avx on no less than three occasions since 4.4 due to compiler bugs on certain chips (usually newer chips + old releases), so it'd be nice to have it just work. If x86_avx.cc must be compiled with -mavx then can it be appended after user CFLAGS? That should make everyone happy.