[Bug debug/110073] [14 regression] btfout.cc format errors break bootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110073 --- Comment #10 from Iain Sandoe --- this is fixed, at least on Darwin, right? is there some failing case remaining on Solaris or can we close this?

[Bug c++/110477] -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 --- Comment #1 from Peter Dimov --- Looks like a duplicate of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108742 and is fixed by casting the rhs to (float), but any ordinary programmer would be baffled. For context, I encountered this

[Bug d/110480] [14 regression] ICE: tree check: expected none of vector_type, have vector_type in d_signed_or_unsigned_type, at d/types.cc:55)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110480 Rainer Orth changed: What|Removed |Added Target Milestone|--- |14.0

[Bug d/110480] New: [14 regression] ICE: tree check: expected none of vector_type, have vector_type in d_signed_or_unsigned_type, at d/types.cc:55)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110480 Bug ID: 110480 Summary: [14 regression] ICE: tree check: expected none of vector_type, have vector_type in d_signed_or_unsigned_type, at d/types.cc:55) Product: gcc

[Bug c++/110477] -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 --- Comment #5 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #4) > double f = 2.1; > assert( f == 2.1 ); // fails Which is effectively the same as your example from PR 110476.

[Bug tree-optimization/110452] Bad vectorization of invariant masks

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110452 --- Comment #1 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:6d2eddf456f2d6494cac490c4aa3e7d089926098 commit r14-2183-g6d2eddf456f2d6494cac490c4aa3e7d089926098 Author: Richard Biener Date:

[Bug target/110331] ppc64 vec_extract with constant index is suboptimal on P8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110331 --- Comment #1 from HaoChen Gui --- Even the P9 assembly is not good, as vextu* has a higher lantency than mfvsrd. li 9,12 vextubrx 3,9,2

[Bug tree-optimization/110452] Bad vectorization of invariant masks

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110452 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/110460] [14 Regression] ft32 ICE on 931110-1.c with new TYPE_PRECISION checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110460 Rainer Orth changed: What|Removed |Added Target|ft32-elf, moxie-elf |ft32-elf, moxie-elf, sparc,

[Bug rtl-optimization/110391] [12/13/14 Regression] wrong code at -O2 and -O3 with "-fsel-sched-pipelining -fselective-scheduling2" on x86_64-linux-gnu

-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 20230629 (experimental) [master r14-924-gd709841ae0f] (GCC) [544] % [544] % gcctk -O2 -fselective-scheduling2 small.c [545] % timeout -s 9 5 ./a.out Killed [546] % [546] % gcctk -O1 small.c; ./a.out [547] % [547

[Bug target/110473] vec_convert for aarch64 seems to lower to something which should be improved

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110473 Richard Biener changed: What|Removed |Added Last reconfirmed||2023-06-29

[Bug tree-optimization/110460] [14 Regression] ft32 ICE on 931110-1.c with new TYPE_PRECISION checking

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

[Bug tree-optimization/110481] New: Possible improvements in dense switch statement returning values

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110481 Bug ID: 110481 Summary: Possible improvements in dense switch statement returning values Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: enhancement

[Bug tree-optimization/110252] [14 Regression] Wrong code at -O2/3/s on x86_64-linux-gnu

-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 20230629 (experimental) [master r14-924-gd709841ae0f] (GCC) [558] % [558] % gcctk -O2 small.c [559] % ./a.out Aborted [560] % gcctk -O1 small.c; ./a.out [561] % [561] % cat small.c int a, b = 2, c = 2; int

[Bug tree-optimization/110475] New: [14 Regression] Wrong code at -O2/3/s on x86_64-pc-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110475 Bug ID: 110475 Summary: [14 Regression] Wrong code at -O2/3/s on x86_64-pc-linux-gnu Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug testsuite/110419] [14 regression] new test case gfortran.dg/value_9.f90 in r14-2050-gd130ae8499e0c6 fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110419 Mikael Morin changed: What|Removed |Added CC||mikael at gcc dot gnu.org --- Comment

[Bug target/110448] [RISC-V] RVV intrinsic api test error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110448 Kito Cheng changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug tree-optimization/110460] [14 Regression] ft32 ICE on 931110-1.c with new TYPE_PRECISION checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110460 --- Comment #2 from Richard Biener --- So we're trying vectorizing SImode vector<2> short as SImode vector<1> int. Usually the vectorizer fends off existing vector code quite early which doesn't work here for some reason.

[Bug target/108742] Incorrect constant folding with (or exposed by) -fexcess-precision=standard

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

[Bug c++/110477] -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE

