[Bug tree-optimization/110388] wrong code with on x86_64-linux-gnu

2023-06-24 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110388 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #1 fr

[Bug c/92220] -Wconversion generates a false warning for modulo expression when the modulus has smaller type

2023-06-24 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92220 --- Comment #5 from Xi Ruoyao --- Unfortunately the value range info is not available in the frontend :(.

[Bug c/92220] -Wconversion generates a false warning for modulo expression when the modulus has smaller type

2023-06-24 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92220 --- Comment #6 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #5) > Unfortunately the value range info is not available in the frontend :(. Here "value range info" means the info from the VRP pass. For this case we can specially check M

[Bug c++/110394] Lambda capture receives wrong value

2023-06-24 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110394 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #4 fr

[Bug c++/110401] New: Unhelpful "goto is not a constant expression" in ill-formed constexpr function template

2023-06-25 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110401 Bug ID: 110401 Summary: Unhelpful "goto is not a constant expression" in ill-formed constexpr function template Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-26 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #14 from Xi Ruoyao --- Any clue about how to fix this?

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-27 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #15 from Xi Ruoyao --- attachment 54666 from PR109093 seems able to fix this. Could we make it into trunk and the release branches?

[Bug c++/110437] SIGILL when return missing in a C++ function with a condition

2023-06-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110437 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #11 f

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #17 from Xi Ruoyao --- (In reply to H.J. Lu from comment #16) > Created attachment 55409 [details] > A patch > > I am stilling trying to find a small testcase. The patch triggers an ICE building Spidermonkey 115b9 (it segfaults wit

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #18 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #17) > (In reply to H.J. Lu from comment #16) > > Created attachment 55409 [details] > > A patch > > > > I am stilling trying to find a small testcase. > > The patch trigge

[Bug c/110453] gcc accepts redefinition of global variable without initializer

2023-06-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110453 Xi Ruoyao changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #20 from Xi Ruoyao --- (In reply to H.J. Lu from comment #19) > (In reply to Xi Ruoyao from comment #17) > > (In reply to H.J. Lu from comment #16) > > > Created attachment 55409 [details] > > > A patch > > > > > > I am stilling try

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #21 from Xi Ruoyao --- Created attachment 55421 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55421&action=edit test case broken by draft patch (at -O2 -mavx2 -mtune=haswell)

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #22 from Xi Ruoyao --- (In reply to H.J. Lu from comment #19) > Do you have a testcase? Attached.

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-29 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #24 from Xi Ruoyao --- (In reply to H.J. Lu from comment #23) > Created attachment 55424 [details] > An updated patch Unfortunately Spidermonkey 115 still crashes even with the patch (and -O3 -march=tigerlike -mtune=tigerlake -fno-e

[Bug target/109780] [12/13/14 Regression] csmith: runtime crash with -O2 -march=znver1

2023-06-29 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780 --- Comment #25 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #24) > (In reply to H.J. Lu from comment #23) > > Created attachment 55424 [details] > > An updated patch > > Unfortunately Spidermonkey 115 still crashes even with the patc

[Bug target/110457] Unnecessary movsx eax, dil

2023-06-29 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110457 Xi Ruoyao changed: What|Removed |Added Ever confirmed|0 |1 CC|

[Bug c++/110484] Spec2017 541 after adding the '-flto-fomit-frame-pointer' optimization, after optimizing the rnreg, directly replaced other registers with the $r22 register, so that the value of the

2023-06-29 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110484 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #2 fr

[Bug middle-end/110282] Segmentation fault with specific optimizations

2023-06-30 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110282 --- Comment #7 from Xi Ruoyao --- (In reply to CTC from comment #6) > Another related and smaller reproducer: > > # cat tmp.i > main() { > int *a = 0; > int b = *a; > } No, this is an undefined behavior and the compiler is allowed to gener

[Bug middle-end/110294] [10/11 Regression] Segmentation fault with '-O3 -fno-dce -fno-toplevel-reorder -fno-tree-dce -fno-tree-pta -fno-tree-sink -ftoplevel-reorder'

2023-06-30 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110294 --- Comment #4 from Xi Ruoyao --- (In reply to CTC from comment #3) > Another related and smaller reproducer: > > # cat tmp.i > a; > *const b; > main() { a != *b; } This is an undefined behavior and the compiler is allowed to generate code to

[Bug target/110557] New: Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields

2023-07-05 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110557 Bug ID: 110557 Summary: Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug target/110557] [13/14 Regression] Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields

2023-07-05 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110557 Xi Ruoyao changed: What|Removed |Added Target||x86_64-linux-gnu Target Milestone|---

