From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-438499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 9578 invoked by alias); 25 Dec 2013 16:46:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 9534 invoked by uid 48); 25 Dec 2013 16:46:27 -0000
From: "hjl.tools at gmail dot com" <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: Wed, 25 Dec 2013 16:46: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: hjl.tools at gmail dot com
X-Bugzilla-Status: WAITING
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: <bug-53113-4-2Tp3OPXzER@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53113-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53113-4@http.gcc.gnu.org/bugzilla/>
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/msg02154.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53113

--- Comment #16 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to David Kredba from comment #15)
> For me it looks like that GCC build process is taking from some internal
> definition that AVX should be present on Core2 and enables it for libitm.
> Patch attached in this bug report works for gcc-4.9-20131222 fine too.
> 
> "Known to fail" can contain 4.8.2 (and 4.9.0 branch too if possible).
> 
> Gcc knows that there is no AVX, both for 4.8.2 and 4.9.0 snapshot but both

What is exactly the problem? How can I reproduce it?

> versions enable AVX for libitim for me:
> 

That is intentional.  AVX is always compiled in if your binutils supports
it.  When you copy the same GCC run-time library binaries you built on
non-AVX machine, including libitm, to an AVX machine, the AVX functions
are checked and used at the run-time if OS/HW support AVX.