Re: Strange compile error when g++ work with std=c++20.

On Mon, Nov 27, 2023 at 8:24 PM Lew Robin via Gcc-bugs wrote: > > This error happens when using macro and template. > GCC Version: gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~22.04) > OS: ubuntu 22.04 (x64) > Compile Command: > g++-12 ./testmacro.cc --std=c++20 > > In fact, this error exisits from

[Bug debug/112656] btf: function prototypes generated with name

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112656 Jose E. Marchesi changed: What|Removed |Added CC||david.faust at oracle dot com --- Co

[Bug tree-optimization/52252] An opportunity for x86 gcc vectorizer (gain up to 3 times)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52252 Andrew Pinski changed: What|Removed |Added CC||pinskia at gcc dot gnu.org --- Comment #

[Bug middle-end/112710] [13/14 Regression] ICE: in write_type, at cp/mangle.cc:2226 with -fdump-go-spec=filename -flto -fno-use-linker-plugin

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112710 --- Comment #3 from Zdenek Sojka --- (In reply to Ian Lance Taylor from comment #2) > Also -fdump-go-spec isn't useful for C++ code. > > Why does this come up? What are you trying to do? I am trying nothing else than to crash the compiler. Pl

[Bug target/112740] New: [14 Regression] wrong code with vector compare on riscv64 at -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112740 Bug ID: 112740 Summary: [14 Regression] wrong code with vector compare on riscv64 at -O0 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: wrong-code

[Bug target/112713] RISC-V: Trunk GCC regression on VSETVL PASS comparing with GCC-13

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112713 JuzheZhong changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/112722] RISC-V: ICE on tree-vect-slp.cc:8029 for -march=rv64gc_zve64d

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112722 JuzheZhong changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug preprocessor/112701] wrong type inference for ternary operator with `0/0u` in preprocessing context

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112701 Sam James changed: What|Removed |Added Target Milestone|--- |14.0

[Bug target/112740] [14 Regression] wrong code with vector compare on riscv64 at -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112740 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |14.0 --- Comment #1 from Andrew Pinski

[Bug middle-end/32667] block copy with exact overlap is expanded as memcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667 --- Comment #51 from post+gcc at ralfj dot de --- Oh great, I love it when one part of the C standard just adds exceptions to statements made elsewhere. It's almost as if the authors want this to be as hard to understand as possible... That then

[Bug middle-end/32667] block copy with exact overlap is expanded as memcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667 --- Comment #52 from post+gcc at ralfj dot de --- For the point discussed earlier with the `restrict` in the musl memcpy, I had another look at the definition of `restrict` and it's not entirely clear to me any more that there is UB here. The rest

[Bug sanitizer/112741] New: ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3261

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112741 Bug ID: 112741 Summary: ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3261 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug tree-optimization/112742] New: missed vectorization with src[a*b+i] where a*b is not int rather than same percission as size_type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112742 Bug ID: 112742 Summary: missed vectorization with src[a*b+i] where a*b is not int rather than same percission as size_type Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug sanitizer/112741] ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3261

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112741 Sam James changed: What|Removed |Added CC||sjames at gcc dot gnu.org --- Comment #1 fr

<    1   2   3