[Bug debug/88730] New: gcc generates wrong debug information at -Og

2019-01-06 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- Unlike PR88686, it happens at -Og. The correct value of j should be 5. At "-Og", gdb prints "j = 2" incorrectly. $ gcc-trunk -v Using built-in specs. C

[Bug debug/88730] gcc generates wrong debug information at -Og

2019-01-06 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88730 --- Comment #1 from Qirun Zhang --- It appears to be a regression in 8.X.

[Bug debug/88882] New: gcc generates wrong debug information at -O1

2019-01-16 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It incorrectly prints "l = 0" at -O1. CC'ing alex.. $ gcc-trunk -v Using built-in specs. COLLECT_GCC=gcc-trunk COLLECT_LTO_WRAPPER=/home/absozero/trunk/root-g

[Bug debug/88686] New: gcc generates wrong debug information at -O1

2019-01-03 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- I have reported this bug at gdb bugzilla(https://sourceware.org/bugzilla/show_bug.cgi?id=24032). However, it appears to be a gcc bug. I can reproduce the bug with &quo

[Bug debug/88686] gcc generates wrong debug information at -O1

2019-01-03 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88686 --- Comment #1 from Qirun Zhang --- The output should be "j=0". However, it incorrectly prints "j=1" at -O1.

[Bug rtl-optimization/89528] Wrong debug info generated at -Og [gcc-trunk]

2019-03-31 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89528 Qirun Zhang changed: What|Removed |Added CC||qrzhang at gatech dot edu --- Comment #2

[Bug rtl-optimization/88730] [8 Regression] gcc generates wrong debug information at -Og

2019-03-31 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88730 --- Comment #4 from Qirun Zhang --- Bisection points to r254888.

[Bug debug/89791] gcc generates wrong debug information at -O3

2019-03-31 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89791 Qirun Zhang changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug debug/89792] gcc generates wrong debug information at -O3

2019-03-31 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89792 Qirun Zhang changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug debug/89530] Wrong debug informations for C array generated at -Og [gcc-trunk]

2019-03-20 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89530 Qirun Zhang changed: What|Removed |Added CC||qrzhang at gatech dot edu --- Comment #8

[Bug debug/89463] debug information for iteractor of an empty loop is gone (at -O3)

2019-03-25 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89463 --- Comment #9 from Qirun Zhang --- (In reply to Richard Biener from comment #8) > Patch posted here: https://gcc.gnu.org/ml/gcc-patches/2019-03/msg01192.html > > Some of your bugs might turn out as duplicates if they are fixed by that > patch.

[Bug debug/89801] New: gcc generates wrong debug information at -O2

2019-03-22 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It affects gcc-6 to gcc-trunk. gcc-5 works fine. Bisect points to r222305. $ gcc-trunk -v gcc version 9.0.1 20190322 (experimental) [trunk revision 269869] (GCC) $ gdb -v

[Bug debug/88882] gcc generates wrong debug information at -O1

2019-03-31 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2 --- Comment #2 from Qirun Zhang --- Bisection points to r216247.

[Bug debug/89529] Wrong debug info generated at -Og [gcc-trunk]

2019-03-31 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89529 Qirun Zhang changed: What|Removed |Added CC||qrzhang at gatech dot edu --- Comment #3

[Bug debug/89905] New: gcc generates wrong debug information at -Og

2019-04-01 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It affects gcc-8 to trunk. Gcc-7 works fine. Bisection points to r247596. The correct value is "i=830100328". However, with "-Og", gdb outputs "i

[Bug debug/89454] New: gcc generates wrong debug information at -Og

2019-02-22 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It bug affects the latest trunk. It also affects gcc-8 to gcc-4.8. With "-Og", it incorrectly prints "l=0". $ gcc-trunk -v Using built-in specs. C

[Bug debug/89463] New: gcc generates wrong debug information at -O3