[Bug c++/110477] -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 --- Comment #3 from Peter Dimov --- That's true, but the normal expectation of anyone using -fexcess-precision=standard would be for it to apply consistently everywhere (that is, as if FLT_EVAL_METHOD is 0.) Of course given that

[Bug tree-optimization/110461] [14 regression] ICE when building openh264 with new vector_type checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110461 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug debug/110073] [14 regression] btfout.cc format errors break bootstrap

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110073 Rainer Orth changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

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

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

[Bug middle-end/110399] pointer substraction causes coredump with ftrapv on edge case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110399 --- Comment #3 from Chan Lewis --- (In reply to Andrew Pinski from comment #2) > Dup of bug 13421. > > *** This bug has been marked as a duplicate of bug 13421 *** I see. I wonder why gcc consider pointer signed and need to abort in this

[Bug c/110454] [14 Regression] ICE: tree check: expected none of vector_type, have vector_type in convert_argument, at c/c-typeck.cc:3388 with -Wtraditional-conversion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110454 Richard Biener changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org

[Bug middle-end/110459] Trivial on stack variable was not optimized away

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110459 Richard Biener changed: What|Removed |Added Target||x86_64-*-* --- Comment #2 from

[Bug testsuite/110419] [14 regression] new test case gfortran.dg/value_9.f90 in r14-2050-gd130ae8499e0c6 fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110419 --- Comment #2 from Mikael Morin --- (In reply to Mikael Morin from comment #1) > Harald committed an additional fix to the PR: > Unfortunately, the failure on big endian power remains. Is the execution output the same as before?

[Bug tree-optimization/110474] Vect: the epilog vect loop should have small VF if the loop is unrolled during vectorization

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

[Bug tree-optimization/110475] [14 Regression] Wrong code at -O2/3/s on x86_64-pc-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110475 Richard Biener changed: What|Removed |Added Target||x86_64-*-* Target Milestone|---

[Bug d/106977] [13/14 regression] d21 dies with SIGBUS on 32-bit Darwin

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106977 Iain Sandoe changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/110476] constexpr floating point regression with -std=c++XX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110476 --- Comment #1 from Peter Dimov --- As discussed in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108742, this is a consequence of applying the FLT_EVAL_METHOD=2 rules, and can be fixed by casting 3.14f to (float). That's... incredibly

[Bug rtl-optimization/110479] New: Unnecessary register move

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110479 Bug ID: 110479 Summary: Unnecessary register move Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component:

[Bug target/110478] RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 --- Comment #2 from Bin Meng --- I am not sure I understand your comments. Are you saying that this behavior of "zicsr" libgcc path in the multilib configuration is intentional?

[Bug c++/110477] -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 --- Comment #6 from Peter Dimov --- I suppose this is unfixable because there's all sorts of code assuming that the value of (long double)3.14 is 3.14L and not (long double)(double)3.14L. I doubt that anyone sane expects this from (long

[Bug middle-end/110148] [14 Regression] TSVC s242 regression between g:c0df96b3cda5738afbba3a65bb054183c5cd5530 and g:e4c986fde56a6248f8fbe6cf0704e1da34b055d8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110148 --- Comment #5 from CVS Commits --- The master branch has been updated by Lili Cui : https://gcc.gnu.org/g:4633e38cd22c5e51fac984124c7627be912d0999 commit r14-2185-g4633e38cd22c5e51fac984124c7627be912d0999 Author: Lili Cui Date: Thu Jun 29

[Bug c/110482] New: ICE tree check: expected none of vector_type, have vector_type in type_has_mode_precision_p, at tree.h:6644

lla/attachment.cgi?id=55425=edit unreduced testcase gcc version 14.0.0 20230629 (experimental) 6d2eddf456f2d6494cac490c4aa3e7d089926098 i.e. with the fix to PR110454 applied. $ gcc -mno-sse -mno-mmx -mno-sse2 -O2 -c nf_conntrack_expect.i during GIMPLE pass: slp /usr/src/linux.git/net/netfil

[Bug tree-optimization/110475] [14 Regression] Wrong code at -O2/3/s on x86_64-pc-linux-gnu

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

[Bug c/110454] [14 Regression] ICE: tree check: expected none of vector_type, have vector_type in convert_argument, at c/c-typeck.cc:3388 with -Wtraditional-conversion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110454 --- Comment #2 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:d81c7a25365d3cc87e5edad5e68049b149af55b4 commit r14-2181-gd81c7a25365d3cc87e5edad5e68049b149af55b4 Author: Richard Biener Date:

