[Bug c/97100] -Wformat checks all arms of _Generic leading to irrelevant type expectation warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97100 --- Comment #11 from Martin Uecker --- A conforming C compiler has to diagnose all violations of constraints with the same correct type of x in all branches (not the type it would have in another context where a different is taken).

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #1 from prathamesh3492 at gcc dot gnu.org --- Investigating this a bit further, the ICE appears with gfortran-13 because for the testcase, because length of postorder traversal over SLP graph (27) doesn't match number of nodes (28), a

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #2 from prathamesh3492 at gcc dot gnu.org --- Created attachment 57956 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57956&action=edit Input to SLP pass (dse4 dump)

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #3 from Andrew Pinski --- Does -fno-cost-model affect the behavior here?

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #4 from Andrew Pinski --- (In reply to Andrew Pinski from comment #3) > Does -fno-cost-model affect the behavior here? Sorry -fno-vect-cost-model.

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #5 from prathamesh3492 at gcc dot gnu.org --- (In reply to Andrew Pinski from comment #3) > Does -fno-cost-model affect the behavior here? With 43da77a4, it doesn't result in ICE with -fno-vect-cost-model or -fvect-cost-model=unlimit

[Bug c/114723] ICE when checking for type compatibility with structure that contains flexible array member (C23)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114723 Richard Biener changed: What|Removed |Added Keywords||ice-on-valid-code --- Comment #1 from

[Bug c/97100] -Wformat checks all arms of _Generic leading to irrelevant type expectation warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97100 --- Comment #12 from Konstantin Kharlamov --- (In reply to Martin Uecker from comment #11) > A conforming C compiler has to diagnose all violations of constraints with > the same correct type of x in all branches (not the type it would have in >

[Bug c/114727] ICE with c23 with aligned attribute and .-g

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114727 --- Comment #2 from Richard Biener --- Possibly type verification should be triggered from rest_of_type_compilation rather than from (only) gen_type_die_with_usage.

[Bug rtl-optimization/114729] RISC-V SPEC2017 507.cactu excessive spillls with -fschedule-insns

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729 Richard Biener changed: What|Removed |Added Target||riscv --- Comment #6 from Richard Bien

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #6 from prathamesh3492 at gcc dot gnu.org --- Created attachment 57957 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57957&action=edit SLP dump

[Bug c/114730] should enum types be vector types?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114730 --- Comment #2 from Richard Biener --- I think we need to reject all integral types whose operation range doesn't match the corresponding integer mode range. For enums it depends on the language standard, in general I'd say it's not wanted. So

[Bug middle-end/114733] [14] Miscompile with -march=rv64gcv -O3 on riscv

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114733 --- Comment #1 from Robin Dapp --- Confirmed, also shows up here.

[Bug target/114734] [14] RISC-V rv64gcv_zvl256b miscompile with -flto -O3 -mrvv-vector-bits=zvl

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114734 --- Comment #1 from Robin Dapp --- Confirmed.

[Bug target/114734] [14] RISC-V rv64gcv_zvl256b miscompile with -flto -O3 -mrvv-vector-bits=zvl

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114734 Richard Biener changed: What|Removed |Added Keywords||needs-bisection Ever confirmed|0

[Bug tree-optimization/114737] New: Missed optimization : fail to optimize load with select clobber

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114737 Bug ID: 114737 Summary: Missed optimization : fail to optimize load with select clobber Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #7 from Richard Biener --- It's probably latent on trunk. The assert verifies all vertices are backward reachable from the leafs. vertices and leafs are discovered with a DFS from the instances. So the question is what's that miss

[Bug c++/114706] ICE - std::bit_cast in consteval function involving array of union

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114706 --- Comment #4 from Jakub Jelinek --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:79ff53453e88e40c4f2ecf6f7f7409afc41b46fc commit r14-9987-g79ff53453e88e40c4f2ecf6f7f7409afc41b46fc Author: Jakub Jelinek Date:

[Bug c++/114706] ICE - std::bit_cast in consteval function involving array of union

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114706 Jakub Jelinek changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug middle-end/114733] [14] Miscompile with -march=rv64gcv -O3 on riscv

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114733 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[Bug c/97100] -Wformat checks all arms of _Generic leading to irrelevant type expectation warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97100 --- Comment #13 from Martin Uecker --- A C compiler has to diagnose all constraint violations. Alternatively, it could also reject the program with an error.

[Bug fortran/114467] f951: internal compiler error: Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114467 --- Comment #2 from thomas --- Yes, I use associate constructs at multiple places in the code. Unfortunately, I won't easily be able to provide a self-contained reproducer, as the error occurs in the middle of a larger compilation cascade involv

[Bug middle-end/114733] [14] Miscompile with -march=rv64gcv -O3 on riscv

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114733 --- Comment #3 from Richard Biener --- So the issue is that we do switch (induction_type) { case vect_step_op_neg: if (TREE_CODE (init_expr) != INTEGER_CST && TREE_CODE (init_expr) != REAL_CST) { /* C

[Bug target/114639] [riscv] ICE in create_pre_exit, at mode-switching.cc:451

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114639 Andreas Schwab changed: What|Removed |Added Target Milestone|--- |14.0 Resolution|---

[Bug target/114255] [RISC-V] [RVV] unable to find a register to spill

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114255 Andreas Schwab changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug lto/113208] [14 Regression] lto1: error: Alias and target's comdat groups differs since r14-5979-g99d114c15523e0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113208 --- Comment #29 from Jakub Jelinek --- Looking at t1 (i.e. the reduced testcase with constexpr), the difference with -std=c++20 -O1 -fkeep-inline-functions is that in r14-5978 we used to emit _ZN6vectorI12QualityValueEC2ERKS1_ in _ZN6vectorI12Qu

[Bug fortran/114467] f951: internal compiler error: Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114467 --- Comment #3 from thomas --- (In reply to anlauf from comment #1) > Can you attached a self-contained reproducer? > > The traceback looks familiar. Are you by chance using an associate > construct? There has been a fix backported from 14-ma

[Bug other/114738] New: [14 Regression] Default DOCUMENTATION_ROOT_URL vs. release branches

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114738 Bug ID: 114738 Summary: [14 Regression] Default DOCUMENTATION_ROOT_URL vs. release branches Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug other/114738] [14 Regression] Default DOCUMENTATION_ROOT_URL vs. release branches

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114738 Jakub Jelinek changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org Target Mi

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Assignee|unassigned

[Bug target/114732] ge can't be reversed to unlt for bcd compares

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114732 --- Comment #2 from Segher Boessenkool --- The fourth CR bit for BCD insns does not mean "unordered", it means "invalid or overflow". It behaves exactly as unordered though, except that it can signal overflow as well as one of the lt gt eq cond

[Bug libstdc++/57585] New --enable-clocale model using POSIX 2008

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57585 --- Comment #2 from Jonathan Wakely --- Separately, it would be good to provide a libintl-based implementation of std::messages, for targets where that's not part of glibc.

[Bug c/97100] -Wformat checks all arms of _Generic leading to irrelevant type expectation warnings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97100 --- Comment #14 from Alejandro Colomar --- Hi Martin, For the discussion of my -Wincompatible-pointer-types reproducer, please visit . I'll reply to you there, since it's more on-topic, and a

[Bug target/111231] [12/13/14 regression] armhf: Miscompilation with -O2/-fno-exceptions level (-fno-tree-vectorize is working)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #34 from Richard Earnshaw --- To be honest, I'm more concerned that we aren't eliminating a lot of these copies during the gimple optimization phase. The memcpy is really a type punning step (that's strictly ISO C compliant, rather

[Bug lto/113208] [14 Regression] lto1: error: Alias and target's comdat groups differs since r14-5979-g99d114c15523e0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113208 Jakub Jelinek changed: What|Removed |Added CC||jason at gcc dot gnu.org,