[Bug tree-optimization/110557] [13/14 Regression] Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields

2023-07-06 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110557 --- Comment #3 from Xi Ruoyao --- It looks like if !UNSIGNED_TYPE (TREE_TYPE (bf_ref)), we need to generate something like: masked = (the signed variant of the wider type in {type_out, type_container}) container << (bitpos + bitsize); result =

[Bug tree-optimization/110557] [13/14 Regression] Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields

2023-07-06 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110557 --- Comment #4 from Xi Ruoyao --- Untested patch: diff --git a/gcc/tree-vect-patterns.cc b/gcc/tree-vect-patterns.cc index de20e9d59cb..01df568ee61 100644 --- a/gcc/tree-vect-patterns.cc +++ b/gcc/tree-vect-patterns.cc @@ -2566,7 +2566,7 @@ vec

[Bug tree-optimization/110557] [13/14 Regression] Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields

2023-07-06 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110557 Xi Ruoyao changed: What|Removed |Added URL||https://gcc.gnu.org/piperma

[Bug tree-optimization/110557] [13/14 Regression] Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields

2023-07-06 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110557 --- Comment #6 from Xi Ruoyao --- (In reply to avieira from comment #5) > Hi Xi, > > Feel free to test your patch and submit it to the list for review. I had a > look over and it looks correct to me. https://gcc.gnu.org/pipermail/gcc-patches/2

[Bug plugins/110610] File insn-opinit.h not installed ?

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110610 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #1 fr

[Bug plugins/110610] File insn-opinit.h not installed ?

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110610 --- Comment #4 from Xi Ruoyao --- (In reply to avieira from comment #2) > I can't reproduce this but it seems like the modula2 build also suffers from > the same issue, see PR110284. > > David, what exactly are you trying to build? Can you give

[Bug plugins/110610] File insn-opinit.h not installed ?

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110610 --- Comment #6 from Xi Ruoyao --- (In reply to avieira from comment #5) > intenral-fn.h is generated at gcc build-time. I guess you mean insn-opinit.h, not internal-fn.h. internal-fn.h is in the GCC Git repo. > I'm not sure we want to > 'inst

[Bug tree-optimization/110557] [13/14 Regression] Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110557 Xi Ruoyao changed: What|Removed |Added Target Milestone|13.3|13.2 Status|ASSIGNED

[Bug other/110205] Some new warnings from clang for the range code

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110205 Xi Ruoyao changed: What|Removed |Added Component|c |other CC|

[Bug middle-end/110617] New: RFE: Add a diagnostic-only variant of nonnull attribute

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617 Bug ID: 110617 Summary: RFE: Add a diagnostic-only variant of nonnull attribute Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: enhancement

[Bug middle-end/110617] RFE: Add a diagnostic-only variant of nonnull attribute

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617 --- Comment #1 from Xi Ruoyao --- [1]: https://sourceware.org/glibc/wiki/Style_and_Conventions#Bugs_in_the_user_program [2]: https://sourceware.org/pipermail/libc-alpha/2023-July/149893.html

[Bug rtl-optimization/104843] signed overflow in compute_const_anchors, at cse.cc:1180

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104843 Xi Ruoyao changed: What|Removed |Added Target Milestone|--- |13.0 Status|UNCONFIRMED

[Bug other/63426] [meta-bug] Issues found with -fsanitize=undefined

2023-07-10 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426 Bug 63426 depends on bug 104843, which changed state. Bug 104843 Summary: signed overflow in compute_const_anchors, at cse.cc:1180 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104843 What|Removed |Added

[Bug tree-optimization/110557] [13/14 Regression] Wrong code for x86_64-linux-gnu with -O3 -mavx2: vectorized loop mishandles signed bit-fields

2023-07-11 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110557 --- Comment #10 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #9) > Fixed for 14 and 13.2. There is a test suite issue in the committed patch, fixed at r14-2427 and r13-7555.

[Bug middle-end/110617] RFE: Add a diagnostic-only variant of nonnull attribute

2023-07-11 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617 --- Comment #6 from Xi Ruoyao --- (In reply to Richard Biener from comment #5) > I think a -f... option to disable the code generation effects would make > more sense than adding another attribute kind. Then maybe we'd just add a -D_GLIBC_NONNU

[Bug middle-end/110617] RFE: Add a diagnostic-only variant of nonnull attribute

2023-07-11 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617 --- Comment #10 from Xi Ruoyao --- (In reply to Florian Weimer from comment #9) > (In reply to Xi Ruoyao from comment #6) > > (In reply to Richard Biener from comment #5) > > > I think a -f... option to disable the code generation effects would

