From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8218 invoked by alias); 17 Apr 2013 18:41:12 -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 8189 invoked by uid 55); 17 Apr 2013 18:41:09 -0000 From: "winfried.magerl@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56866] gcc 4.7.x/gcc-4.8.x with '-O3 -march=bdver2' misscompiles glibc-2.17/crypt/sha512.c Date: Wed, 17 Apr 2013 18:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: winfried.magerl@t-online.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-SW-Source: 2013-04/txt/msg01632.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56866 --- Comment #9 from Winfried Magerl 2013-04-17 18:41:06 UTC --- Hi, at least one confirmation. I've done some further checks about float-errors in glibc and that FAM/FAM4 are the extension responsible for the additional float-errors. How to proceed? >>From my point of view and comapred with '-march=amdfam10' the extensions XOP/FAM4/FAM are responsible for the failed tests. Disabling it in gcc-4.8-noxop/gcc/config/i386/i386.c brings me back to the same test-results I'm seeing with amdfam10 (excluding all sorts of scan-*-errors). I would propose the following patch for bdver2-support because features which are untested and known to break code (like for example all the additional test-errors in the gcc-testsuite) should be disabeled: --- gcc-4.8-noxop/gcc/config/i386/i386.c.orig 2013-04-12 20:49:09.181351855 +0200 +++ gcc-4.8-noxop/gcc/config/i386/i386.c 2013-04-12 23:15:09.112185980 +0200 @@ -2976,9 +2976,9 @@ {"bdver2", PROCESSOR_BDVER2, CPU_BDVER2, PTA_64BIT | PTA_MMX | PTA_SSE | PTA_SSE2 | PTA_SSE3 | PTA_SSE4A | PTA_CX16 | PTA_ABM | PTA_SSSE3 | PTA_SSE4_1 - | PTA_SSE4_2 | PTA_AES | PTA_PCLMUL | PTA_AVX | PTA_FMA4 - | PTA_XOP | PTA_LWP | PTA_BMI | PTA_TBM | PTA_F16C - | PTA_FMA | PTA_PRFCHW | PTA_FXSR | PTA_XSAVE}, + | PTA_SSE4_2 | PTA_AES | PTA_PCLMUL | PTA_AVX + | PTA_LWP | PTA_BMI | PTA_TBM | PTA_F16C + | PTA_PRFCHW | PTA_FXSR | PTA_XSAVE}, {"bdver3", PROCESSOR_BDVER3, CPU_BDVER3, PTA_64BIT | PTA_MMX | PTA_SSE | PTA_SSE2 | PTA_SSE3 | PTA_SSE4A | PTA_CX16 | PTA_ABM | PTA_SSSE3 | PTA_SSE4_1 just an examp,e because the features should be disabled in bdver1/3 too (XOP/FMA4/FMA are only available in bdver1/2/3). Maybe adding the gcc-developers from @amd.com? regards winfried