[Bug c/110454] [14 Regression] ICE: tree check: expected none of vector_type, have vector_type in convert_argument, at c/c-typeck.cc:3388 with -Wtraditional-conversion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110454 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/110461] [14 regression] ICE when building openh264 with new vector_type checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110461 --- Comment #13 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:1e6f1659bd7337e91a88086f8092ada01e80ac94 commit r14-2182-g1e6f1659bd7337e91a88086f8092ada01e80ac94 Author: Richard Biener Date:

[Bug target/110478] RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 Kito Cheng changed: What|Removed |Added CC||kito at gcc dot gnu.org --- Comment #3

[Bug c++/110477] -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 Matthias Kretz (Vir) changed: What|Removed |Added CC||mkretz at gcc dot gnu.org ---

[Bug c++/110476] New: constexpr floating point regression with -std=c++XX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110476 Bug ID: 110476 Summary: constexpr floating point regression with -std=c++XX Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/110450] [14 Regression] Dead Code Elimination Regression at -O2 since r14-261-g0ef3756adf0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110450 Richard Biener changed: What|Removed |Added Keywords||missed-optimization Target

[Bug tree-optimization/110461] [14 regression] ICE when building openh264 with new vector_type checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110461 --- Comment #11 from Richard Biener --- (In reply to Andrew Pinski from comment #4) > Yes it is that pattern, specifically : > /* Try to fold (type) X op CST -> (type) (X op ((type-x) CST)) >when profitable. >For bitwise binary

[Bug tree-optimization/110461] [14 regression] ICE when building openh264 with new vector_type checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110461 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug c++/110477] New: -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 Bug ID: 110477 Summary: -fexcess-precision=standard not applied consistently Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/110461] [14 regression] ICE when building openh264 with new vector_type checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110461 --- Comment #12 from David Binderman --- Here is a test case which seems to demonstrate the problem: $ /home/dcb38/gcc/results/bin/gcc -c -w -O1 -march=znver1 bug935.c during GIMPLE pass: fre bug935.c: In function ‘func_63’: bug935.c:5:6:

[Bug driver/110478] New: RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 Bug ID: 110478 Summary: RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity:

[Bug target/110478] RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 Andrew Pinski changed: What|Removed |Added Component|driver |target Target|

[Bug d/110193] d_signed_or_unsigned_type is invoked for vector types

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

[Bug d/110480] [14 regression] ICE: tree check: expected none of vector_type, have vector_type in d_signed_or_unsigned_type, at d/types.cc:55)

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

[Bug c++/110477] -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 --- Comment #4 from Jonathan Wakely --- (In reply to Peter Dimov from comment #1) > Looks like a duplicate of > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108742 and is fixed by casting > the rhs to (float), Yes, with

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

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

[Bug tree-optimization/110485] New: vectorizing simd clone calls without loop masking applied

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110485 Bug ID: 110485 Summary: vectorizing simd clone calls without loop masking applied Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077 --- Comment #9 from Jonathan Wakely --- Thanks for the quick response! For x86 both these conditions are false: #if defined(__STDCPP_FLOAT128_T__) && defined(_GLIBCXX_LDOUBLE_IS_IEEE_BINARY128) ... #elif defined(__STDCPP_FLOAT128_T__) &&

[Bug target/108742] Incorrect constant folding with (or exposed by) -fexcess-precision=standard

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108742 --- Comment #13 from Peter Dimov --- I think that https://eel.is/c++draft/lex.fcon#3 disagrees. "If the scaled value is not in the range of representable values for its type, the program is ill-formed. Otherwise, the value of a