[Bug target/111231] [12/13/14 regression] armhf: Miscompilation with -O2/-fno-exceptions level (-fno-tree-vectorize is working)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 --- Comment #35 from rguenther at suse dot de --- On Tue, 16 Apr 2024, rearnsha at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 > > --- Comment #34 from Richard Earnshaw --- > To be honest, I'm more concerned t

[Bug middle-end/114733] [14] Miscompile with -march=rv64gcv -O3 on riscv

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114733 --- Comment #4 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:45a41ace55d0ffb1097e374868242329788ec82a commit r14-9992-g45a41ace55d0ffb1097e374868242329788ec82a Author: Richard Biener Date:

[Bug tree-optimization/114736] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #9 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:f949481a1f7ab973608a4ffcc0e342ab5a74e8e4 commit r14-9993-gf949481a1f7ab973608a4ffcc0e342ab5a74e8e4 Author: Richard Biener Date:

[Bug tree-optimization/114736] [13 Regression] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 Richard Biener changed: What|Removed |Added Target Milestone|--- |13.3 Known to work|

[Bug middle-end/114733] [13 Regression] Miscompile with -march=rv64gcv -O3 on riscv

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114733 Richard Biener changed: What|Removed |Added Priority|P3 |P2 Target Milestone|---

[Bug tree-optimization/114737] Missed optimization : fail to optimize load with select clobber

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114737 Richard Biener changed: What|Removed |Added Last reconfirmed||2024-04-16 Status|UNCONFIR

[Bug other/114738] [14 Regression] Default DOCUMENTATION_ROOT_URL vs. release branches

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114738 Richard Biener changed: What|Removed |Added CC||rguenth at gcc dot gnu.org --- Comment

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #12 from Alejandro Colomar --- Hi Martin, On Tue, Apr 16, 2024 at 05:35:03AM +, uecker at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97100 > > --- Comment #7 from uecker at gcc dot gnu.org --- > > Th

[Bug other/114738] [14 Regression] Default DOCUMENTATION_ROOT_URL vs. release branches

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114738 --- Comment #3 from Richard Biener --- We could also make changing it part of branching.html and have additional directories without minor/patchlevel version, thus https://gcc.gnu.org/onlinedocs/gcc-14/ where we could autogenerate docs in more o

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 uecker at gcc dot gnu.org changed: What|Removed |Added CC||uecker at gcc dot gnu.org --

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #14 from Alejandro Colomar --- Oops, I forgot to paste the version with casts. Here it is. It is too repetitive and error prone. alx@debian:~/tmp/c$ cat g.c #include #include #include #include #define is_same_type(a, b)

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #15 from Alejandro Colomar --- (In reply to uecker from comment #13) > A couple of comments: > > In principle, those warnings are not false positives. The design of _Generic > requires that the non-taken branches are valid in C, so

[Bug fortran/114739] New: [14 Regression] ice in gfc_find_derived_types, at fortran/symbol.cc:2458

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114739 Bug ID: 114739 Summary: [14 Regression] ice in gfc_find_derived_types, at fortran/symbol.cc:2458 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: norma

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #16 from uecker at gcc dot gnu.org --- Your example program is indeed not conforming and violates a constraint because you pass a pointer of type that can not be assigned to the type of the argument. So a diagnostic is required and a

[Bug middle-end/111692] ICE in output_constant at varasm:cc:5267 during RTL "final" pass

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111692 --- Comment #2 from Filip Kastl --- The same ICE happens with gcc gcc.target/x86_64/abi/avx512fp16/m512h/test_passing_structs.c --param=dse-max-object-size=2147483647

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #17 from Alejandro Colomar --- Neither -Wall nor -Wextra (nor -Wincompatible-pointer-types) imply -pedantic. (Ahh, this is the pedwarn reference from Andrew.) Which means the compiler could decide to turn off -Wincompatible-pointer

