https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91322
--- Comment #7 from Christophe Lyon ---
Created attachment 48185
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48185&action=edit
qemu execution trace
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91322
--- Comment #6 from Christophe Lyon ---
Created attachment 48184
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48184&action=edit
GCC passes dumps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91322
--- Comment #5 from Christophe Lyon ---
Created attachment 48183
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48183&action=edit
executable asm from objdump
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94043
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Since r10-7491, I've noticed a regression with an ICE:
FAIL: gcc.target/aarch64/sve/pr87815.c -march=armv8.2-a+sve (internal compiler
error)
/gcc/test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94445
--- Comment #3 from Christophe Lyon ---
I also checked that arm_handle_cmse_nonsecure_call correctly duplicates the
type.
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
I've noticed that when GCC is configured --target arm-none-abi
--with-mode=thumb --with-cpu=cortex-m33, the cmse-15.c test fails:
FAIL: gcc.target/arm/cmse/cmse
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94401
--- Comment #2 from Christophe Lyon ---
The defaults are OK (either native or cross aarch64)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90332
--- Comment #12 from Christophe Lyon ---
> Can you open a new bugreport?
Sure, I filed PR94401
-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
I've noticed that the fix for PR90332 caused a regression on aarch64:
FAIL: gcc.dg/vect/pr92420.c -flto -ffat-lto-objects execution test
FAIL: gcc.dg/vect/pr92
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90332
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94339
--- Comment #2 from Christophe Lyon ---
Created attachment 48123
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48123&action=edit
ada-lang.ii.xz
: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Hi,
I've noticed this ICE while building GDB with recent GCC trunk, it appeared
between: r10-7336 and r10-7346
x86_64-unknown-linux-gnu-g++ -g -O2 -c ada-la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94317
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90378
--- Comment #10 from Christophe Lyon ---
I checked the stack settings on the ARMv7 and ARMv8 machines:
ARMv7: beced000-bed0e000 rw-p 00:00 0 [stack]
ARMv8: fff12000-fff33000 rw-p 00:00 0 [stack]
In both cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90378
--- Comment #8 from Christophe Lyon ---
I also tried to run the program under QEMU, it works (doesn't crash)
||clyon at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #7 from Christophe Lyon ---
I am able to reproduce the failure with the same commit mentioned by Maxim in
comment #3. Using a more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89661
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91724
--- Comment #6 from Christophe Lyon ---
I added --enable-default-pie to my configure options, and it's still
successful.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91724
--- Comment #4 from Christophe Lyon ---
It worked for me with gcc-8-branch at
g:9eba9635f653291804ecb832eebe1ed96e3346ba
Using:
../gcc/configure --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard
--with-mode=thumb --with-build-config=boo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93375
--- Comment #8 from Christophe Lyon ---
(In reply to David Malcolm from comment #7)
> Does the patch in comment #6 fix the remaining test failures for everyone?
It's OK for me on arm, thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91333
--- Comment #13 from Christophe Lyon ---
(In reply to Vladimir Makarov from comment #12)
> (In reply to Christophe Lyon from comment #10)
> > (In reply to Jeffrey A. Law from comment #9)
> > > Fixed by Vlad's patch on the trunk.
> >
> > This pat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91333
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92706
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93473
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93375
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93391
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40752
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93263
--- Comment #15 from Christophe Lyon ---
> Seen on arm too, both master and gcc-9
And aarch64 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93263
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
The test fails on aarch64:
g++.dg/cpp0x/initlist118.C -std=c++14 (internal compiler error)
g++.dg/cpp0x/initlist118.C -std=c++14 (test for excess errors)
g++.dg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36941
--- Comment #11 from Christophe Lyon ---
Author: clyon
Date: Fri Dec 6 10:54:46 2019
New Revision: 279039
URL: https://gcc.gnu.org/viewcvs?rev=279039&root=gcc&view=rev
Log:
[testsuite][aarch64] type_redef_11.c: Update expected diagnostics.
Aft
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88827
--- Comment #3 from Christophe Lyon ---
Author: clyon
Date: Fri Dec 6 10:54:46 2019
New Revision: 279039
URL: https://gcc.gnu.org/viewcvs?rev=279039&root=gcc&view=rev
Log:
[testsuite][aarch64] type_redef_11.c: Update expected diagnostics.
Afte
-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
After commit r278938, I've noticed regressions on aarch64:
FAIL: gcc.target/aarch64/fmla_intrinsic_1.c scan-assembler-times
fmla\\tv[0-9]+.2s, v[0-9]+.2s, v[0-9]+.2s\\
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91975
Bug 91975 depends on bug 92047, which changed state.
Bug 92047 Summary: [10 regression] aarch64 regressions after r276645
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92047
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92047
Christophe Lyon changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91612
Christophe Lyon changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91613
Christophe Lyon changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91615
Christophe Lyon changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92473
--- Comment #2 from Christophe Lyon ---
Created attachment 47218
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47218&action=edit
Execution trace for arm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92473
--- Comment #1 from Christophe Lyon ---
Created attachment 47217
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47217&action=edit
Execution trace for aarch64
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
The test pr92324-2.c introduced at r277958 fails on arm and aarch64:
FAIL: gcc.dg/vect/pr92324-2.c -flto -ffat-lto-objects execution test
FAIL: gcc.dg/vect/pr92324-2.c execution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92333
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208
--- Comment #9 from Christophe Lyon ---
(In reply to Tobias Burnus from comment #8)
> (In reply to Christophe Lyon from comment #7)
> > On gcc-9, the patch introduced regressions, seen on arm and aarch64:
>
> On trunk, the following was needed (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61761
--- Comment #13 from Christophe Lyon ---
It's still failing on trunk:
https://gcc.gnu.org/ml/gcc-testresults/2019-11/msg00131.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61761
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92207
--- Comment #7 from Christophe Lyon ---
When single-stepping in the r277178 executable, the final
=> 0x18bc0 <_malloc_r+1092>:str r3, [r2, #4]
succeeds and
(gdb) p /x $r2
$2 = 0x804aa40
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92207
--- Comment #6 from Christophe Lyon ---
In particular, the execution continues after the last block dumped by qemu:
0x00018e40: e5974008 ldr r4, [r7, #8]
0x00018e44: e0898008 add r8, sb, r8
0x00018e48: e3888001 orr r8, r8, #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92207
--- Comment #3 from Christophe Lyon ---
Created attachment 47104
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47104&action=edit
Execution trace for r277178
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92207
--- Comment #4 from Christophe Lyon ---
Created attachment 47105
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47105&action=edit
Execution trace for r277179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92207
--- Comment #2 from Christophe Lyon ---
Created attachment 47103
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47103&action=edit
Executable from r277179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92207
--- Comment #1 from Christophe Lyon ---
Created attachment 47102
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47102&action=edit
Executable from r277178
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
As discussed in https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01619.html
I have noticed a regression after r277179.
However, it seems tricky to reproduce, and I had to manually
|u |u arm aarch64
CC||clyon at gcc dot gnu.org
--- Comment #1 from Christophe Lyon ---
Seen on arm and aarch64 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92128
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
|u |u aarch64 arm
CC||clyon at gcc dot gnu.org
--- Comment #1 from Christophe Lyon ---
Seen on aarch64 and arm too.
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
I've noticed that r276645 introduced a regression on armeb:
FAIL: gcc.dg/vect/fast-math-vect-pr29925.c scan-tree-dump-times vect
"vectorized 1 loops" 1
ma
: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
After r276645, I've noticed regressions on aarch64:
FAIL: gcc.target/aarch64/sve/index_offset_1.c -march=armv8.2-a+sve
scan-assembler-times ld1b\\tz[0-9]+.b, p[0-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92016
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84487
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91983
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91982
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91909
--- Comment #5 from Christophe Lyon ---
I confirm that the proposed patch fixed the problem for me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91885
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
After r275898, I've noticed a regression on armeb:
FAIL: gcc.dg/vect/vect-cond-4.c execution test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91749
Christophe Lyon changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91749
--- Comment #4 from Christophe Lyon ---
Author: clyon
Date: Tue Sep 17 08:13:11 2019
New Revision: 275799
URL: https://gcc.gnu.org/viewcvs?rev=275799&root=gcc&view=rev
Log:
[PR91749][arm] FDPIC: Handle -mflip-thumb
2019-09-16 Christophe Lyon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91749
Christophe Lyon changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |clyon at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91749
--- Comment #1 from Christophe Lyon ---
Can you share your configure options?
Also, it looks like you are forcing at least -mfdpic when running the
testsuite?
Why did you put "known to work 9.2", since -mfdpic does not exist in that
version?
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Since r274823, this arm test fails:
FAIL: gcc.target/arm/pr53447-5.c scan-assembler-times (ldrd|vldr\\.64) 20
FAIL: gcc.target/arm/pr53447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89188
--- Comment #9 from Christophe Lyon ---
Good point, I just checked with
gcc-linaro-7.4.1-2019.02-x86_64_aarch64-linux-gnu, and it does ICE.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89188
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91684
--- Comment #8 from Christophe Lyon ---
Indeed, it's now unsupported in this config.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91684
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
++
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
The new test introduced at r275403 fails on arm targets:
/libstdc++-v3/testsuite/23_containers/span/get_neg.cc:27: error: call of
overloaded 'span(int*, long unsigned int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36262
--- Comment #16 from Christophe Lyon ---
> Wrong bugzilla? But also should be fixed by the followup.
I replied to the bugzilla mentioned in the ChangeLog...
>
> 2019-09-05 Richard Biener
>
> PR rtl-optimization/91656
> * p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36262
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
Known
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91708
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91603
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91615
--- Comment #7 from Christophe Lyon ---
(In reply to Bernd Edlinger from comment #6)
> Created attachment 46820 [details]
> untested patch
This patch fixes the armeb problems reported here, thanks!
(in addition to the scan-assembler-times issue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91615
--- Comment #5 from Christophe Lyon ---
(In reply to Bernd Edlinger from comment #4)
> Hi Christophe,
>
> many thanks for your invaluable help.
>
> I think except this one all regressions are fixed or
> at least understood.
>
> Unfortunately I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91612
--- Comment #4 from Christophe Lyon ---
> I don't know yet for pr91613
This patch fixes pr91613 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91308
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91612
--- Comment #3 from Christophe Lyon ---
(In reply to Bernd Edlinger from comment #2)
> Created attachment 46792 [details]
> untested patch
>
> This is a untested patch it should fix
> pr91612 pr91613 pr91615 (?)
> pr91603
> and pr91605 (i386)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81740
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91615
--- Comment #1 from Christophe Lyon ---
There are also 2 regressions in gfortran
--target armeb-none-linux-gnueabihf
--with-cpu cortex-a9
--with-fpu neon-fp16
gfortran.dg/vect/no-vfa-pr32377.f90 -O (internal compiler error)
gfortran.dg/vect/p
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Since r274986 with the patch from
https://gcc.gnu.org/ml/gcc-patches/2019-08/msg02018.html, I've noticed ICEs on
armeb (arm big-endian cross compiler):
gcc.c-torture/ex
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91614
--- Comment #1 from Christophe Lyon ---
The same is true
--with-cpu cortex-a57
--with-fpu crypto-neon-fp-armv8
: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Since r274986, even with the patch from
https://gcc.gnu.org/ml/gcc-patches/2019-08/msg02018.html, I've noticed:
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
After r274986, even with the patch from
https://gcc.gnu.org/ml/gcc-patches/2019-08/msg02018.html, I've noticed:
FAIL: gcc.dg/pr83930.c (int
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Since r274985, I've noticed new failures, not fixed by the patch proposed at
https://gcc.gnu.org/ml/gcc-patches/2019-08/msg02018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91457
--- Comment #10 from Christophe Lyon ---
Thanks for the pointer to the glibc discussion.
My understanding is that GCC's warning is legitimate, and won't be removed?
Since this breaks all my validations, I guess the best course of action on my
si
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91457
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
--- Comment #15 from Christophe Lyon ---
Since r274532 (gcc-9-branch), I am seeing:
FAIL: gcc.c-torture/execute/20040709-1.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects execution test
target arm-none-linux-gnueabi
--with-mode arm
--wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
--- Comment #12 from Christophe Lyon ---
Indeed, although r274163 fixes the problem I reported, it also introduces a
regression when compiling the very same testcase but adding -mthumb:
FAIL: gcc.c-torture/execute/20040709-1.c -O2 (internal c
-*-*,
||aarch64-linux-gnu,
||arm*-linux-gnueabihf
CC||clyon at gcc dot gnu.org
--- Comment #13 from Christophe Lyon ---
The new test (gcc.dg/torture/pr91323.c) fails on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42575
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
--- Comment #2 from Christophe Lyon ---
Removing the test*() calls from the end, the first failing one is testX().
However, if I remove all the preceding ones, the test passes.
Using -fwhole-program instead of -flto has no effect: the test still
: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
Hi,
I've noticed that since r273135 (fix for PR91091), there is a regression on
arm-none-linux-gnueabi
--with
501 - 600 of 1134 matches
Mail list logo