[Bug debug/104050] '-fcompare-debug' failure w/ -std=c++20 -O1

2024-06-20 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104050

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|12.4|12.5

--- Comment #6 from Richard Biener  ---
GCC 12.4 is being released, retargeting bugs to GCC 12.5.

[Bug debug/104050] '-fcompare-debug' failure w/ -std=c++20 -O1

2023-05-08 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104050

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|12.3|12.4

--- Comment #5 from Richard Biener  ---
GCC 12.3 is being released, retargeting bugs to GCC 12.4.

[Bug debug/104050] '-fcompare-debug' failure w/ -std=c++20 -O1

2022-08-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104050

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|12.2|12.3

--- Comment #4 from Richard Biener  ---
GCC 12.2 is being released, retargeting bugs to GCC 12.3.

[Bug debug/104050] '-fcompare-debug' failure w/ -std=c++20 -O1

2022-05-06 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104050

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|12.0|12.2

--- Comment #3 from Jakub Jelinek  ---
GCC 12.1 is being released, retargeting bugs to GCC 12.2.

[Bug debug/104050] '-fcompare-debug' failure w/ -std=c++20 -O1

2022-04-18 Thread iains at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104050

--- Comment #2 from Iain Sandoe  ---
(In reply to Martin Liška from comment #1)
> Confirmed. Interesting that one needs -save-temps. Likely started with GCC
> 11.

I compared the simple from the FE with -save-temps (FAILS) and without (OK)

the only difference between the two cases is that the temporary numbers are
different by two (the numbers are +2 for the case without save temps).  That is
the same as the difference shown in the report - but not sure how to analyse
that further right now ...

[Bug debug/104050] '-fcompare-debug' failure w/ -std=c++20 -O1

2022-01-17 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104050

Martin Liška  changed:

   What|Removed |Added

Summary|[12 Regression] |'-fcompare-debug' failure
   |[coroutines]|w/ -std=c++20 -O1
   |'-fcompare-debug' failure   |
   |w/ -std=c++20 -O1   |
 Ever confirmed|0   |1
 CC||iains at gcc dot gnu.org,
   ||marxin at gcc dot gnu.org
   Last reconfirmed||2022-01-17
 Status|UNCONFIRMED |NEW

--- Comment #1 from Martin Liška  ---
Confirmed. Interesting that one needs -save-temps. Likely started with GCC 11.