[Bug c++/106584] New: g++ not showing correct line number in "use of deleted function" error

2022-08-11 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106584 Bug ID: 106584 Summary: g++ not showing correct line number in "use of deleted function" error Product: gcc Version: 12.1.1 Status: UNCONFIRMED Severity: norma

[Bug c++/106584] g++ not showing correct line number in "use of deleted function" error

2022-08-11 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106584 --- Comment #1 from Devourer Station --- Created attachment 53436 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53436&action=edit Preprocessed source file compile with g++ example.cpp -c

[Bug c++/106584] g++ not showing correct line number in "use of deleted function" error

2022-08-11 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106584 --- Comment #2 from Devourer Station --- Created attachment 53437 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53437&action=edit compiler's output

[Bug c++/106584] g++ not showing correct line number in "use of deleted function" error

2022-08-11 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106584 --- Comment #5 from Devourer Station --- (In reply to Andrew Pinski from comment #4) > Actually clang references the call: > f(cl); > > When it comes to the copy constructor. At least it tells you about where the error is, otherwise you may fa

[Bug c/102098] New: ICE when #include with -fmodules-ts -std=c++20

2021-08-27 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102098 Bug ID: 102098 Summary: ICE when #include with -fmodules-ts -std=c++20 Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P

[Bug c++/102098] ICE when #include with -fmodules-ts -std=c++20 since r11-7530-g1e5cdb9f896fb220

2021-08-31 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102098 --- Comment #4 from Devourer Station --- Created attachment 51388 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51388&action=edit preprocessed source file (xz compressed) preprocessed source file (xz compressed)

[Bug c++/102098] ICE when #include with -fmodules-ts -std=c++20 since r11-7530-g1e5cdb9f896fb220

2021-08-31 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102098 --- Comment #5 from Devourer Station --- (In reply to Martin Liška from comment #1) > Please attach the source files.. I'm sorry that the attachment suddenly went missing. I reattached it.

[Bug c++/102098] ICE when #include with -fmodules-ts -std=c++20 since r11-7530-g1e5cdb9f896fb220

2022-05-29 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102098 --- Comment #6 from Devourer Station --- Still exists with 11.2.0

[Bug c++/102098] ICE when #include with -fmodules-ts -std=c++20 since r11-7530-g1e5cdb9f896fb220

2023-08-05 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102098 --- Comment #7 from Devourer Station --- Confirmed solved in 13.1.1

[Bug c++/103524] [meta-bug] modules issue

2023-08-05 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524 Bug 103524 depends on bug 102098, which changed state. Bug 102098 Summary: ICE when #include with -fmodules-ts -std=c++20 since r11-7530-g1e5cdb9f896fb220 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102098 What|Removed

[Bug c++/102098] ICE when #include with -fmodules-ts -std=c++20 since r11-7530-g1e5cdb9f896fb220

2023-08-05 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102098 Devourer Station changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/116638] New: False-positive maybe-uninitizlied warning: ‘*(const std::array*)((char*)& +12)’ may be used uninitialized [-Werror=maybe-uninitialized]

2024-09-06 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116638 Bug ID: 116638 Summary: False-positive maybe-uninitizlied warning: ‘*(const std::array*)((char*)& +12)’ may be used uninitialized [-Werror=maybe-uninitialized] Product: gcc

[Bug c++/116638] False-positive maybe-uninitizlied warning: ‘*(const std::array*)((char*)& +12)’ may be used uninitialized [-Werror=maybe-uninitialized]

2024-09-06 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116638 --- Comment #1 from accelerator0099 at gmail dot com --- If you uncomment that /* inline */, the compiler gives no error Removing the -O2 flag also outputs no error

[Bug c++/107288] coroutines: Double-free of temporaries created in statement following co_await

2024-05-05 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107288 accelerator0099 at gmail dot com changed: What|Removed |Added CC||accelerator0099 at gma

[Bug c++/104384] coroutines: Heap corruption when initializing struct with co_await

2024-05-05 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104384 accelerator0099 at gmail dot com changed: What|Removed |Added CC||accelerator0099 at gma

[Bug c++/103909] coroutines: co_yield of aggregate-initialized temporaries leads to segmentation faults.

2024-05-05 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103909 accelerator0099 at gmail dot com changed: What|Removed |Added CC||accelerator0099 at gma

[Bug c++/109283] Destructor of co_yield conditional argument called twice

2024-05-20 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109283 accelerator0099 at gmail dot com changed: What|Removed |Added CC||accelerator0099 at gma

[Bug c++/109283] Destructor of co_yield conditional argument called twice

2024-05-25 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109283 --- Comment #6 from accelerator0099 at gmail dot com --- Still ICEs in truck commit 28b508233a12c13295f960a2cb8a4864879acfb4 May 25 2024 version 15.0.0 Output: co_yield_bug.cc:197:31: error: redefinition of default argument for ‘class _Alloc’

[Bug c++/113142] New: ICE in reference_binding, at cp/call.cc:2020

2023-12-25 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113142 Bug ID: 113142 Summary: ICE in reference_binding, at cp/call.cc:2020 Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c

[Bug c++/113560] New: Strange code generated when optimizing a multiplication on x86_64

2024-01-23 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113560 Bug ID: 113560 Summary: Strange code generated when optimizing a multiplication on x86_64 Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal

[Bug target/113560] Strange code generated when optimizing a multiplication on x86_64

2024-01-24 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113560 --- Comment #4 from accelerator0099 at gmail dot com --- Well, I hope gcc will just generate mulx instruction on arch with BMI2. Let's look at the AMD64 Architecture Programmer’s Manual Volume 3: Computes the unsigned product of the specified sou

[Bug target/113560] Strange code generated when optimizing a multiplication on x86_64

2024-01-24 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113560 --- Comment #5 from accelerator0099 at gmail dot com --- If we are using an arch without BMI2, we can use single MUL instruction instead. Here is the description of MUL reg64/mem64. Multiplies a 64-bit register or memory operand by the contents o

[Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues

2024-11-18 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 Bug 24639 depends on bug 116638, which changed state. Bug 116638 Summary: False-positive maybe-uninitizlied warning: ‘*(const std::array*)((char*)& +12)’ may be used uninitialized [-Werror=maybe-uninitialized] https://gcc.gnu.org/bugzilla/show_b

[Bug tree-optimization/116638] False-positive maybe-uninitizlied warning: ‘*(const std::array*)((char*)& +12)’ may be used uninitialized [-Werror=maybe-uninitialized]

2024-11-18 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116638 accelerator0099 at gmail dot com changed: What|Removed |Added Resolution|--- |FIXED Sta

[Bug target/113560] [12/13 regression] Strange code generated when optimizing a multiplication on x86_64

2024-11-18 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113560 accelerator0099 at gmail dot com changed: What|Removed |Added Resolution|--- |FIXED Sta

[Bug c++/117658] New: Different behavior between header file and module:invalid 'static_cast' from type 'const char [20]' to type 'no_cvref_t' {aka 'char [20]'}

2024-11-18 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117658 Bug ID: 117658 Summary: Different behavior between header file and module:invalid 'static_cast' from type 'const char [20]' to type 'no_cvref_t' {aka 'char [20]'} Product:

[Bug c++/117658] Different ADL behavior between gcc and clang

2024-11-23 Thread accelerator0099 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117658 --- Comment #1 from accelerator0099 at gmail dot com --- main.cc: import std; import pr; int main() { std::printf("%d\n", pr::alias_printable>); } pr.cc: module; import std; namespace pr { struct alias_t {}; constexpr alias_t alias; t