[Bug middle-end/110617] RFE: Add a diagnostic-only variant of nonnull attribute

2023-07-11 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110617 --- Comment #12 from Xi Ruoyao --- (In reply to Florian Weimer from comment #11) > (In reply to Xi Ruoyao from comment #10) > > But Zack's reason against using __nonnull is __nonnull may cause unwanted > > optimizations to *the user code*. > >

[Bug rtl-optimization/107013] Add fmin/fmax to RTL codes

2023-07-11 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107013 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #2 fr

[Bug libgcc/109670] [13/14 regression] Exception handling broken for 32-bit Windows

2023-07-12 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109670 Xi Ruoyao changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/110675] Using std::set with avx2 pragma is broken on latest gcc version (compilation fails)

2023-07-15 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110675 --- Comment #2 from Xi Ruoyao --- Clearly related to PR109753, but I'm not sure if it's OK to just mark it as a dup.

[Bug target/110675] Using std::set with avx2 pragma is broken on latest gcc version (compilation fails)

2023-07-15 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110675 Xi Ruoyao changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED

[Bug c++/109753] [13/14 Regression] pragma GCC target causes std::vector not to compile (always_inline on constructor)

2023-07-15 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109753 Xi Ruoyao changed: What|Removed |Added CC||gcc.gnu.org at aryanc403 dot com --- Comme

[Bug c++/109753] [13/14 Regression] pragma GCC target causes std::vector not to compile (always_inline on constructor)

2023-07-15 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109753 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #8 fr

[Bug rtl-optimization/110701] [14 Regression] Wrong code at -O1/2/3/s on x86_64-linux-gnu

2023-07-17 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110701 Xi Ruoyao changed: What|Removed |Added Component|c |rtl-optimization --- Comment #1 from Xi Ruo

[Bug target/110709] how to handle the initialization of global struct data for position independent executable application.

2023-07-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110709 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org Statu

[Bug bootstrap/110716] failed to build cross gcc 10.5 with host gcc 4.6.3

2023-07-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110716 --- Comment #1 from Xi Ruoyao --- GCC 10 branch has been closed so this is unlikely to be fixed.

[Bug bootstrap/110716] failed to build cross gcc 10.5 with host gcc 4.6.3

2023-07-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110716 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #3 fr

[Bug target/110709] how to handle the initialization of global struct data for position independent executable application.

2023-07-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110709 --- Comment #7 from Xi Ruoyao --- (In reply to wangwen from comment #6) > would anyone guide me any place to ask such question? You are building the .o files with -fpie, but have you linked the executable with -pie? Note that -fpie and -pie ar

[Bug bootstrap/110716] failed to build cross gcc 10.5 with host gcc 4.6.3

2023-07-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110716 --- Comment #5 from Xi Ruoyao --- Should we change invoke.texi? diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index e099cd0b568..dd4f74fbd78 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -231,7 +231,7 @@ Necessary t

[Bug c/110738] GCC trunk failed to do some optimizations since GCC-8

2023-07-19 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110738 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #4 fr

[Bug target/112970] New: LoongArch: Suboptimal code when the address and the value of an array element are both used

2023-12-11 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112970 Bug ID: 112970 Summary: LoongArch: Suboptimal code when the address and the value of an array element are both used Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug target/112970] LoongArch: Suboptimal code when the address and the value of an array element are both used

2023-12-11 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112970 --- Comment #1 from Xi Ruoyao --- With -mexplicit-relocs=auto the generated code is sub-optimal as well: pcalau12i $r12,%pc_hi20(.LANCHOR0) addi.d $r12,$r12,%pc_lo12(.LANCHOR0) ld.wu $r5,$r12,4 addi.d $

[Bug target/112970] LoongArch: Suboptimal code when the address and the value of an array element are both used

2023-12-11 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112970 --- Comment #2 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #1) > With -mexplicit-relocs=auto the generated code is sub-optimal as well: I mean "always", not "auto". > pcalau12i $r12,%pc_hi20(.LANCHOR0) > addi.d $r

[Bug middle-end/112985] New: LOGICAL_OP_NON_SHORT_CIRCUIT unconditionally execute comparison even if it's very expensive

2023-12-12 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112985 Bug ID: 112985 Summary: LOGICAL_OP_NON_SHORT_CIRCUIT unconditionally execute comparison even if it's very expensive Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug preprocessor/112978] Five minute long error message when OpenMP pragma is erroneously placed in macro