2019-02-22 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It bug affects the latest trunk. It also affects gcc-8 and gcc-7. gcc-6 works fine. With "-O3", it incorrectly prints "i=0". $ gcc-trunk -v

[Bug debug/89463] debug information for iteractor of an empty loop is gone (at -O3)

2019-02-22 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89463 --- Comment #2 from Qirun Zhang --- (In reply to Andrew Pinski from comment #1) > What is happening is the empty loop is being removed and not replaced with a > debug statement say i is 6 afterwards. I don't know if this is a good idea > to put

[Bug debug/89463] debug information for iteractor of an empty loop is gone (at -O3)

2019-03-21 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89463 --- Comment #4 from Qirun Zhang --- Bisect points to r151362. commit ff79704e04af919c4fe501c7dceca8b21cced614 Author: aoliva Date: Thu Sep 3 05:24:57 2009 + * toplev.c (process_options): Enable var-tracking-assignments by

[Bug debug/89791] New: gcc generates wrong debug information at -O3

2019-03-21 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It affects gcc-4.6 to gcc-trunk. The expected output is "i=7" or . With "-O3", it outputs "i=0". I am using two files since "noipa&qu

[Bug debug/89454] gcc generates wrong debug information at -Og

2019-03-21 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89454 --- Comment #1 from Qirun Zhang --- Bisect points to r151362. commit ff79704e04af919c4fe501c7dceca8b21cced614 Author: aoliva Date: Thu Sep 3 05:24:57 2009 + * toplev.c (process_options): Enable var-tracking-assignments by

[Bug debug/89463] debug information for iteractor of an empty loop is gone (at -O3)

2019-03-21 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89463 --- Comment #5 from Qirun Zhang --- (In reply to Qirun Zhang from comment #4) > Bisect points to r151362. > > commit ff79704e04af919c4fe501c7dceca8b21cced614 > Author: aoliva > Date: Thu Sep 3 05:24:57 2009 + > > * toplev.c

[Bug debug/89463] debug information for iteractor of an empty loop is gone (at -O3)

2019-03-21 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89463 --- Comment #6 from Qirun Zhang --- As mentioned in my earlier comment, the revision should be between gcc-5 and gcc-6. Bisect points to r239357. commit ec969ce4161538b561592a032eca6dcfaf513596 Author: rguenth Date: Thu Aug 11 09:02:04

[Bug debug/89454] gcc generates wrong debug information at -Og

2019-03-21 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89454 --- Comment #2 from Qirun Zhang --- (In reply to Qirun Zhang from comment #1) > Bisect points to r151362. > > commit ff79704e04af919c4fe501c7dceca8b21cced614 > Author: aoliva > Date: Thu Sep 3 05:24:57 2009 + > > * toplev.c

[Bug debug/89792] gcc generates wrong debug information at -O3

2019-03-21 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89792 --- Comment #1 from Qirun Zhang --- This might be a latent issue. Attaching my gcc version: $ gcc-trunk -v Thread model: posix gcc version 9.0.1 20190321 (experimental) [trunk revision 269832] (GCC) $ gcc-7 -v Thread model: posix gcc version

[Bug debug/89792] New: gcc generates wrong debug information at -O3

2019-03-21 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It affects gcc-8 and gcc-trunk. gcc-7 works fine. The testcase looks similar to Bug 89463. But they affect different gcc versions and bisect points to different revisions

[Bug debug/90017] New: gcc generates wrong debug information at -O3

2019-04-08 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It seems to be a recent regression, starting at r269302. It only affects "-O3" and trunk. The correct value is "l=0". With -O3, it generates l=8. $ gcc-

[Bug debug/90074] New: wrong debug info at -O3

2019-04-12 Thread qrzhang at gatech dot edu
Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It's a latent issue which affects 4.8-6, and 8-trunk. Gcc-7 works fine. It happens at -O3 only. Bisect between gcc-7 and gcc-8 points to r255267. $ gcc-trunk -v gcc version 9.0.1 20190412

[Bug debug/90017] gcc generates wrong debug information at -O3

