[Bug c++/116889] source_location line number off-by-one when implicitly converting to a type with a defaulted source_location argument

2024-09-29 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116889 --- Comment #2 from Oliver Rosten --- Excellent!

[Bug libstdc++/116889] New: source_location line number off-by-one when implicitly converting to a type with a defaulted source_location argument

2024-09-29 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116889 Bug ID: 116889 Summary: source_location line number off-by-one when implicitly converting to a type with a defaulted source_location argument Product: gcc Versio

[Bug target/109494] inline const variables interfere with source_location

2023-04-16 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109494 --- Comment #12 from Oliver Rosten --- Yes, I am aware that I homebrewed gcc. What I don't understand is the extent to which this a homebrew problem and not a gcc problem. Forgive my ignorance but I would like to understand what submitting this

[Bug target/109494] inline const variables interfere with source_location

2023-04-15 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109494 --- Comment #10 from Oliver Rosten --- Can do, but I don't have sufficient understanding to understand why! Can you kindly explain?

[Bug target/109494] inline const variables interfere with source_location

2023-04-15 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109494 --- Comment #8 from Oliver Rosten --- Created attachment 54870 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54870&action=edit Output from gcc -v

[Bug target/109494] inline const variables interfere with source_location

2023-04-15 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109494 --- Comment #6 from Oliver Rosten --- I've added a simple makefile to the project: https://github.com/ojrosten/SourceLoc

[Bug target/109494] inline const variables interfere with source_location

2023-04-13 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109494 --- Comment #3 from Oliver Rosten --- Created attachment 54852 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54852&action=edit Preprocessed file for Test.cpp

[Bug target/109494] inline const variables interfere with source_location

2023-04-13 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109494 --- Comment #2 from Oliver Rosten --- Created attachment 54851 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54851&action=edit Preprocessed file

[Bug c++/109494] New: inline const variables interfere with source_location

2023-04-13 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109494 Bug ID: 109494 Summary: inline const variables interfere with source_location Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Com

[Bug other/89856] `ld: warning: direct access to global weak symbol means the weak symbol cannot be overridden at runtime` using LTO with optimization and -fprofile-generate

2023-04-12 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89856 --- Comment #6 from Oliver Rosten --- If you're sure. The only thing which gives me pause for thought is that the problem I see with source_location only occurs when I also see ld: warning: direct access to global weak symbol means the weak sym

[Bug other/89856] `ld: warning: direct access to global weak symbol means the weak symbol cannot be overridden at runtime` using LTO with optimization and -fprofile-generate

2023-04-12 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89856 Oliver Rosten changed: What|Removed |Added CC||oliver.rosten at googlemail dot co

[Bug c++/108974] New: std::barrier except completion function which is not manifestly noexcept

2023-02-28 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108974 Bug ID: 108974 Summary: std::barrier except completion function which is not manifestly noexcept Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: nor

[Bug c++/96848] Inherited conditionally explicit constructors via using declaration do not enforce explicitness if dependent on template parameter

2023-02-20 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96848 Oliver Rosten changed: What|Removed |Added CC||oliver.rosten at googlemail dot co

[Bug c++/104575] New: noexcept operator rejects call to templated base class member function

2022-02-16 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104575 Bug ID: 104575 Summary: noexcept operator rejects call to templated base class member function Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: norma

[Bug c++/104411] New: Cannot capture by reference using braced initializer

2022-02-06 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104411 Bug ID: 104411 Summary: Cannot capture by reference using braced initializer Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug c++/104410] New: Internal error using default-initialized constexpr bool in requires clause

2022-02-06 Thread oliver.rosten at googlemail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104410 Bug ID: 104410 Summary: Internal error using default-initialized constexpr bool in requires clause Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: n