[Bug libstdc++/41495] libstdc++ --enable-clocale=ieee_1003.1-2001 fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41495 --- Comment #12 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #5) > N.B. messages_base::catalog is required to be a typedef for int, although > there is an open issue which would allow intptr_t to be used instead: > http://op

[Bug gcov-profile/114735] Gcov not working with gcc version 11.4.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114735 --- Comment #2 from Gejoe --- May I know where the fix has gone to , meaning the gcc version which will not have this issue of gcov failure ?

[Bug target/114734] [14] RISC-V rv64gcv_zvl256b miscompile with -flto -O3 -mrvv-vector-bits=zvl

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114734 --- Comment #2 from Richard Biener --- probably -fwhole-program is enough, -flto not needed(?) # vectp_g.248_1401 = PHI ... _1411 = .SELECT_VL (ivtmp_1409, POLY_INT_CST [2, 2]); .. vect__193.250_1403 = .MASK_LEN_LOAD (vectp_g.248_1401, 3

[Bug libgomp/92840] [OpenACC] Disallow 'acc_unmap_data' for everything other than 'acc_map_data'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92840 Thomas Schwinge changed: What|Removed |Added CC||cltang at gcc dot gnu.org --- Comment

[Bug libgomp/92840] [OpenACC] Disallow 'acc_unmap_data' for everything other than 'acc_map_data'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92840 --- Comment #5 from Thomas Schwinge --- As determined during patch review, there's still an unresolved issue: On 2024-04-16T17:12:17+0800, Chung-Lin Tang wrote: > If we continue to use k->refcount itself as the flag holder of map type, I > gue

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 Martin Uecker changed: What|Removed |Added CC||muecker at gwdg dot de --- Comment #18

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #19 from Martin Uecker --- It would still work for other arguments that are used in the active branch, but not arguments you may not use in active branch or other subexpressions not used in the active branch.

[Bug c++/114740] New: i686-linux-gnu-g++ does not interpret floating point literals as double

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114740 Bug ID: 114740 Summary: i686-linux-gnu-g++ does not interpret floating point literals as double Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: norm

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #20 from Alejandro Colomar --- H, I like the _Generic() to assert the type. Thanks! With that, I find it more acceptable. At least I don't need to use GNU extensions, and the cast is coupled with the verification of the type.

