* [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.
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
@ 2015-10-20 11:51 ` rguenth at gcc dot gnu.org
2015-10-21 14:09 ` ranjan.amit8 at gmail dot com
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: rguenth at gcc dot gnu.org @ 2015-10-20 11:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |lto
CC| |hubicka at gcc dot gnu.org
Component|lto |target
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
static bool
rs6000_option_override_internal (bool global_init_p)
{
...
if (main_target_opt)
{
if (main_target_opt->x_rs6000_single_float != rs6000_single_float)
error ("target attribute or pragma changes single precision floating "
"point");
if (main_target_opt->x_rs6000_double_float != rs6000_double_float)
error ("target attribute or pragma changes double precision floating "
"point");
}
it looks like -mcpu=... is not allowed to differ from global defaults. Note
that LTO now passes all "Save" options in function attributes and no longer
passes along -mcpu= to the link-time transparently.
mcpu=
Target RejectNegative Joined Var(rs6000_cpu_index) Init(-1)
Enum(rs6000_cpu_opt_value) Save
-mcpu= Use features of and schedule code for given CPU
so -mcpu= is 'Save' but appearantly switches additional flags?
^ permalink raw reply [flat|nested] 13+ messages in thread* [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.
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
2015-10-20 11:51 ` [Bug target/68028] " rguenth at gcc dot gnu.org
@ 2015-10-21 14:09 ` ranjan.amit8 at gmail dot com
2015-10-21 14:28 ` rguenth at gcc dot gnu.org
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: ranjan.amit8 at gmail dot com @ 2015-10-21 14:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
--- Comment #2 from martin <ranjan.amit8 at gmail dot com> ---
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=e6500.
Without -flto there is no issue as
$ ./powerpc-windriver-linux-gcc test.c -mcpu=e6500
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=e6500 -flto
In function âmainâ:
lto1: warning: compilation : main_target_opt = 1
lto1: error: target attribute or pragma changes single precision floating point
lto1: error: target attribute or pragma changes double precision floating point
lto-wrapper: fatal error: ./powerpc-windriver-linux-gcc returned 1 exit status
compilation terminated.
/opt/2cross/lib/gcc/powerpc-windriver-linux/5.2.0/../../../../powerpc-windriver-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: <gcc-bugs-return-500186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
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: <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
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" <gcc-bugzilla@gcc.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: <bug-68041-4-gDZDcGNx7d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68041-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68041-4@http.gcc.gnu.org/bugzilla/>
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=68041
--- Comment #5 from Maxim Ostapenko <chefmax at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #4)
> With the patch in comment 2, bootstrap completed without any problem.
>
> Preliminary tests for g++ and asan
>
> === g++ Summary for unix/-m64 ===
>
> # of expected passes 1007
> # of unexpected failures 14
> # of unsupported tests 179
>
> === g++ Summary ===
>
> # of expected passes 2021
> # of unexpected failures 21
> # of unsupported tests 358
>
> the failures are
>
> 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=none output pattern test
> FAIL: c-c++-common/asan/sanity-check-pure-c-1.c -O2 -flto output pattern
> test
>
> for both -m32 and -m64, and
>
> 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=none output
> pattern test
> FAIL: c-c++-common/asan/memcmp-1.c -O2 -flto output pattern test
>
> for -m64 only.
>
> 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)?
>
> 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: <gcc-bugs-return-500187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
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: <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
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" <gcc-bugzilla@gcc.gnu.org>
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: <bug-67991-4-ns8xFVPgVU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67991-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67991-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: 2015-10/txt/msg01742.txt.bz2
Content-length: 318
https://gcc.gnu.org/bugzilla/show_bug.cgi?idg991
--- Comment #7 from Jacob McIntosh <nacitar at ubercpp dot com> ---
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.
^ permalink raw reply [flat|nested] 13+ messages in thread* [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.
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
2015-10-20 11:51 ` [Bug target/68028] " rguenth at gcc dot gnu.org
2015-10-21 14:09 ` ranjan.amit8 at gmail dot com
@ 2015-10-21 14:28 ` rguenth at gcc dot gnu.org
2015-10-21 14:46 ` ranjan.amit8 at gmail dot com
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: rguenth at gcc dot gnu.org @ 2015-10-21 14:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I was saying that LTO now makes it appear like it uses target attributes to
change this kind of property and this is because the rs6000.opt file tells
it that it can do this. But then when it does things fail.
I think the code still passes on -mcpu=e6500 to the link stage thus you
get
int __attribute__((target("cpu=e6500"))) main()
{
}
compiled by
$ ./powerpc-pc-linux-gcc test.c -mcpu=e6500
does that work? (without LTO?)
Note I have in my local tree
Index: gcc/lto-opts.c
===================================================================
--- gcc/lto-opts.c (revision 229119)
+++ gcc/lto-opts.c (working copy)
@@ -201,6 +201,12 @@ lto_write_options (void)
&& lto_stream_offload_p)
continue;
+ /* Do not store target-specific options if we target a
+ SWITCHABLE_TARGET target. */
+ if ((cl_options[option->opt_index].flags & CL_TARGET)
+ && SWITCHABLE_TARGET)
+ continue;
+
/* Drop options created from the gcc driver that will be rejected
when passed on to the driver again. */
if (cl_options[option->opt_index].cl_reject_driver)
which would stop us from passing the target options seen at compile-time
as the "default global state" to the link command.
^ permalink raw reply [flat|nested] 13+ messages in thread* [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.
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (2 preceding siblings ...)
2015-10-21 14:28 ` rguenth at gcc dot gnu.org
@ 2015-10-21 14:46 ` ranjan.amit8 at gmail dot com
2015-10-30 4:34 ` ranjan.amit8 at gmail dot com
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: ranjan.amit8 at gmail dot com @ 2015-10-21 14:46 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
--- Comment #4 from martin <ranjan.amit8 at gmail dot com> ---
$ ./powerpc-pc-linux-gcc test.c -mcpu=e6500
does that work? (without LTO?)
Yes, It works without -flto.
^ permalink raw reply [flat|nested] 13+ messages in thread* [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.
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (3 preceding siblings ...)
2015-10-21 14:46 ` ranjan.amit8 at gmail dot com
@ 2015-10-30 4:34 ` ranjan.amit8 at gmail dot com
2015-10-30 9:32 ` rguenther at suse dot de
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: ranjan.amit8 at gmail dot com @ 2015-10-30 4:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
--- Comment #5 from martin <ranjan.amit8 at gmail dot com> ---
Hi Richard,
There are the changes came after gcc-4.9.3 because of that I am getting above
issue, but if I comment these 2 line in file (tree-streamer-in.c &
tree-streamer-out.c) then it resolves the issue I am facing in gcc-5.2.0.
Because of these changes, the gcc-5.2.0 fails but gcc-4.9.3 sources are
working fine.
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=73527b1dbb74fb8a2fcb92627292c1c0334c8364
Index:
===================================================================
--- a/gcc/tree-streamer-in.c 2015-03-27 12:28:59.000000000 +0530
+++ b/gcc/tree-streamer-in.c 2015-10-23 03:09:08.758332929 +0530
@@ -802,7 +802,7 @@ lto_input_ts_function_decl_tree_pointers
/* DECL_STRUCT_FUNCTION is loaded on demand by cgraph_get_body. */
DECL_FUNCTION_PERSONALITY (expr) = stream_read_tree (ib, data_in);
#ifndef ACCEL_COMPILER
- DECL_FUNCTION_SPECIFIC_TARGET (expr) = stream_read_tree (ib, data_in);
+/* DECL_FUNCTION_SPECIFIC_TARGET (expr) = stream_read_tree (ib, data_in);*/
#endif
DECL_FUNCTION_SPECIFIC_OPTIMIZATION (expr) = stream_read_tree (ib, data_in);
===================================================================
--- a/gcc/tree-streamer-out.c 2015-02-26 17:56:11.000000000 +0530
+++ b/gcc/tree-streamer-out.c 2015-10-23 03:09:13.542332646 +0530
@@ -708,7 +708,7 @@ write_ts_function_decl_tree_pointers (st
stream_write_tree (ob, DECL_FUNCTION_PERSONALITY (expr), ref_p);
/* Don't stream these when passing things to a different target. */
if (!lto_stream_offload_p)
- stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_TARGET (expr), ref_p);
+ /* stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_TARGET (expr), ref_p);*/
stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_OPTIMIZATION (expr), ref_p);
}
Thanks,
Martin
^ permalink raw reply [flat|nested] 13+ messages in thread* [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.
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (4 preceding siblings ...)
2015-10-30 4:34 ` ranjan.amit8 at gmail dot com
@ 2015-10-30 9:32 ` rguenther at suse dot de
2021-02-12 18:05 ` [Bug target/68028] [8/9/10/11 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC seurer at gcc dot gnu.org
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: rguenther at suse dot de @ 2015-10-30 9:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 30 Oct 2015, ranjan.amit8 at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
>
> --- Comment #5 from martin <ranjan.amit8 at gmail dot com> ---
> Hi Richard,
>
> There are the changes came after gcc-4.9.3 because of that I am getting above
> issue, but if I comment these 2 line in file (tree-streamer-in.c &
> tree-streamer-out.c) then it resolves the issue I am facing in gcc-5.2.0.
>
> Because of these changes, the gcc-5.2.0 fails but gcc-4.9.3 sources are
> working fine.
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=73527b1dbb74fb8a2fcb92627292c1c0334c8364
>
>
> Index:
> ===================================================================
> --- a/gcc/tree-streamer-in.c 2015-03-27 12:28:59.000000000 +0530
> +++ b/gcc/tree-streamer-in.c 2015-10-23 03:09:08.758332929 +0530
> @@ -802,7 +802,7 @@ lto_input_ts_function_decl_tree_pointers
> /* DECL_STRUCT_FUNCTION is loaded on demand by cgraph_get_body. */
> DECL_FUNCTION_PERSONALITY (expr) = stream_read_tree (ib, data_in);
> #ifndef ACCEL_COMPILER
> - DECL_FUNCTION_SPECIFIC_TARGET (expr) = stream_read_tree (ib, data_in);
> +/* DECL_FUNCTION_SPECIFIC_TARGET (expr) = stream_read_tree (ib, data_in);*/
> #endif
> DECL_FUNCTION_SPECIFIC_OPTIMIZATION (expr) = stream_read_tree (ib, data_in);
>
>
> ===================================================================
> --- a/gcc/tree-streamer-out.c 2015-02-26 17:56:11.000000000 +0530
> +++ b/gcc/tree-streamer-out.c 2015-10-23 03:09:13.542332646 +0530
> @@ -708,7 +708,7 @@ write_ts_function_decl_tree_pointers (st
> stream_write_tree (ob, DECL_FUNCTION_PERSONALITY (expr), ref_p);
> /* Don't stream these when passing things to a different target. */
> if (!lto_stream_offload_p)
> - stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_TARGET (expr), ref_p);
> + /* stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_TARGET (expr), ref_p);*/
> stream_write_tree (ob, DECL_FUNCTION_SPECIFIC_OPTIMIZATION (expr), ref_p);
> }
Yes, those are used to implement the feature I was talking about.
But the issue lies somewhere in the rs6000 backend and thus needs
deeper investigation by one of its maintainers.
^ permalink raw reply [flat|nested] 13+ messages in thread* [Bug target/68028] [8/9/10/11 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (5 preceding siblings ...)
2015-10-30 9:32 ` rguenther at suse dot de
@ 2021-02-12 18:05 ` seurer at gcc dot gnu.org
2021-05-14 9:47 ` [Bug target/68028] [9/10/11/12 " jakub at gcc dot gnu.org
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: seurer at gcc dot gnu.org @ 2021-02-12 18:05 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
seurer at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seurer at gcc dot gnu.org
--- Comment #16 from seurer at gcc dot gnu.org ---
I just tried this on gcc trunk, 10, 9, and even 8 and could not get it to fail.
I tried on a powerpc 8 BE and a different powerpc 8 LE machine.
seurer@genoa:~/tests/gcc$ ~/gcc/git/install/gcc-test/bin/gcc -flto test.c
-mcpu=e6500
seurer@genoa:~/tests/gcc$ ~/gcc/git/install/gcc-10/bin/gcc -flto test.c
-mcpu=e6500
seurer@genoa:~/tests/gcc$ ~/gcc/git/install/gcc-9/bin/gcc -flto test.c
-mcpu=e6500
seurer@genoa:~/tests/gcc$ ~/gcc/git/install/gcc-8/bin/gcc -flto test.c
-mcpu=e6500
seurer@genoa:~/tests/gcc$ cat test.c
#include<stdio.h>
int main()
{
printf("Good\n");
return 0;
}
^ permalink raw reply [flat|nested] 13+ messages in thread* [Bug target/68028] [9/10/11/12 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (6 preceding siblings ...)
2021-02-12 18:05 ` [Bug target/68028] [8/9/10/11 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC seurer at gcc dot gnu.org
@ 2021-05-14 9:47 ` jakub at gcc dot gnu.org
2021-06-01 8:07 ` rguenth at gcc dot gnu.org
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-05-14 9:47 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|8.5 |9.4
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 8 branch is being closed.
^ permalink raw reply [flat|nested] 13+ messages in thread* [Bug target/68028] [9/10/11/12 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (7 preceding siblings ...)
2021-05-14 9:47 ` [Bug target/68028] [9/10/11/12 " jakub at gcc dot gnu.org
@ 2021-06-01 8:07 ` rguenth at gcc dot gnu.org
2022-05-27 9:35 ` [Bug target/68028] [10/11/12/13 " rguenth at gcc dot gnu.org
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: rguenth at gcc dot gnu.org @ 2021-06-01 8:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|9.4 |9.5
--- Comment #18 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 9.4 is being released, retargeting bugs to GCC 9.5.
^ permalink raw reply [flat|nested] 13+ messages in thread* [Bug target/68028] [10/11/12/13 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (8 preceding siblings ...)
2021-06-01 8:07 ` rguenth at gcc dot gnu.org
@ 2022-05-27 9:35 ` rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug target/68028] [11/12/13/14 " rguenth at gcc dot gnu.org
11 siblings, 0 replies; 13+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-05-27 9:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|9.5 |10.4
--- Comment #19 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 9 branch is being closed
^ permalink raw reply [flat|nested] 13+ messages in thread* [Bug target/68028] [10/11/12/13 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (9 preceding siblings ...)
2022-05-27 9:35 ` [Bug target/68028] [10/11/12/13 " rguenth at gcc dot gnu.org
@ 2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug target/68028] [11/12/13/14 " rguenth at gcc dot gnu.org
11 siblings, 0 replies; 13+ messages in thread
From: jakub at gcc dot gnu.org @ 2022-06-28 10:31 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.4 |10.5
--- Comment #20 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 10.4 is being released, retargeting bugs to GCC 10.5.
^ permalink raw reply [flat|nested] 13+ messages in thread* [Bug target/68028] [11/12/13/14 regression] Compilation error "lto1: error: target attribute or pragma changes single precision floating point" with LTO on PowerPC
2015-10-20 10:31 [Bug lto/68028] New: 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 ranjan.amit8 at gmail dot com
` (10 preceding siblings ...)
2022-06-28 10:31 ` jakub at gcc dot gnu.org
@ 2023-07-07 10:30 ` rguenth at gcc dot gnu.org
11 siblings, 0 replies; 13+ messages in thread
From: rguenth at gcc dot gnu.org @ 2023-07-07 10:30 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68028
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.5 |11.5
--- Comment #21 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 10 branch is being closed.
^ permalink raw reply [flat|nested] 13+ messages in thread