[Bug c++/113599] New: Wrong computation of member offset through pointer-to-member

2024-01-25 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113599 Bug ID: 113599 Summary: Wrong computation of member offset through pointer-to-member Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug c++/111374] New: Spurious -Warray-bounds warning when building std::vector (or libstdc++ bug?)

2023-09-11 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111374 Bug ID: 111374 Summary: Spurious -Warray-bounds warning when building std::vector (or libstdc++ bug?) Product: gcc Version: 14.0 Status: UNCONFIRMED Severity:

[Bug libstdc++/108288] Deadlock when using -fno-elide-constructor + -D_GLIBCXX_DEBUG=1 + -std=c++11

2023-01-05 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108288 --- Comment #8 from Simon Marchi --- I tested with just patching my /usr/include, and it looks like it works fine, I'm able to run a program under my GDB. Removing the fix, I get back the hang.

[Bug libstdc++/108288] Deadlock when using -fno-elide-constructor + -D_GLIBCXX_DEBUG=1 + -std=c++11

2023-01-05 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108288 --- Comment #6 from Simon Marchi --- Because some code trying to acquire the lock (see frame #7 in my backtrace) is in debug.cc, I thought it would maybe need to be changed too? But I don't really understand any of this.

[Bug libstdc++/108288] Deadlock when using -fno-elide-constructor + -D_GLIBCXX_DEBUG=1 + -std=c++11

2023-01-05 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108288 --- Comment #4 from Simon Marchi --- Thanks for looking into this so quickly. I'll try to test the patch against my use case, but I might need some guidance. I know how to build gcc and install it in some non-default prefix. But then, do I

[Bug libstdc++/108288] New: Deadlock when using -fno-elide-constructor + -D_GLIBCXX_DEBUG=1 + -std=c++11

2023-01-04 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108288 Bug ID: 108288 Summary: Deadlock when using -fno-elide-constructor + -D_GLIBCXX_DEBUG=1 + -std=c++11 Product: gcc Version: 12.2.0 Status: UNCONFIRMED

[Bug debug/107414] dwarf 5 C macro support

2022-10-26 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107414 Simon Marchi changed: What|Removed |Added CC||simon.marchi at polymtl dot ca ---

[Bug c++/81159] New warning idea: -Wself-move

2022-08-26 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81159 --- Comment #11 from Simon Marchi --- Awesome, thanks!

[Bug debug/105088] Small DWARF 5 spec violation in line table when passing an absolute path

2022-03-28 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105088 --- Comment #1 from Simon Marchi --- Looking at the .s, I see that gcc attempts to pass "/tmp/cwd/test.c" as the name of the file at index 0: .file 0 "/home/simark" "/tmp/cwd/test.c" If gas did put "/tmp/cwd/test.c" as the name in the line

[Bug debug/105088] New: Small DWARF 5 spec violation in line table when passing an absolute path

2022-03-28 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105088 Bug ID: 105088 Summary: Small DWARF 5 spec violation in line table when passing an absolute path Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity:

[Bug libstdc++/101659] _GLIBCXX_DEBUG mode for std::optional ?

2021-07-29 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101659 Simon Marchi changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/101659] New: _GLIBCXX_DEBUG mode for std::optional ?

2021-07-28 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101659 Bug ID: 101659 Summary: _GLIBCXX_DEBUG mode for std::optional ? Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug debug/101378] Negative DW_AT_data_member_location

2021-07-08 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378 --- Comment #1 from Simon Marchi --- I bisected, it started with: libstdc++: Remove inheritance from elements in std::tuple 91e6226f880b048275a7ceedef716e159c7cefd9 So it's likely related to the use of [[no_unique_address]]. Relevant thread

[Bug debug/101378] New: Negative DW_AT_data_member_location

2021-07-08 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378 Bug ID: 101378 Summary: Negative DW_AT_data_member_location Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug

[Bug debug/100610] New: DWARF5, wrong include_directories[0] when building in /

2021-05-15 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100610 Bug ID: 100610 Summary: DWARF5, wrong include_directories[0] when building in / Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug debug/100446] GDB has problems reading GCC's debugging info level -g3

2021-05-12 Thread simon.marchi at polymtl dot ca via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100446 Simon Marchi changed: What|Removed |Added CC||simon.marchi at polymtl dot ca ---