[Bug c/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #21 from Alejandro Colomar --- It would be interesting to learn why MSVC gets it right. Maybe there's a deterministic way to avoid this warning. Although maybe it's just that they're doing heuristics.

[Bug target/114741] New: [14 regression] aarch64 sve: unnecessary fmov for scalar int bit operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114741 Bug ID: 114741 Summary: [14 regression] aarch64 sve: unnecessary fmov for scalar int bit operations Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: no

[Bug c++/114740] i686-linux-gnu-g++ does not interpret floating point literals as double

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114740 --- Comment #1 from Jonathan Wakely --- See the first item at https://gcc.gnu.org/gcc-13/changes.html#cxx

[Bug gcov-profile/114735] Gcov not working with gcc version 11.4.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114735 --- Comment #3 from Andrew Pinski --- The "fix" was to how to build to be able to use gcov. Basically you build to an object file first and then link the object file to get the old behavior and the behavior that gcov expects.

[Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875 Andrew Pinski changed: What|Removed |Added CC||sjh at schilling dot dk --- Comment #12

[Bug c++/114050] Inconsistency in double/float constant evaluation between 32 and 64 bit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114050 Andrew Pinski changed: What|Removed |Added Resolution|INVALID |DUPLICATE --- Comment #11 from Andrew P

[Bug c++/114740] i686-linux-gnu-g++ does not interpret floating point literals as double

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

[Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875 Andrew Pinski changed: What|Removed |Added CC||gnu.ojxq8 at dralias dot com --- Comment

[Bug target/114741] [14 regression] aarch64 sve: unnecessary fmov for scalar int bit operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114741 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization Target Milestone|

[Bug target/114734] [14] RISC-V rv64gcv_zvl256b miscompile with -flto -O3 -mrvv-vector-bits=zvl

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114734 --- Comment #3 from Robin Dapp --- > probably -fwhole-program is enough, -flto not needed(?) Yes, -fwhole-program is sufficient. > > # vectp_g.248_1401 = PHI > ... > _1411 = .SELECT_VL (ivtmp_1409, POLY_INT_CST [2, 2]); > .. > vect__19

[Bug libstdc++/57585] New --enable-clocale model using POSIX 2008

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57585 --- Comment #3 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #2) > Separately, it would be good to provide a libintl-based implementation of > std::messages, for targets where that's not part of glibc. Although the POSIX cat

[Bug tree-optimization/114736] [13 Regression] ICE during SLP pass with gfortran-13 -O3 -mcpu=neoverse-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114736 --- Comment #11 from prathamesh3492 at gcc dot gnu.org --- Hi Richard, Thanks for the quick fix! I verified it now compiles the test-case with -O3 -mcpu=neoverse-v2. I suppose this will need backporting to gcc-13 branch. The test compiles OK with

[Bug target/114734] [14] RISC-V rv64gcv_zvl256b miscompile with -flto -O3 -mrvv-vector-bits=zvl

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114734 --- Comment #4 from Robin Dapp --- Ok, it looks like we do 5 iterations with the last one being length-masked to length 2 and then in the "live extraction" phase use "iteration 6".

[Bug libstdc++/114742] New: invalid use of '__ieee128' in and

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114742 Bug ID: 114742 Summary: invalid use of '__ieee128' in and Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Com

[Bug libstdc++/114742] invalid use of '__ieee128' in and

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114742 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/114742] invalid use of '__ieee128' in and

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114742 --- Comment #2 from Jonathan Wakely --- Mathias noted that still fails with -mcpu=power7 Checking for _ARCH_PWR8 or __POWER8_VECTOR__ instead works.

[Bug sanitizer/114743] New: ICE in build_check_stmt at asan.cc:2707 while compiling gcc.dg/ubsan/pr112709-2.c with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114743 Bug ID: 114743 Summary: ICE in build_check_stmt at asan.cc:2707 while compiling gcc.dg/ubsan/pr112709-2.c with -fsanitize=address Product: gcc Version: 14.0

[Bug sanitizer/114743] ICE in build_check_stmt at asan.cc:2707 while compiling gcc.dg/ubsan/pr112709-2.c with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114743 Filip Kastl changed: What|Removed |Added Target Milestone|--- |14.0

[Bug target/114732] ge can't be reversed to unlt for bcd compares

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114732 --- Comment #3 from Segher Boessenkool --- 1001, 0101, 0011 I mean of course. In some ways CCmode models this better than CCFPmode, but we do not actually model the SO bit (bit 3) at all in CCmode. It is a nice feature of CCmode (that we actua

[Bug rtl-optimization/114729] RISC-V SPEC2017 507.cactu excessive spillls with -fschedule-insns

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729 --- Comment #7 from Jeffrey A. Law --- Yes, there are different algorithms. I looked at them a while back when we first noticed the problems with spilling and x264. There was very little difference for specint when we varied the algorithms. I

[Bug testsuite/114744] New: test case gcc.target/powerpc/builtins-6-p9-runnable.c fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114744 Bug ID: 114744 Summary: test case gcc.target/powerpc/builtins-6-p9-runnable.c fails Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal P

[Bug rtl-optimization/114729] RISC-V SPEC2017 507.cactu excessive spillls with -fschedule-insns

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729 --- Comment #8 from Jeffrey A. Law --- I didn't even notice you had that testcase attached! I haven't done a deep dive, but the first thing that jumps out is the number of instructions in the ready queue, most likely because of the addressing o

[Bug testsuite/99731] g++.dg/modules/alias-1_a.H: error: failed to read compiled module: No such file or directory

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99731 vvinayag at arm dot com changed: What|Removed |Added CC||vvinayag at arm dot com --- Com

[Bug testsuite/114744] test case gcc.target/powerpc/builtins-6-p9-runnable.c fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114744 --- Comment #1 from seurer at gcc dot gnu.org --- also gcc 11

[Bug c++/114050] Inconsistency in double/float constant evaluation between 32 and 64 bit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114050 Vincent Lefèvre changed: What|Removed |Added CC||vincent-gcc at vinc17 dot net --- Com

[Bug modula2/114745] New: const cast causes ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114745 Bug ID: 114745 Summary: const cast causes ICE Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee

[Bug c++/114740] i686-linux-gnu-g++ does not interpret floating point literals as double

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114740 Vincent Lefèvre changed: What|Removed |Added CC||vincent-gcc at vinc17 dot net --- Com

[Bug c++/114740] i686-linux-gnu-g++ does not interpret floating point literals as double

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114740 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #4

[Bug modula2/114745] const cast causes ICE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114745 Gaius Mulley changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[Bug target/114255] [RISC-V] [RVV] unable to find a register to spill

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114255 Andreas Schwab changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #2 from Andreas

[Bug target/113790] [14 Regression][riscv64] ICE in curr_insn_transform, at lra-constraints.cc:4294 since r14-4944-gf55cdce3f8dd85

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113790 Andreas Schwab changed: What|Removed |Added CC||sch...@linux-m68k.org --- Comment #4 f

[Bug fortran/114739] [14 Regression] ice in gfc_find_derived_types, at fortran/symbol.cc:2458

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114739 kargls at comcast dot net changed: What|Removed |Added CC||kargls at comcast dot net --

[Bug target/114741] [14 regression] aarch64 sve: unnecessary fmov for scalar int bit operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114741 Wilco changed: What|Removed |Added CC||wilco at gcc dot gnu.org --- Comment #1 from Wi

[Bug c++/114050] Inconsistency in double/float constant evaluation between 32 and 64 bit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114050 --- Comment #13 from Jonathan Wakely --- -fexcess-precision does affect constants. With -fexcess-precision=standard, assignments and casts discard excess precision which may otherwise be present in arithmetic expressions and constants. With -fe

[Bug fortran/114739] [14 Regression] ice in gfc_find_derived_types, at fortran/symbol.cc:2458

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114739 --- Comment #2 from David Binderman --- Created attachment 57959 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57959&action=edit F90 source code

[Bug lto/113208] [14 Regression] lto1: error: Alias and target's comdat groups differs since r14-5979-g99d114c15523e0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113208 --- Comment #31 from Jakub Jelinek --- Created attachment 57960 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57960&action=edit gcc14-pr113208.patch Here is my attempt to optimize it in the C++ FE. The ICE is gone and for pr113208_0.C co

[Bug c/92880] Documentation for Built-in Vector-Extensions should mention C99 Fixed-width ints as base types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92880 --- Comment #6 from GCC Commits --- The trunk branch has been updated by Andrew Pinski : https://gcc.gnu.org/g:8eddd87da2dd01c841f9742f973f65ebe0a88e71 commit r14-9994-g8eddd87da2dd01c841f9742f973f65ebe0a88e71 Author: Andrew Pinski Date: Mon

[Bug libstdc++/57585] New --enable-clocale model using POSIX 2008

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57585 --- Comment #4 from Jonathan Wakely --- Created attachment 57961 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57961&action=edit Add --enable-clocale=ieee_1003.1-2008 This is an initial prototype of a new clocale model. The wide string i

[Bug c/92880] Documentation for Built-in Vector-Extensions should mention C99 Fixed-width ints as base types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92880 Andrew Pinski changed: What|Removed |Added Status|ASSIGNED|RESOLVED Target Milestone|---

[Bug sanitizer/114743] ICE in build_check_stmt at asan.cc:2707 while compiling gcc.dg/ubsan/pr112709-2.c with -fsanitize=address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114743 Jakub Jelinek changed: What|Removed |Added Ever confirmed|0 |1 Assignee|unassigned at gcc

  1   2   >