[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 Ian Lance Taylor changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 --- Comment #10 from CVS Commits --- The master branch has been updated by Ian Lance Taylor : https://gcc.gnu.org/g:325e70b47c6c321710c7b9c792b8fbee95cecd63 commit r11-6779-g325e70b47c6c321710c7b9c792b8fbee95cecd63 Author: Ian Lance Taylor

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread mark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 --- Comment #9 from Mark Wielaard --- (In reply to Mark Wielaard from comment #7) > (In reply to Ian Lance Taylor from comment #5) > > I'm not seeing any failures in the Go testsuite with GNU binutils 2.35.1. > > Anybody know what changed in

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread mark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 --- Comment #8 from Mark Wielaard --- (In reply to Ian Lance Taylor from comment #6) > On the other hand the libbacktrace testsuite now fails when using dwz > 0.13+20201015-2. But I guess that is not a GCC problem. > > dwz -m

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread mark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 --- Comment #7 from Mark Wielaard --- (In reply to Ian Lance Taylor from comment #5) > I'm not seeing any failures in the Go testsuite with GNU binutils 2.35.1. > Anybody know what changed in newer version of the binutils? The difference is

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 --- Comment #6 from Ian Lance Taylor --- On the other hand the libbacktrace testsuite now fails when using dwz 0.13+20201015-2. But I guess that is not a GCC problem. dwz -m b3test_dwz_common.debug b3test_dwz_1 b3test_dwz_2 dwz: b3test_dwz_1:

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread ian at airs dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 Ian Lance Taylor changed: What|Removed |Added CC||ian at airs dot com --- Comment #5

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 Jakub Jelinek changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 --- Comment #3 from Jakub Jelinek --- So, seems when asan alloca_big_alignment test is built with -gdwarf-4 -flto, we have: Offset: 0x57 Length: 214 DWARF Version: 4 Prologue

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 --- Comment #2 from Jakub Jelinek --- The failed asan tests are all with -flto, and the changes in the output are from: WRITE of size 1 at 0x7ffeab2b5d8a thread T0 #0 0x401288 in foo

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-18 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 Richard Biener changed: What|Removed |Added Target Milestone|--- |11.0 Priority|P3

[Bug debug/98716] [11 Regression] sanitizer regressions by r11-6755

2021-01-17 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98716 Jakub Jelinek changed: What|Removed |Added CC||ian at gcc dot gnu.org,