2023-12-12 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112978 Xi Ruoyao changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug target/112998] s390x: Incorrect code generation

2023-12-14 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112998 Xi Ruoyao changed: What|Removed |Added Resolution|--- |DUPLICATE CC|

[Bug target/112986] s390x gcc O2, O3: Incorrect logic operation in < comparison with the same values

2023-12-14 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986 --- Comment #8 from Xi Ruoyao --- *** Bug 112998 has been marked as a duplicate of this bug. ***

[Bug target/112329] Faulty arithmetic comparison in O2, O3 of s390x-gcc with -march=z13

2023-12-14 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112329 Xi Ruoyao changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/112986] s390x gcc O2, O3: Incorrect logic operation in < comparison with the same values

2023-12-14 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986 --- Comment #9 from Xi Ruoyao --- *** Bug 112329 has been marked as a duplicate of this bug. ***

[Bug target/112112] Improper Arithmetic Type Conversion in s390x-linux-gnu-gcc

2023-12-14 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112112 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org Statu

[Bug target/112986] s390x gcc O2, O3: Incorrect logic operation in < comparison with the same values

2023-12-14 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986 --- Comment #10 from Xi Ruoyao --- *** Bug 112112 has been marked as a duplicate of this bug. ***

[Bug target/113034] Miscompilation of __m128 ne comparison on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113034 Xi Ruoyao changed: What|Removed |Added CC||chenglulu at loongson dot cn,

[Bug target/113034] Miscompilation of __m128 ne comparison on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113034 --- Comment #3 from Xi Ruoyao --- (define_code_iterator vfcond [unordered ordered eq ne le lt uneq unle unlt]) (define_code_attr fcc [(unordered "cun") (ordered "cor") (eq"ceq") (ne"cne") (uneq "cueq") (u

[Bug target/113034] Miscompilation of __m128 ne comparison on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113034 Xi Ruoyao changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at g

