[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2017-01-12 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 Richard Biener changed: What|Removed |Added Priority|P3 |P2

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-10-17 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 --- Comment #17 from Richard Biener --- I have a fix for that, queued into early LTO debug patches. But the testcase still fails... foo (arg7=arg7@entry=30, arg6=, arg5=, arg4=, arg3=, arg2=, arg1=, arg8=7) at /space/rguenther/src

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-10-17 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 --- Comment #16 from Jakub Jelinek --- Yes, see the #c4 partial patch and the following comments.

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-10-17 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 --- Comment #15 from Richard Biener --- So with LTO early debug I now get proper debug decls but still no locations for the parameters <1><1ff>: Abbrev Number: 10 (DW_TAG_subprogram) <200> DW_AT_abstract_origin: <0x28b> <204> DW_AT_

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-04-29 Thread seurer at linux dot vnet.ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 --- Comment #14 from Bill Seurer --- Dominik Vogt, I've noticed that sort of failure in several of the guality test cases where a test is done at line X but optimization moves the assignment being tested to after line X. Should the tests be adju

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-04-29 Thread vogt at linux dot vnet.ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 --- Comment #13 from Dominik Vogt --- By the way, I think the value of y should be tested *after* the asm statement in line 17 not before it in line 16. At higher optimization levels the assignement may not have happened yet when gdb reaches lin

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-04-28 Thread vogt at linux dot vnet.ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 --- Comment #12 from Dominik Vogt --- We've just been looking at this today for s390x which fails these tests for various reasons too (actually we've located at least four different Gcc bugs by looking at this test case). Some of the calculation

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-04-28 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 --- Comment #11 from Jakub Jelinek --- (In reply to Bill Seurer from comment #9) > The pr36728 and pr68860 test cases that check the arguments (where the > arguments are unused) all currently (and for a long time) fail on power. > They show up a

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-04-28 Thread rguenther at suse dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 --- Comment #10 from rguenther at suse dot de --- On Thu, 28 Apr 2016, seurer at linux dot vnet.ibm.com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 > > Bill Seurer changed: > >What|Removed |

[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1

2016-04-28 Thread seurer at linux dot vnet.ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860 Bill Seurer changed: What|Removed |Added CC||seurer at linux dot vnet.ibm.com --- Comm