[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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110484 --- Comment #1 from chenglulu --- The following code modification problem can be solved： --- a/gcc/config/loongarch/loongarch.cc +++ b/gcc/config/loongarch/loongarch.cc @@ -1112,7 +1112,9 @@ loongarch_first_stack_step (struct

[Bug c++/110468] [12/13/14 regression] Internal compiler error in nothrow_spec_p

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110468 Patrick Palka changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot gnu.org

[Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077 --- Comment #6 from Jonathan Wakely --- This is going to be hard for me to figure out without access to a Solaris x86 system. Could you please attach the output of this command using GCC trunk on solaris x86? g++ -std=c++23 -include charconv

[Bug tree-optimization/110460] [14 Regression] ft32 ICE on 931110-1.c with new TYPE_PRECISION checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110460 Richard Biener changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug tree-optimization/110460] [14 Regression] ft32 ICE on 931110-1.c with new TYPE_PRECISION checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110460 Manuel Lauss changed: What|Removed |Added CC||manuel.lauss at googlemail dot com ---

[Bug c/110482] ICE tree check: expected none of vector_type, have vector_type in type_has_mode_precision_p, at tree.h:6644

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

[Bug c++/110484] New: 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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110484 Bug ID: 110484 Summary: Spec2017 541 after adding the '-flto-fomit-frame-pointer' optimization, after optimizing the rnreg, directly replaced other registers with

[Bug tree-optimization/110458] -Warray-bounds=2 new false positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110458 --- Comment #2 from Franz Sirl --- This has been exposed by commit r14-2013-gfb0447b1f6b7373f57cb3a3d17a46803cfd9909d "Hide IVOPTs strip_offset".

[Bug c++/110477] -fexcess-precision=standard not applied consistently

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110477 --- Comment #8 from Peter Dimov --- As I commented on the duplicate bug, I don't think this behavior is allowed by https://eel.is/c++draft/lex.fcon#3. "If the scaled value is not in the range of representable values for its type, the program

[Bug analyzer/110483] New: Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110483 Bug ID: 110483 Summary: Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug analyzer/110483] Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110483 Rainer Orth changed: What|Removed |Added Target Milestone|--- |14.0

[Bug c++/110476] constexpr floating point regression with -std=c++XX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110476 --- Comment #3 from Jonathan Wakely --- I think the justification for GCC's behaviour is that "representable value" is to be interpreted in the context of FLT_EVAL_METHOD, so it means representable as double (for FLT_EVAL_METHOD==1) or long

[Bug rtl-optimization/110479] Unnecessary register move

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110479 --- Comment #1 from Uroš Bizjak --- (In reply to Thomas Koenig from comment #0) > movl%edi, %ecx This one? It is needed because SAL wants its count argument in %cl and first argument is passed in %edi (mandated by x86_64 ABI).

[Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077 --- Comment #7 from Rainer Orth --- Created attachment 55426 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55426=edit 32-bit i386-pc-solaris2.11 charconv.ii

[Bug tree-optimization/110460] [14 Regression] ft32 ICE on 931110-1.c with new TYPE_PRECISION checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110460 --- Comment #4 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:cd23ed2119120bd7b710fbe679fdfcb8f4461800 commit r14-2186-gcd23ed2119120bd7b710fbe679fdfcb8f4461800 Author: Richard Biener Date:

[Bug c++/110476] constexpr floating point regression with -std=c++XX

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110476 --- Comment #2 from Peter Dimov --- Discussion of FLT_EVAL_METHOD notwithstanding, I think that this behavior is not allowed by https://eel.is/c++draft/lex.fcon#3. "If the scaled value is not in the range of representable values for its type,

[Bug target/110457] Unnecessary movsx eax, dil

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110457 Xi Ruoyao changed: What|Removed |Added Ever confirmed|0 |1 CC|

[Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077 --- Comment #8 from Rainer Orth --- (In reply to Jonathan Wakely from comment #6) > This is going to be hard for me to figure out without access to a Solaris > x86 system. There's hope that at least one, maybe two, Solaris 11.4/x86 systems can

[Bug c++/110486] New: gcc rejects constant expression with consteval lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110486 Bug ID: 110486 Summary: gcc rejects constant expression with consteval lambda Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug tree-optimization/110311] [14 Regression] regression in tree-optimizer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110311 --- Comment #24 from Jürgen Reuter --- Here is a first reproducer without the need for OCaml, unfortunately a bit too big to be uploaded, here is the link: https://www.desy.de/~reuter/downloads/repro001.tar.xz the tarball contains Fortran files

[Bug rtl-optimization/110479] Unnecessary register move

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

[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

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

[Bug tree-optimization/110252] [14 Regression] Wrong code at -O2/3/s on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110252 --- Comment #11 from Andrew Pinski --- *** Bug 110475 has been marked as a duplicate of this bug. ***

[Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077 --- Comment #12 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #10) > (In reply to Jonathan Wakely from comment #9) > > One solution would be to just add the declaration to the header, and adjust > > the exports so this new

[Bug libstdc++/110462] [14 regression] Build failure with musl-1.2.4 (filesystem/ops-common.h:377:5: error: 'off64_t' was not declared in this scope; did you mean 'off_t'?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110462 Jonathan Wakely changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c/38341] Wrong warning comparison of promoted ~unsigned with unsigned

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38341 wolter.hellmundvega at tevva dot com changed: What|Removed |Added CC|

[Bug c++/110486] gcc rejects constant expression with consteval lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110486 --- Comment #1 from Andrew Pinski --- The question is the second lamdba implicitly consteval or not ... If it is, then the bug is dealing with that. That is adding consteval to the second lamdba allows GCC to accept the code.

[Bug libstdc++/110462] [14 regression] Build failure with musl-1.2.4 (filesystem/ops-common.h:377:5: error: 'off64_t' was not declared in this scope; did you mean 'off_t'?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110462 --- Comment #11 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:ff29ee6af88f709e08ee467869d8c1b13889a724 commit r14-2191-gff29ee6af88f709e08ee467869d8c1b13889a724 Author: Jonathan Wakely

[Bug tree-optimization/110475] [14 Regression] Wrong code at -O2/3/s on x86_64-pc-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110475 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|ASSIGNED

[Bug testsuite/110419] [14 regression] new test case gfortran.dg/value_9.f90 in r14-2050-gd130ae8499e0c6 fails

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110419 --- Comment #3 from seurer at gcc dot gnu.org --- I just tried r14-2190-ge972bdce61cc52 on another BE machine and got: spawn [open ...] by value(kind=1): B by value(kind=1): A Program received signal SIGSEGV: Segmentation fault - invalid

[Bug libstdc++/110432] macOS: Segmentation fault when using stdlibc++ from gcc 13.1 in combination with clang-16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432 --- Comment #8 from Sascha Scandella --- I've tested the proposed solution ... #if !__has_attribute(__init_priority__) || defined __APPLE__ ... and it works as expected. I had also done something similar before, so I wasn't that surprised.

[Bug tree-optimization/110458] [14 Regression] -Warray-bounds=2 new false positive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110458 Andrew Pinski changed: What|Removed |Added Summary|-Warray-bounds=2 new false |[14 Regression]

[Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077 --- Comment #10 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #9) > One solution would be to just add the declaration to the header, and adjust > the exports so this new symbol is exported at GLIBCXX_3.4.32 not >

[Bug libstdc++/110077] [14 regression] libstdc++-abi/abi_check FAILs on Solaris

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110077 --- Comment #11 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #1) > This affects aarch64 too: > https://gcc.gnu.org/pipermail/gcc-patches/2023-June/620335.html > And probably other targets where long double uses binary128

[Bug middle-end/110472] 60% slowdown with fwrapv when using openmp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110472 --- Comment #2 from Ryan Holt --- (In reply to Andrew Pinski from comment #1) > I think it is just wrong iv-opt choices. > > Works just fine on aarch64-linux-gnu too: > ubuntu@ubuntu:~/src/upstream-gcc-aarch64\# ~/upstream-gcc/bin/gcc t4.c -O2

[Bug c/101537] -Wconversion false positive in ternary and |=

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101537 --- Comment #9 from wolter.hellmundvega at tevva dot com --- Will the current fix be released when the C++ FE is patched as well or perhaps before that?

[Bug tree-optimization/110381] [11/12/13 Regression] double counting for sum of structs of floating point types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110381 Christophe Lyon changed: What|Removed |Added CC||clyon at gcc dot gnu.org --- Comment

[Bug libstdc++/110432] macOS: Segmentation fault when using stdlibc++ from gcc 13.1 in combination with clang-16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432 Patrick Palka changed: What|Removed |Added Status|NEW |ASSIGNED Target Milestone|---

[Bug target/110478] RISC-V multilib gcc zicsr in the -march causing incorrect libgcc to be used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110478 --- Comment #4 from Bin Meng --- I can't get the build to pass with the same configure scripts on current GCC HEAD :( --host=x86_64-linux-gnu --build=aarch64-linux --target=riscv64-linux --enable-targets=all

[Bug libstdc++/107852] [12 Regression] Spurious warnings stringop-overflow and array-bounds copying data as bytes into vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107852 Rogério de Souza Moraes changed: What|Removed |Added CC||rogerio.souza at gmail dot

[Bug libstdc++/107852] [12 Regression] Spurious warnings stringop-overflow and array-bounds copying data as bytes into vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107852 --- Comment #17 from Rogério de Souza Moraes --- Created attachment 55428 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55428=edit Preprocessed file for GCC 13.1.0 bug This is the preprocessed file (*.i*) that triggers the bug reported

[Bug libstdc++/110432] macOS: Segmentation fault when using stdlibc++ from gcc 13.1 in combination with clang-16

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110432 --- Comment #10 from Iain Sandoe --- (In reply to Patrick Palka from comment #9) > (In reply to Jonathan Wakely from comment #1) > > Patrick, we talked about this and IIRC your suggestion was to move the > > __has_attribute check into

  1   2   >