[Bug target/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 Xi Ruoyao changed: What|Removed |Added CC||chenglulu at loongson dot cn,

[Bug target/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 --- Comment #2 from Xi Ruoyao --- It looks like we are missing a force_reg () somewhere.

[Bug target/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 --- Comment #3 from Xi Ruoyao --- (define_expand "vec_init" [(match_operand:LSX 0 "register_operand") (match_operand:LSX 1 "")] "ISA_HAS_LSX" { loongarch_expand_vector_init (operands[0], operands[1]); DONE; }) We need to add a predi

[Bug target/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 --- Comment #4 from Xi Ruoyao --- Strange... Most backends do not have predicate for op2 of vec_init but how do they evade this issue?

[Bug middle-end/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 Xi Ruoyao changed: What|Removed |Added Component|target |middle-end CC|

[Bug middle-end/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-16 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 Xi Ruoyao changed: What|Removed |Added Keywords||missed-optimization --- Comment #6 from Xi

[Bug target/112936] LoongArch: Wrong instruction costs

2023-12-17 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112936 Xi Ruoyao changed: What|Removed |Added Target Milestone|--- |14.0 Status|ASSIGNED

[Bug target/113034] Miscompilation of __m128 ne comparison on LoongArch

2023-12-17 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113034 Xi Ruoyao changed: What|Removed |Added Keywords||patch URL|

[Bug middle-end/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 Xi Ruoyao changed: What|Removed |Added URL||https://gcc.gnu.org/piperma

[Bug target/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 Xi Ruoyao changed: What|Removed |Added Component|middle-end |target --- Comment #8 from Xi Ruoyao --- (

[Bug target/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 --- Comment #9 from Xi Ruoyao --- diff --git a/gcc/config/loongarch/loongarch.cc b/gcc/config/loongarch/loongarch.cc index 256fa7d048d..65a2915329e 100644 --- a/gcc/config/loongarch/loongarch.cc +++ b/gcc/config/loongarch/loongarch.cc @@ -10770,

[Bug c++/113025] Pointer is sometimes assumed to be 16-byte aligned even when there is no such guarantee

2023-12-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113025 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #3 fr

[Bug c++/113025] Pointer is sometimes assumed to be 16-byte aligned even when there is no such guarantee

2023-12-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113025 --- Comment #4 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #3) > (In reply to juki from comment #2) > > Unfortunately alignment of the cast type was not causing this issue. > > > > I changed all calls that were defined in GCC headers

[Bug c++/113025] Pointer is sometimes assumed to be 16-byte aligned even when there is no such guarantee

2023-12-18 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113025 --- Comment #6 from Xi Ruoyao --- Works for me: #include #include #define LOAD_SI128(ptr) \ ( ((uintptr_t)(ptr) & 15) == 0 ) ? _mm_load_si128((__m128i*)(ptr)) : _mm_loadu_si128((__m128i*)(ptr)) extern char x[16]; __m128i y; void te

[Bug target/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-20 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 Xi Ruoyao changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/113034] Miscompilation of __m128 ne comparison on LoongArch

2023-12-20 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113034 Xi Ruoyao changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug target/113148] 14.0 ICE: maximum number of generated reload insns per insn achieved

2023-12-26 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113148 Xi Ruoyao changed: What|Removed |Added Last reconfirmed||2023-12-26 Ever confirmed|0

[Bug target/113148] 14.0 ICE: maximum number of generated reload insns per insn achieved

2023-12-26 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113148 --- Comment #2 from Xi Ruoyao --- A bug in loongarch_secondary_reload is causing an infinite loop: diff --git a/gcc/config/loongarch/loongarch.cc b/gcc/config/loongarch/loongarch.cc index 5ffd06ce9be..c0a0af3dda5 100644 --- a/gcc/config/loongar

[Bug sanitizer/113151] Need for a TBAA / strict aliasing sanitizer (TySan)

2023-12-26 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113151 Xi Ruoyao changed: What|Removed |Added Ever confirmed|0 |1 Severity|normal

[Bug target/113148] 14.0 ICE: maximum number of generated reload insns per insn achieved

2023-12-26 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113148 Xi Ruoyao changed: What|Removed |Added URL||https://gcc.gnu.org/piperma

[Bug target/113148] 14.0 ICE: maximum number of generated reload insns per insn achieved

2023-12-26 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113148 --- Comment #4 from Xi Ruoyao --- (In reply to Xi Ruoyao from comment #3) > Patch: https://gcc.gnu.org/pipermail/gcc-patches/2023-December/641443.html I've successfully built Xwayland with patched GCC.

[Bug target/113148] [14 Regression] ICE: maximum number of generated reload insns per insn achieved

2023-12-26 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113148 Xi Ruoyao changed: What|Removed |Added Priority|P3 |P1 Summary|14.0 ICE: maximum num

[Bug target/113148] [14 Regression] ICE: maximum number of generated reload insns per insn achieved

2023-12-27 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113148 Xi Ruoyao changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/113033] GCC 14 (20231203 snapshot) ICE when building LSX vector rotate code on LoongArch

2023-12-27 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113033 --- Comment #12 from Xi Ruoyao --- Missed-optimization fixed at r14-6851.

[Bug libstdc++/113159] More robust std::sort for silly comparator functions

2023-12-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113159 Xi Ruoyao changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug c++/113124] g++ should relax designated initialiser rules for trivial classes (read: C structures) and C arrays.

2023-12-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113124 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #6 fr

[Bug c++/113124] g++ should relax designated initialiser rules for trivial classes (read: C structures) and C arrays.

2023-12-28 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113124 --- Comment #8 from Xi Ruoyao --- (In reply to Alexey Dobriyan from comment #7) > > fancy C++ extension > > It is not fancy. > > C99 initialisers is the only feature where Modern C beats Modern C++. Fancy or not you should ask the standard co

[Bug other/113177] GCC 8.5.0 build with libstdcxx gets library versions mixed up

2023-12-30 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113177 Xi Ruoyao changed: What|Removed |Added Last reconfirmed||2023-12-30 CC|

[Bug other/113177] GCC 8.5.0 build with libstdcxx gets library versions mixed up

2023-12-30 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113177 Xi Ruoyao changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

2023-12-30 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 Xi Ruoyao changed: What|Removed |Added CC||eyalroz1 at gmx dot com --- Comment #13 from

[Bug bootstrap/87858] Building old multilib bootstrap GCC: stage1 32-bit libstdc++ fails to build after building 64-bit libstdc++

2023-12-30 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87858 Xi Ruoyao changed: What|Removed |Added Status|UNCONFIRMED |NEW CC|

[Bug testsuite/113175] [14 Regression] testsuite/std/ranges/iota/max_size_type.cc 5x times slower

2023-12-31 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113175 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #4 fr

[Bug web/113190] New: Alert not to report bugs against EOL releases

2024-01-01 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113190 Bug ID: 113190 Summary: Alert not to report bugs against EOL releases Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Compo

[Bug tree-optimization/112457] Possible better vectorization of different reduction min/max reduction

2024-01-02 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112457 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #4 fr

<    2   3   4   5   6   7   8   9   10   11   >