2019-04-11 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90017 --- Comment #3 from Qirun Zhang --- (In reply to Alexandre Oliva from comment #2) > This odd behavior is an artifact of the way GCC lays out the basic blocks, > and how GDB interprets the line number program. > > The blocks containing the

[Bug debug/90716] New: gcc generates wrong debug information at -O2

2019-06-02 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- This is a recent regression. Gcc-8 works fine. Bisect points to r271553. The expected value of "j" should be 8. With optimization, it prints "0".

[Bug debug/90946] New: gcc generates wrong debug information at -O3

2019-06-19 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It affects the trunk at "-O3". The expected output is "105487". However, at -O3, it prints "40369". Bisect points to r270902. $ gcc-trunk

[Bug debug/90336] New: gcc generates wrong debug information at -O1 to -O3

2019-05-03 Thread qrzhang at gatech dot edu
Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- This is a recent regression. Gcc-8 works fine. Bisect points to r260253. The expected value of "l_90" should be 852. With optimization, it prints "-1

[Bug debug/90131] New: wrong debug info at -O3

2019-04-17 Thread qrzhang at gatech dot edu
Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- This issue is similar to bug 90074 --- same flag, same gcc versions. The bisection also points to r255267. It appears that the issue remains after the patch. $ gcc-trunk -v gcc version 9.0.1

[Bug debug/92444] gcc generates wrong debug information at -O2 and -O3

2019-11-10 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92444 Qirun Zhang changed: What|Removed |Added CC||hubicka at gcc dot gnu.org --- Comment #1

[Bug debug/92444] New: gcc generates wrong debug information at -O2 and -O3

2019-11-10 Thread qrzhang at gatech dot edu
Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It seems to be a recent regression. gcc-9 works fine. The expected output is 1. With "-O2" and "-O3", gdb outputs 8. $ gcc-trunk -v Suppo

[Bug debug/92417] gcc generates wrong debug information at -O2

2019-11-09 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92417 Qirun Zhang changed: What|Removed |Added CC||hubicka at gcc dot gnu.org --- Comment #1

[Bug debug/92387] gcc generates wrong debug information at -O1

2019-11-09 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92387 Qirun Zhang changed: What|Removed |Added CC||hubicka at gcc dot gnu.org --- Comment #2

[Bug debug/92387] New: gcc generates wrong debug information at -O1

2019-11-05 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It seems to be a recent regression. gcc-9 works fine. The expected value of i should be 0 or opt-out. However, with "-O1", gdb outputs "i=1". $ gcc-t

[Bug debug/92417] New: gcc generates wrong debug information at -O2

2019-11-07 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It happens at O2 only. "-O1" and "-O3" works fine. It's a recent regression since "gcc-9 -O2" also works. The expected value of l_1162[0][0]

[Bug debug/92468] gcc generates wrong debug information at -O2 and -O3

2019-11-11 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92468 Qirun Zhang changed: What|Removed |Added CC||aoliva at gcc dot gnu.org --- Comment #1

[Bug debug/92468] New: gcc generates wrong debug information at -O2 and -O3

2019-11-11 Thread qrzhang at gatech dot edu
Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It affects the trunk and both 8 and 9 releases. Gcc-7 works fine. The expected output is k=0 or opt-out. With O2 and O3, gdb outputs k=1. $ gcc-trunk -v gcc version

[Bug debug/93941] New: gcc generates wrong debug information at -O2

