[Bug c++/118951] New: __FILE__ inserts the filename as array, __builtin_FILE as pointer

2025-02-20 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118951 Bug ID: 118951 Summary: __FILE__ inserts the filename as array, __builtin_FILE as pointer Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/114925] include/bits/fs_path.h#L841 deprecation note suggests UB

2024-05-02 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114925 --- Comment #2 from fabian_kessler at gmx dot de --- (In reply to Andrew Pinski from comment #1) > I thought char8_t is still a character type so aliasing wise it falls under > that rule. Actually no. They are distinct types and only 4 types a

[Bug libstdc++/114926] New: Add way to silence deprecation warning for fs::u8path

2024-05-02 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114926 Bug ID: 114926 Summary: Add way to silence deprecation warning for fs::u8path Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Compo

[Bug libstdc++/114925] New: include/bits/fs_path.h#L841 deprecation note suggests UB

2024-05-02 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114925 Bug ID: 114925 Summary: include/bits/fs_path.h#L841 deprecation note suggests UB Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Prio

[Bug debug/110351] gcc does not recognize gcodeview as debuglevel

2023-06-21 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110351 fabian_kessler at gmx dot de changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #2 fro

[Bug debug/110351] New: gcc does not recognize gcodeview as debuglevel

2023-06-21 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110351 Bug ID: 110351 Summary: gcc does not recognize gcodeview as debuglevel Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug libstdc++/110196] stacktrace_entry does not print which library the function was from

2023-06-10 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #11 from fabian_kessler at gmx dot de --- With the following code extension, I get what I want, but this may also be platform dependent: class stacktrace_entry{ // ... std::string _symbol(uintptr_t const pc) const { Dl_info

[Bug libstdc++/110196] stacktrace_entry does not print which library the function was from

2023-06-10 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #10 from fabian_kessler at gmx dot de --- > It is only called once, isn't it? Actually, _S_init is even called in a loop. And the singleton pattern is also a code extension from me. Therefore, backtrace_create_state is also called i

[Bug libstdc++/110196] stacktrace_entry does not print which library the function was from

2023-06-09 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #7 from fabian_kessler at gmx dot de --- To fix this some sort of char ** __backtrace_symbols (void *const *array, int size) must be used internally.

[Bug libstdc++/110196] stacktrace_entry does not print which library the function was from

2023-06-09 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #6 from fabian_kessler at gmx dot de --- output is now ``` 0# main at /mnt/c/Users/Febbe/workspace/test/test/main.cpp:7 1# __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58 2# __libc_start_main_impl at ..

[Bug libstdc++/110196] stacktrace_entry does not print which library the function was from

2023-06-09 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #5 from fabian_kessler at gmx dot de --- Indeed, changing _S_init to the following improved it: ``` static backtrace_state *_S_init() { static backtrace_state *__state = []() { auto getpath = []() -> std::string {

[Bug libstdc++/110196] stacktrace_entry does not print which library the function was from

2023-06-09 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #4 from fabian_kessler at gmx dot de --- Indeed, changing _S_init to the following did the trick: ``` static backtrace_state *_S_init() { static backtrace_state *__state = []() { auto getpath = []() -> std::string {

[Bug libstdc++/110196] stacktrace_entry does not print origin binary filename

2023-06-09 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #3 from fabian_kessler at gmx dot de --- It may be, because backtrace_create_state is called without a filename. Also, backtrace_create_state is ment to be called just once per execution, because it allocates unfreeable memory. Mayb

[Bug libstdc++/110196] stacktrace_entry does not print origin binary filename

2023-06-09 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #2 from fabian_kessler at gmx dot de --- (In reply to Andrew Pinski from comment #1) > I am trying to understand the issue here? > Is what you are asking is that the " at :0" should not be printed out? Or > the issue is the source l

[Bug libstdc++/110196] New: stacktrace_entry does not print origin binary filename

2023-06-09 Thread fabian_kessler at gmx dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 Bug ID: 110196 Summary: stacktrace_entry does not print origin binary filename Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Co