From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 44246 invoked by alias); 21 Oct 2015 14:09:10 -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 44204 invoked by uid 48); 21 Oct 2015 14:09:06 -0000 From: "ranjan.amit8 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/68028] Compilation error "lto1: error: target attribute or pragma changes single precision floating point", with "-flto" on different variant of powerpc like -mcpu=e6500, 8540, 8548, e500mc, e500mc64, e5500. With gcc-5.2.0 while with 4.9.3 it is working fine. Date: Wed, 21 Oct 2015 14:09: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-Version: 5.2.0 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: blocker X-Bugzilla-Who: ranjan.amit8 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg01740.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D68028 --- Comment #2 from martin --- Hi Richard, You mean to say that there is no issue with LTO, the error is only due to addition flags for particular -mcpu. I am only getting this issue when I passs -flto option with -mcpu=3De6500. Without -flto there is no issue as $ ./powerpc-windriver-linux-gcc test.c -mcpu=3De6500 It means with particular -mcpu with -flto option switches additional flags which is resulting in this error during compilation. While those additional flags came into picture after gcc-5.1.0 release. $ ./powerpc-windriver-linux-gcc test.c -mcpu=3De6500 -flto In function =C3=A2main=C3=A2: lto1: warning: compilation : main_target_opt =3D 1 lto1: error: target attribute or pragma changes single precision floating p= oint lto1: error: target attribute or pragma changes double precision floating p= oint lto-wrapper: fatal error: ./powerpc-windriver-linux-gcc returned 1 exit sta= tus compilation terminated. /opt/2cross/lib/gcc/powerpc-windriver-linux/5.2.0/../../../../powerpc-windr= iver-linux/bin/ld: lto-wrapper failed collect2: error: ld returned 1 exit status Can you guide me further. Thanks, Martin >>From gcc-bugs-return-500186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 21 14:17:31 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 99835 invoked by alias); 21 Oct 2015 14:17:30 -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 Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 99566 invoked by uid 48); 21 Oct 2015 14:17:26 -0000 From: "chefmax at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/68041] [6 Regression] Bootstrap broken on x86_64-apple-darwin14 at revision r229119 Date: Wed, 21 Oct 2015 14:17:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: blocker X-Bugzilla-Who: chefmax at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 6.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg01741.txt.bz2 Content-length: 2010 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D68041 --- Comment #5 from Maxim Ostapenko --- (In reply to Dominique d'Humieres from comment #4) > With the patch in comment 2, bootstrap completed without any problem. >=20 > Preliminary tests for g++ and asan >=20 > =3D=3D=3D g++ Summary for unix/-m64 =3D=3D=3D >=20 > # of expected passes 1007 > # of unexpected failures 14 > # of unsupported tests 179 >=20 > =3D=3D=3D g++ Summary =3D=3D=3D >=20 > # of expected passes 2021 > # of unexpected failures 21 > # of unsupported tests 358 >=20 > the failures are >=20 > FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O0 output pattern test > FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O1 output pattern test > FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O2 output pattern test > FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O3 -g output pattern = test > FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -Os output pattern test > FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O2 -flto > -flto-partition=3Dnone output pattern test > FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O2 -flto output patte= rn > test >=20 > for both -m32 and -m64, and >=20 > FAIL: c-c++-common/asan/memcmp-1.c -O0 output pattern test > FAIL: c-c++-common/asan/memcmp-1.c -O1 output pattern test > FAIL: c-c++-common/asan/memcmp-1.c -O2 output pattern test > FAIL: c-c++-common/asan/memcmp-1.c -O3 -g output pattern test > FAIL: c-c++-common/asan/memcmp-1.c -Os output pattern test > FAIL: c-c++-common/asan/memcmp-1.c -O2 -flto -flto-partition=3Dnone ou= tput > pattern test > FAIL: c-c++-common/asan/memcmp-1.c -O2 -flto output pattern test >=20 > for -m64 only. >=20 > How many lines of the output do you need to adjust the regexps? Thanks! These tests passed before, right? So, could you share more details about these tests output (perhaps open a new bug with sanitizer label)? >=20 > Further tests for ubsan and gcc in progress. >>From gcc-bugs-return-500187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 21 14:22:35 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 27697 invoked by alias); 21 Oct 2015 14:22:34 -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 Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 27642 invoked by uid 48); 21 Oct 2015 14:22:31 -0000 From: "nacitar at ubercpp dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67991] Pointer to function with internal linkage not being allowed, when it should be Date: Wed, 21 Oct 2015 14:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 5.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nacitar at ubercpp dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: 2015-10/txt/msg01742.txt.bz2 Content-length: 318 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67991 --- Comment #7 from Jacob McIntosh --- Per a thread on the isocpp group(linked in the OP), N4268's wording was incorporated shortly before C++14's ratification, so it's unclear to me why this is a C++1z feature and not a C++14 feature.