2020-02-25 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a recent regression. My bisect points to g:82e8e335f917b9ce40801838c (needs double check). $ gcc-trunk -v gcc version 10.0.1 20200225 (experimental

[Bug debug/94018] New: gcc generates wrong debug information at -Og

2020-03-03 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a recent regression. Gcc-9 works fine. It happens at -Og only. Bisection points to g:ec8ac265ff21fb379ac072848561a91e4990c47f $ gcc-trunk -v gcc version

[Bug debug/94005] New: gcc generates wrong debug information at -Og

2020-03-02 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a regression in gcc-9. bisection points to g:36f6476b80ca559ff0fc436d2ab84130b The value of l at line 11 is 153. At -Og it generates l=0. O3 and O2 works

[Bug debug/93954] gcc generates wrong debug information at -O3

2020-02-26 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93954 --- Comment #2 from Qirun Zhang --- (In reply to Andrew Pinski from comment #1) > >Bisection points to g:bd2b9f1e2d67ec8e88c977154ecfee > > My bet is if you put a break point at "i--;" you would get the incorrect > answer before that patch. >

[Bug debug/93954] New: gcc generates wrong debug information at -O3

2020-02-26 Thread qrzhang at gatech dot edu
: debug Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a regression in gcc-8. The code is pretty self-explanatory. Bisection points to g:bd2b9f1e2d67ec8e88c977154ecfee $ gcc-trunk -v gcc version 10.0.1

[Bug tree-optimization/93586] [10 Regression] wrong code at -O1 on x86_64-linux-gnu

2020-02-04 Thread qrzhang at gatech dot edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93586 --- Comment #2 from Qirun Zhang --- (In reply to Andrew Pinski from comment #1) > (In reply to Qirun Zhang from comment #0) > > commit ede31f6ffe73357705e95016046e77c7e3d6ad13 > > Author: Jan Hubicka > > Date: Tue Oct 1 21:46:09 2019 +0200 >

[Bug tree-optimization/93586] New: wrong code at -O1 on x86_64-linux-gnu

2020-02-04 Thread qrzhang at gatech dot edu
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- The master branch version of gcc miscompiles the code at -O1 and above. It seems to be a recent regression. gcc-9 works fine. Bisection points to: commit

[Bug tree-optimization/93820] New: wrong code at -O3 on x86_64-linux-gnu

2020-02-18 Thread qrzhang at gatech dot edu
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a regression in 9.x. Gcc-8.3 works fine. Bisection points to: g:be43a8877e2f2f4590ba667b27a24a0cfdf8141d $ gcc-trunk -v gcc version 10.0.1 20200218

[Bug tree-optimization/93767] New: wrong code at -O3 on x86_64-linux-gnu

2020-02-16 Thread qrzhang at gatech dot edu
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a regression in 8.X. Gcc-7.4 works fine. Bisection points to: g:a57776a11369621f9e9e8a8a3db6cb406c8bf27b $ gcc-trunk -v gcc version 10.0.1 20200216

[Bug tree-optimization/93843] New: wrong code at -O3 on x86_64-linux-gnu

2020-02-19 Thread qrzhang at gatech dot edu
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- A recent regression. Gcc-9 works fine. Bisection points to g:6271dd984d7f920d4fb17ad37af6a1f8e6b796dc $ gcc-trunk -v gcc version 10.0.1 20200219 (experimental) [master

[Bug tree-optimization/94125] New: wrong code at -O3 on x86_64-linux-gnu

2020-03-10 Thread qrzhang at gatech dot edu
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a regression in 9. Gcc-8.3 works fine. Bisection points to g:8f70fdc31a7b0099e7322d0aba94830fb08f4c88 $ gcc-trunk -v gcc version 10.0.1 20200310

[Bug tree-optimization/94567] New: wrong code at -O2 and -O3 on x86_64-linux-gnu

2020-04-11 Thread qrzhang at gatech dot edu
: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It's a recent regression. Bisection points to g:529ea7d9596b26ba103578eeab $ gcc-trunk -v gcc version 10.0.1 20200411 (experimental) [master revision

[Bug tree-optimization/94724] New: wrong code at -O0 on x86_64-linux-gnu

2020-04-22 Thread qrzhang at gatech dot edu
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It happens at -O0. gcc-9 works fine. Bisection points to g:ca6c722561ce9b9dc7b59cfd9d2 The correct output is 1. $ gcc-trunk -v gcc version 10.0.1 20200422

[Bug tree-optimization/95172] New: wrong code at -O1 on x86_64-linux-gnu

2020-05-16 Thread qrzhang at gatech dot edu
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- Recent regression. Bisection points to g:b6ff3ddecfa93d53867afaaa078f85f $ gcc-trunk -v gcc version 11.0.0 20200516 (experimental) [master revision 53b4d52f114

[Bug tree-optimization/95045] New: wrong code at -O3 on x86_64-linux-gnu

2020-05-10 Thread qrzhang at gatech dot edu
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- Recent regression. Bisection points to g:283cb9ea6293e813e4 $ gcc-trunk -v gcc version 11.0.0 20200510 (experimental) [master revision 4ae915cdbf0:8eedda9eef3

[Bug tree-optimization/101025] [11 Regression] wrong code at -O3 on x86_64-linux-gnu

2021-06-11 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101025 --- Comment #8 from Qirun Zhang --- (In reply to Richard Biener from comment #7) > Fixed on trunk sofar. Keep more testcases coming ;) (I have a hunch this > code has more issues...) Thanks, Richard. Will do.

[Bug tree-optimization/101173] wrong code at -O3 on x86_64-linux-gnu

2021-06-22 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101173 --- Comment #1 from Qirun Zhang --- My bisection points to g:fbdec14e80e9399cd301ed3

[Bug tree-optimization/101173] New: wrong code at -O3 on x86_64-linux-gnu

2021-06-22 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It affects gcc-8 to the trunk. Gcc-7.5.0 works. $ gcc-trunk -v Supported LTO compression algorithms: zlib gcc version 12.0.0 20210622 (experimental) [master revision

[Bug tree-optimization/101001] New: wrong code at -O3 on x86_64-linux-gnu

2021-06-09 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It affects gcc-8 to the trunk. Gcc-7 works fine. $ gcc-trunk -v gcc version 12.0.0 20210609 (experimental) [master revision 174e75a2107:3b61ba37fe1

[Bug tree-optimization/101105] wrong code at -O3 on x86_64-linux-gnu

2021-06-16 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101105 --- Comment #1 from Qirun Zhang --- My bisection points to g:f75211822f8d84bb706421

[Bug tree-optimization/101105] New: wrong code at -O3 on x86_64-linux-gnu

2021-06-16 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a regression in 11. $ gcc-trunk -v Configured with: ../gcc/configure --prefix=/nethome/qzhang414/trunk/root-gcc --enable-languages=c,c++ --disable

[Bug tree-optimization/101025] New: wrong code at -O3 on x86_64-linux-gnu

2021-06-10 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a recent regression. Bisection points to g:128f43cf679e51564202b41f23fae4146347f93d $ gcc-trunk -v Supported LTO compression algorithms: zlib gcc

[Bug tree-optimization/101031] New: wrong code at -O2 on x86_64-linux-gnu

2021-06-11 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a recent regression. $ gcc-trunk -v Supported LTO compression algorithms: zlib gcc version 12.0.0 20210611 (experimental) [master revision

[Bug tree-optimization/101031] wrong code at -O2 on x86_64-linux-gnu

2021-06-11 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101031 Qirun Zhang changed: What|Removed |Added CC||rguenther at suse dot de --- Comment #1

[Bug tree-optimization/101972] New: wrong code at -O2 on x86_64-linux-gnu

2021-08-18 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a regression in gcc-9. gcc-8 works fine. $ gcc-trunk -O2 abc.c ; ./a.out 0 $ gcc-trunk abc.c ; ./a.out 30 $ gcc-8 -O2 abc.c ; ./a.out 30 $ cat

[Bug tree-optimization/101972] wrong code at -O2 on x86_64-linux-gnu

2021-08-18 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101972 --- Comment #1 from Qirun Zhang --- My bisection points to g:a81e2c6240655f60a49c16e0d8bbfd2ba40bba51

[Bug tree-optimization/102149] New: wrong code at -O3 on x86_64-linux-gnu

2021-08-31 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- Seems to be a recent regression. $ gcc-trunk -v gcc version 12.0.0 20210831 (experimental) [master revision 5e57bacf6f3

[Bug tree-optimization/102149] wrong code at -O3 on x86_64-linux-gnu

2021-08-31 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102149 --- Comment #1 from Qirun Zhang --- My bisection points to g:89f33f44addbf9853bc3e6677d

[Bug tree-optimization/101445] New: wrong code at -O3 on x86_64-linux-gnu

2021-07-13 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a recent regression. Note that -O2 works fine. $ gcc-trunk -v Supported LTO compression algorithms: zlib gcc version 12.0.0 20210713 (experimental

[Bug tree-optimization/101445] wrong code at -O3 on x86_64-linux-gnu

2021-07-13 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101445 --- Comment #1 from Qirun Zhang --- My bisection points to g:f75211822f8d84bb706421d3692e

[Bug tree-optimization/101885] New: wrong code at -O3 on x86_64-linux-gnu

2021-08-12 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears a regression in gcc-10. gcc-9 works fine. $ gcc-trunk -v gcc version 12.0.0 20210812 (experimental) [master revision 01f8a8b48e5:0eb7800d242

[Bug tree-optimization/101885] wrong code at -O3 on x86_64-linux-gnu

2021-08-12 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101885 --- Comment #1 from Qirun Zhang --- My bisection points to g:529ea7d9596b26ba103578eeab448e9862a2d2c5

[Bug tree-optimization/101501] New: wrong code at -O3 on x86_64-linux-gnu

2021-07-18 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a recent regression. Gcc-10 works fine. $ gcc-trunk -v gcc version 12.0.0 20210718 (experimental) [master revision 0103d18dfc9:a1cef02c5e3

[Bug tree-optimization/101501] wrong code at -O3 on x86_64-linux-gnu

2021-07-18 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101501 --- Comment #1 from Qirun Zhang --- My bisection points to g:287522613d661b4c5ba8403b051eb470c1674cba

[Bug tree-optimization/101615] New: wrong code at -O3 on x86_64-linux-gnu

2021-07-24 Thread qrzhang at gatech dot edu via Gcc-bugs
-optimization Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu Target Milestone: --- It appears to be a recent regression. $ gcc-trunk -v Supported LTO compression algorithms: zlib gcc version 12.0.0 20210724 (experimental) [master revision

[Bug tree-optimization/101615] wrong code at -O3 on x86_64-linux-gnu

2021-07-24 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101615 --- Comment #1 from Qirun Zhang --- My bisection points to g:6df6055d5c666e669890ff8

[Bug sanitizer/108845] Unnecessary signed integer overflow checks

2023-02-18 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108845 --- Comment #4 from Qirun Zhang --- (In reply to Qirun Zhang from comment #3) > (In reply to Jakub Jelinek from comment #2) > > I'm not convinced it is a good idea. > > Sure, in the above case it is obvious it will never trigger, but if we say

[Bug sanitizer/108845] New: Unnecessary signed integer overflow checks

2023-02-18 Thread qrzhang at gatech dot edu via Gcc-bugs
: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone

[Bug sanitizer/108995] New: Missed signed integer overflow checks in UBsan?

2023-03-02 Thread qrzhang at gatech dot edu via Gcc-bugs
Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone

[Bug sanitizer/108880] New: slow compilation with "-fsanitize=undefined"

2023-02-21 Thread qrzhang at gatech dot edu via Gcc-bugs
Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: qrzhang at gatech dot edu CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target

[Bug sanitizer/108845] Unnecessary signed integer overflow checks

2023-02-18 Thread qrzhang at gatech dot edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108845 --- Comment #3 from Qirun Zhang --- (In reply to Jakub Jelinek from comment #2) > I'm not convinced it is a good idea. > Sure, in the above case it is obvious it will never trigger, but if we say > use ranger to decide if the operation can or