[Bug debug/100383] cfi sections directive detection fails with binutils 2.36

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100383

Andrew Pinski  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
   Target Milestone|--- |13.0
 Resolution|--- |FIXED

--- Comment #6 from Andrew Pinski  ---
Fixed by r13-4903-gcf8b110ce33db6 .

[Bug debug/100383] cfi sections directive detection fails with binutils 2.36

[ssbssa at yahoo dot de via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100383

--- Comment #5 from Hannes Domani  ---
This could be closed since gcc-13.1.

[Bug debug/100383] cfi sections directive detection fails with binutils 2.36

[10walls at gmail dot com via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100383

jon_y <10walls at gmail dot com> changed:

   What|Removed |Added

 CC||10walls at gmail dot com

--- Comment #4 from jon_y <10walls at gmail dot com> ---
Pushed to git master.

[Bug debug/100383] cfi sections directive detection fails with binutils 2.36

[jyong at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100383

jyong at gcc dot gnu.org changed:

   What|Removed |Added

   Last reconfirmed||2021-05-03
 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1

--- Comment #3 from jyong at gcc dot gnu.org ---
I can confirm it was detected as no with binutils 2.36, and back to yes after
the grep change.

[Bug debug/100383] cfi sections directive detection fails with binutils 2.36

[jakub at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100383

Jakub Jelinek  changed:

   What|Removed |Added

 CC||jyong at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek  ---
Yes.
win32 | pe | cygwin* | mingw32* specific.

[Bug debug/100383] cfi sections directive detection fails with binutils 2.36

[rguenth at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100383

Richard Biener  changed:

   What|Removed |Added

Version|unknown |10.3.0
 CC||jakub at gcc dot gnu.org
   Keywords||build
  Known to fail||7.5.0

--- Comment #1 from Richard Biener  ---
looks like all branches would be affected.