[Bug libstdc++/109162] C++23 improvements to std::format

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109162 --- Comment #10 from GCC Commits --- The master branch has been updated by Tomasz Kaminski : https://gcc.gnu.org/g:3b33d792cf1e4d2ea3d36d3ad403cbb452243cd8 commit r15-9377-g3b33d792cf1e4d2ea3d36d3ad403cbb452243cd8 Author: Tomasz KamiÅski Date

[Bug tree-optimization/119707] wrong code with _BitInt() mask and shift at -O1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119707 --- Comment #6 from Jakub Jelinek --- Fixed on the trunk so far.

[Bug tree-optimization/119707] wrong code with _BitInt() mask and shift at -O1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119707 --- Comment #5 from GCC Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:b57d7ef4bdda8f939d804bfe40123cb9e4b447b3 commit r15-9376-gb57d7ef4bdda8f939d804bfe40123cb9e4b447b3 Author: Jakub Jelinek Date: F

[Bug tree-optimization/119706] [12/13/14 regression] ICE in gimple pass 'dom' for -O3 -mcpu=grace --param=aarch64-autovec-preference=sve-only

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119706 --- Comment #8 from GCC Commits --- The master branch has been updated by Jennifer Schmitz : https://gcc.gnu.org/g:f6e6e6d9ba1d71fdd02a2c570d60217db6c5a31b commit r15-9375-gf6e6e6d9ba1d71fdd02a2c570d60217db6c5a31b Author: Jennifer Schmitz Dat

[Bug cobol/119694] Excessive getenv uses in cobol FE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119694 --- Comment #4 from Jakub Jelinek --- Note, if SHOW_PARSE is something like dumping the semantic IL, then the usual way is have a compiler option and dump the details into a file. Either as messages into the -fdump-tree-original file or see e.g.

[Bug debug/119711] dw_attr_struct and dw_loc_descr_node are wasteful with padding

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119711 --- Comment #4 from Richard Biener --- (In reply to Jakub Jelinek from comment #3) > Created attachment 61064 [details] > gcc15-pr119711.patch > > Untested fix. Ah, interesting way with the macros to reduce the size of the change. The alterna

[Bug tree-optimization/119351] [15 Regression] Wrong code in GROMACS for AArch64 generic SVE VLS target since r15-6807-g68326d5d1a593d

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119351 --- Comment #18 from Tamar Christina --- (In reply to Richard Biener from comment #17) > I wonder if we can use > > BIT_FIELD_REF > > as the "reduction" step. Yeah that's the same comment Richard S suggested when we were talking to avoid th

[Bug tree-optimization/119351] [15 Regression] Wrong code in GROMACS for AArch64 generic SVE VLS target since r15-6807-g68326d5d1a593d

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119351 --- Comment #17 from Richard Biener --- I wonder if we can use BIT_FIELD_REF as the "reduction" step.

[Bug tree-optimization/119722] New: wrong code with _BitInt(), __builtin_stdc_rotate_left() at -O2 -fno-tree-forwprop -fno-tree-copy-prop -fno-tree-fre

-release-nobootstrap-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 15.0.1 20250410 (experimental) (GCC)

[Bug c/83537] missing integer overflow in offsetof not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83537 --- Comment #2 from Andrew Pinski --- This was noticed on Mastodon today: https://infosec.exchange/@jann/114315567622777610

[Bug cobol/119694] Excessive getenv uses in cobol FE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119694 Robert Dubner changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |rdubner at gcc dot gnu.org

[Bug preprocessor/106767] Failure to detect recursive macro calls due to _Pragma(pop_macro)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106767 Andi Kleen changed: What|Removed |Added CC||andi-gcc at firstfloor dot org --- Comment

[Bug preprocessor/118770] Random Segmentation fault in preprocessor from _Pragma push pop within _Pragma

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118770 --- Comment #5 from Andrew Pinski --- (In reply to ymity.me from comment #4) > I would expect it to take longer in such a case, it's almost instant on my > laptop, and quite random on my tower pc. If i modify it just a little bit it > would cont

[Bug gcov-profile/119719] Suitability of gcov for very resource-constrained systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119719 duane ellis changed: What|Removed |Added CC||duane at duaneellis dot com --- Comment #

[Bug gcov-profile/119719] Suitability of gcov for very resource-constrained systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119719 --- Comment #7 from duane ellis --- (In reply to Andi Kleen from comment #3) > autofdo is probably too big for 32K, so it would be only possible over JTAG no i need execution coverage and jtag will no help

[Bug gcov-profile/119719] Suitability of gcov for very resource-constrained systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119719 --- Comment #6 from duane ellis --- (In reply to Andi Kleen from comment #3) > autofdo is probably too big for 32K, so it would be only possible over JTAG no i need execution coverage and jtag will no help

[Bug gcov-profile/119719] Suitability of gcov for very resource-constrained systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119719 --- Comment #5 from duane ellis --- (In reply to Andrew Pinski from comment #1) > So this sounds like what autofdo does. I suspect you could hook up a similar > method for any profiling like program to autofdo. Currently the autofdo uses > perf

[Bug ada/119701] Ada.Calendar.Formatting.Day_Of_Week returns wrong value after Ada.Calendar.Time is incremented via Ada.Calendar.Arithmetic."+".

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119701 --- Comment #2 from William Rupert Greene --- Following your suggestions, here is the changed Ada program: with Ada.Calendar; -- (RM 9.6) with Ada.Calendar.Arithmetic; -- (RM 9.6.1) with Ada.Calendar.Formatting;

[Bug tree-optimization/87909] Undocumented option -f{,no-}tree-cselim

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87909 sandra at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[Bug tree-optimization/87909] Undocumented option -f{,no-}tree-cselim

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87909 --- Comment #2 from GCC Commits --- The master branch has been updated by Sandra Loosemore : https://gcc.gnu.org/g:f6b0dc1b1c5f1736e77a42512085f9ab290775fd commit r15-9374-gf6b0dc1b1c5f1736e77a42512085f9ab290775fd Author: Sandra Loosemore Date

[Bug libstdc++/119721] New: tuple<> cannot be compared with array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119721 Bug ID: 119721 Summary: tuple<> cannot be compared with array Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++

[Bug libfortran/119502] Runtime segfault when closing invalid unit

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119502 Jerry DeLisle changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org --

[Bug c/61744] misleading documentation about cast of extended vectors

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

[Bug c/85562] -Wsuggest-attribute=malloc misleads about "returning normally"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85562 sandra at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|-

[Bug target/113633] FAIL: gcc.dg/bf-ms-attrib.c execution test, wrong size for ms_struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113633 --- Comment #3 from GCC Commits --- The master branch has been updated by Jonathan Yong : https://gcc.gnu.org/g:7e6255edeb5a01d6ae1c2fa5bed391a836726229 commit r15-9373-g7e6255edeb5a01d6ae1c2fa5bed391a836726229 Author: Jonathan Yong <10wa...@g

[Bug middle-end/14708] description of -ffloat-store in gcc man page incorrect/inaccurate

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

[Bug middle-end/14708] description of -ffloat-store in gcc man page incorrect/inaccurate

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14708 --- Comment #10 from GCC Commits --- The master branch has been updated by Sandra Loosemore : https://gcc.gnu.org/g:0c210fbbd70af16326ca64bf3447eb38b6fd6e0d commit r15-9371-g0c210fbbd70af16326ca64bf3447eb38b6fd6e0d Author: Sandra Loosemore Dat

[Bug gcov-profile/119719] Suitability of gcov for very resource-constrained systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119719 Andi Kleen changed: What|Removed |Added CC||andi-gcc at firstfloor dot org --- Comment

[Bug c/119660] builtin functions erroneously suggested as originating in system headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119660 --- Comment #3 from Andrew Pinski --- There was a bug with respect to va_type causing issues IIRC.

[Bug c/119660] builtin functions erroneously suggested as originating in system headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119660 --- Comment #5 from Andrew Pinski --- This was the patch: https://gcc.gnu.org/legacy-ml/gcc-patches/2008-11/msg00644.html

[Bug c/119660] builtin functions erroneously suggested as originating in system headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119660 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug c/119660] builtin functions erroneously suggested as originating in system headers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119660 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug tree-optimization/116463] [15 Regression] complex multiply vectorizer detection failures after r15-3087-gb07f8a301158e5

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116463 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug target/116994] [15 regression] GCC trunk generates larger code than GCC 14 at -Os since r15-313-gd826f794560904

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116994 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c++/114970] [14/15 Regression] 32-bit ARM gcc-14.1 new false positive -Wunused-value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114970 --- Comment #8 from Sam James --- (In reply to Sam James from comment #7) > I'll test it. bootstrapped & regtested armv7a-unknown-linux-gnueabihf, and the file from this bug works now

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718 --- Comment #8 from lucier at math dot purdue.edu --- What I have in mind is along the lines of the patch I proposed here: https://gcc.gnu.org/pipermail/gcc-patches/2023-August/626368.html That adds a warning to -Wdisabled-optimization for when

[Bug tree-optimization/119720] phiopt introduces out-of-bounds reads

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119720 Andrew Pinski changed: What|Removed |Added Keywords||alias --- Comment #1 from Andrew Pinski

[Bug tree-optimization/119720] New: phiopt introduces out-of-bounds reads

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119720 Bug ID: 119720 Summary: phiopt introduces out-of-bounds reads Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optim

[Bug tree-optimization/119393] [15 Regression] Worse vectorization of imagick_r hot loop on aarch64 since r15-5024-g2a2e6784074e1f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119393 --- Comment #10 from Andrew Pinski --- (In reply to Andrew Pinski from comment #9) > Doing this : With this patch I do get one vect.exp extra failure: FAIL: g++.dg/vect/simd-complex-num-null-node.cc scan-tree-dump-times vect "stmt.*COMPLEX_MU

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718 --- Comment #7 from Jakub Jelinek --- (In reply to lucier from comment #6) > If musttail is going to change which tail calls are optimized, I really > think we need a warning flag that will have GCC give a warning when musttail > is not used on

[Bug gcov-profile/119719] Suitability of gcov for very resource-constrained systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119719 --- Comment #2 from Andrew Pinski --- See https://gcc.gnu.org/wiki/AutoFDO/Tutorial .

[Bug gcov-profile/119719] Suitability of gcov for very resource-constrained systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119719 --- Comment #1 from Andrew Pinski --- So this sounds like what autofdo does. I suspect you could hook up a similar method for any profiling like program to autofdo. Currently the autofdo uses perf (the Linux kernel userland tool) output to do it

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718 --- Comment #6 from lucier at math dot purdue.edu --- Thank you for the detailed explanation. What initially got me investigating this is that (a) these tail calls were not optimized by GCC 14 and I got segfaults, so (b) I added musttail and t

[Bug gcov-profile/119719] New: Suitability of gcov for very resource-constrained systems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119719 Bug ID: 119719 Summary: Suitability of gcov for very resource-constrained systems Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug c++/114970] [14/15 Regression] 32-bit ARM gcc-14.1 new false positive -Wunused-value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114970 --- Comment #7 from Sam James --- I'll test it.

[Bug c++/114970] [14/15 Regression] 32-bit ARM gcc-14.1 new false positive -Wunused-value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114970 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

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

[Bug tree-optimization/119393] [15 Regression] Worse vectorization of imagick_r hot loop on aarch64 since r15-5024-g2a2e6784074e1f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119393 Andrew Pinski changed: What|Removed |Added Blocks||53947 --- Comment #9 from Andrew Pinski

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718 --- Comment #4 from Sam James --- Using musttail also makes a promise to the compiler about whether things escape, though.

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718 --- Comment #3 from lucier at math dot purdue.edu --- Originally I understood musttail to be "It's crucial that this call be optimized, fail and tell me why if you can't do it", without changing whether a call is optimized. (This is always assum

[Bug c++/114970] [14/15 Regression] 32-bit ARM gcc-14.1 new false positive -Wunused-value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114970 --- Comment #5 from Jason Merrill --- Created attachment 61069 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61069&action=edit fix This seems like the fix, can someone test it?

[Bug ipa/119376] [15 Regression] musttail does not get dropped after inlining?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119376 Sam James changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718 --- Comment #2 from Andrew Pinski --- musttail does change the definition of the function call slightly when it comes to local variables escaping.

[Bug tree-optimization/119718] __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718 --- Comment #1 from lucier at math dot purdue.edu --- Created attachment 61068 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61068&action=edit test file This is the file with the single incident of __attribute__((musttail)). If you remov

[Bug tree-optimization/119718] New: __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119718 Bug ID: 119718 Summary: __attribute__((musttail)) affects whether -foptimize-tail-calls will in fact optimize a tail call Product: gcc Version: 15.0

[Bug c++/114970] [14/15 Regression] 32-bit ARM gcc-14.1 new false positive -Wunused-value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114970 --- Comment #4 from Andrew Pinski --- Created attachment 61067 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61067&action=edit preprocessed source

[Bug target/118541] Incorrect transformation to xscmpgtdp for Unordered Operations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541 --- Comment #7 from Segher Boessenkool --- isgreater is not supposed to set floating point exception flags at all. So whether the comparison resulted in unordered (i.e., one of the arguments was a NaN) or not, isgreater should not set VXVC in p

[Bug c++/114970] [14/15 Regression] 32-bit ARM gcc-14.1 new false positive -Wunused-value

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114970 Jason Merrill changed: What|Removed |Added CC||jason at gcc dot gnu.org --- Comment #3

[Bug fortran/119669] [15 Regression] ICE in compare_parameter since r15-7449

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119669 Thomas Koenig changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug c++/119175] [14/15 Regression] ICE segfault on lambda in requires clause of generic lambda in requires clause

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119175 Jason Merrill changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c++/119345] [14/15 Regression] ICE segfault on capturing lambda in fold expression in capturing lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119345 Jason Merrill changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c++/119345] [14/15 Regression] ICE segfault on capturing lambda in fold expression in capturing lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119345 --- Comment #5 from GCC Commits --- The releases/gcc-14 branch has been updated by Jason Merrill : https://gcc.gnu.org/g:779e002a1dc4ee7c688b7fb497375185cbcfec87 commit r14-11593-g779e002a1dc4ee7c688b7fb497375185cbcfec87 Author: Jason Merrill

[Bug c++/119175] [14/15 Regression] ICE segfault on lambda in requires clause of generic lambda in requires clause

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119175 --- Comment #4 from GCC Commits --- The releases/gcc-14 branch has been updated by Jason Merrill : https://gcc.gnu.org/g:e13143ab02172adf7b9a4a848c5c17f62579b9cf commit r14-11592-ge13143ab02172adf7b9a4a848c5c17f62579b9cf Author: Jason Merrill

[Bug c++/117530] [14 Regression] Mismatch of lambda type with itself in recursive alias declaration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117530 --- Comment #5 from GCC Commits --- The releases/gcc-14 branch has been updated by Jason Merrill : https://gcc.gnu.org/g:708c393774188d74399ec75ef20a522444b09f92 commit r14-11591-g708c393774188d74399ec75ef20a522444b09f92 Author: Jason Merrill

[Bug tree-optimization/119393] [15 Regression] Worse vectorization of imagick_r hot loop on aarch64 since r15-5024-g2a2e6784074e1f

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119393 --- Comment #8 from Andrew Pinski --- (In reply to Andrew Pinski from comment #7) > I don't see any difference between 14 and 15 with your reduced testcase at > `-Ofast -fno-early-inlining -mcpu=neoverse-v1+nosve ` . ok, the behavior of the vec

[Bug middle-end/119716] segmentation fault when Passing NULL pointer to _bdos with counted_by attribute

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119716 --- Comment #4 from Jakub Jelinek --- If the compiler compiles it and it misbehaves at runtime, that is valid behavior for undefined behavior. ICE (as in the other PR) is something we should fix.

[Bug libstdc++/21334] Lack of Posix compliant thread safety in std::basic_string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21334 Jonathan Wakely changed: What|Removed |Added Status|SUSPENDED |ASSIGNED Assignee|unassigned

[Bug c++/119705] Massive memory use when building Flang (10GB+)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119705 Andi Kleen changed: What|Removed |Added CC||andi-gcc at firstfloor dot org --- Comment

[Bug middle-end/119716] segmentation fault when Passing NULL pointer to _bdos with counted_by attribute

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119716 --- Comment #3 from qinzhao at gcc dot gnu.org --- (In reply to Jakub Jelinek from comment #2) > This is invalid testcase. > E.g. replace return __builtin_dynamic_object_size (p, 1); with return 0; > and try both gcc -fsanitize=undefined -g -O0 o

[Bug target/117229] [15 regression] "libcpp, c, middle-end: Optimize initializers using #embed in C" vs. GCN '-march=gfx908'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117229 --- Comment #14 from Andrew Pinski --- Wait a minute, strstr in newlib has undefined code in it. It does: hs--; which might cause undefinedness. glibc version does not have that though. I am not sure if that is the issue here though

[Bug c++/119345] [14/15 Regression] ICE segfault on capturing lambda in fold expression in capturing lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119345 --- Comment #4 from GCC Commits --- The trunk branch has been updated by Jason Merrill : https://gcc.gnu.org/g:5957b9919c9ecda6e4ca198086f8bb9ea215232c commit r15-9369-g5957b9919c9ecda6e4ca198086f8bb9ea215232c Author: Jason Merrill Date: Th

[Bug middle-end/119716] segmentation fault when Passing NULL pointer to _bdos with counted_by attribute

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

[Bug middle-end/119717] New: ICE in gimplify_expr, at gimplify.cc:20339 due to counted_by attribute

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119717 Bug ID: 119717 Summary: ICE in gimplify_expr, at gimplify.cc:20339 due to counted_by attribute Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/119716] segmentation fault when Passing NULL pointer to _bdos with counted_by attribute

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119716 qinzhao at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |qinzhao at gcc dot g

[Bug middle-end/119716] New: segmentation fault when Passing NULL pointer to _bdos with counted_by attribute

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119716 Bug ID: 119716 Summary: segmentation fault when Passing NULL pointer to _bdos with counted_by attribute Product: gcc Version: 15.0 Status: UNCONFIRMED Severity

[Bug c++/119687] [14/15 Regression] ICE when building kwin-6.3.4 against qt-6.9 (in operator*, at cp/cp-tree.h:876) (deduction guides related) since r14-10655

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119687 Patrick Palka changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c++/119687] [14/15 Regression] ICE when building kwin-6.3.4 against qt-6.9 (in operator*, at cp/cp-tree.h:876) (deduction guides related) since r14-10655

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119687 --- Comment #17 from GCC Commits --- The releases/gcc-14 branch has been updated by Patrick Palka : https://gcc.gnu.org/g:93be6016dae6e2f0bfe849ee0469a0a8ae0b9d5e commit r14-11590-g93be6016dae6e2f0bfe849ee0469a0a8ae0b9d5e Author: Patrick Palka

[Bug c++/119687] [14/15 Regression] ICE when building kwin-6.3.4 against qt-6.9 (in operator*, at cp/cp-tree.h:876) (deduction guides related) since r14-10655

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119687 --- Comment #16 from GCC Commits --- The master branch has been updated by Patrick Palka : https://gcc.gnu.org/g:493974aa0ad8b94dbeb61f00d2acc57c94fd4809 commit r15-9367-g493974aa0ad8b94dbeb61f00d2acc57c94fd4809 Author: Patrick Palka Date:

[Bug target/117229] [15 regression] "libcpp, c, middle-end: Optimize initializers using #embed in C" vs. GCN '-march=gfx908'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117229 --- Comment #13 from Andrew Pinski --- (In reply to Andrew Pinski from comment #12) > >but why for '-march=gfx908' only, but not '-march=gfx1100' (or nvptx, for > >example) > > Is newlib compiled for each of these multilib? If so it could be >

[Bug target/117229] [15 regression] "libcpp, c, middle-end: Optimize initializers using #embed in C" vs. GCN '-march=gfx908'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117229 --- Comment #12 from Andrew Pinski --- >but why for '-march=gfx908' only, but not '-march=gfx1100' (or nvptx, for >example) Is newlib compiled for each of these multilib? If so it could be ./newlib/libc/string/strstr.c (strstr) in newlib is mi

[Bug target/115259] [15 Regressions] GCN vs. "tree-optimization/115144 - improve sinking destination choice"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115259 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization --- Comment #14 fro

[Bug analyzer/119715] New: -Wanalyzer-infinite-loop: specify loop invariant in message where possible

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119715 Bug ID: 119715 Summary: -Wanalyzer-infinite-loop: specify loop invariant in message where possible Product: gcc Version: unknown Status: UNCONFIRMED Severity:

[Bug libstdc++/119708] : \00 should be rejected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119708 --- Comment #4 from Alfred Agrell --- No, that's not relevant to this bug either (though it is relevant to bug 109993). This bug is about ECMAScript flavor regex, not the POSIX ones.

[Bug c/119713] RISC-V: -march=rv64gcv gives an internal compiler error in a_as

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119713 --- Comment #2 from negge at dgql dot org --- Thanks Sam, rebuilding with gcc-15.0.1_pre20250406-r2 seems to have fixed it.

[Bug target/115259] [15 Regressions] GCN vs. "tree-optimization/115144 - improve sinking destination choice"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115259 --- Comment #13 from Andrew Pinski --- (In reply to Thomas Schwinge from comment #12) > Andrew P., thanks for having a look! > > I tested attachment 61055 [details]; terminates normally. :-| Try replacing `all_l4(&g, 4, 0);` with `all_l4(&g,

[Bug c++/119345] [14/15 Regression] ICE segfault on capturing lambda in fold expression in capturing lambda

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119345 Jason Merrill changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org

[Bug libstdc++/119708] : \00 should be rejected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119708 --- Comment #3 from Andrew Pinski --- Hmm https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03 .

[Bug libstdc++/119708] : \00 should be rejected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119708 --- Comment #2 from Alfred Agrell --- No, bug 84110 looks unrelated to me. That bug refers to actual 0x00 bytes in the input regex. This bug is about how the regex parser treats backslashes.

[Bug fortran/119669] [15 Regression] ICE in compare_parameter since r15-7449

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119669 --- Comment #6 from Thomas Koenig --- Created attachment 61066 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61066&action=edit Patch which sets the function attribute This should fix the issue. I am actually not quite sure if the new er

[Bug libstdc++/119708] : \00 should be rejected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119708 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug target/119691] gcc does not build for powerpc64-apple-darwin9: ld: bl out of range (-16845644 max is +/-16M) from __ZN10hash_tableI19default_hash_traitsIP11cgraph_edgeELb0E11xcallocatorED1Ev at 0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119691 --- Comment #6 from Sergey Fedorov --- (In reply to Iain Sandoe from comment #5) > Lets take this discussion elsewhere - e.g. to my Darwin toolchains - there > is no upstream solution to this on any of the components (cctools, ld64, > gcc, llvm)

[Bug libstdc++/119714] Failure when using == operator on a class derived from std::expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119714 --- Comment #1 from Andrew Pinski --- https://en.cppreference.com/w/cpp/utility/expected/operator_cmp This mentions that it is invalid for C++23 but would be valid for C++26. Looks like we have not implemented the 26 rules either.

[Bug libstdc++/119714] New: Failure when using == operator on a class derived from std::expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119714 Bug ID: 119714 Summary: Failure when using == operator on a class derived from std::expected Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal

[Bug rtl-optimization/119709] RISC-V: Why volatile int16_t variables generate extra shift instructions in compiler output

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119709 --- Comment #2 from Andrew Pinski --- I should mention this is a known issue and not one easily solvable. bug 60749 describes the internals of GCC on what is going wrong which is why it might not read as a duplicate. But this is the jist: In par

[Bug rtl-optimization/60749] combine is overly cautious when operating on volatile memory references

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

[Bug rtl-optimization/119709] RISC-V: Why volatile int16_t variables generate extra shift instructions in compiler output

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

[Bug fortran/119669] [15 Regression] ICE in compare_parameter since r15-7449

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

[Bug fortran/119669] [15 Regression] ICE in compare_parameter since r15-7449

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119669 Thomas Koenig changed: What|Removed |Added Status|WAITING |ASSIGNED Assignee|unassigned

[Bug fortran/119669] [15 Regression] ICE in compare_parameter since r15-7449

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119669 --- Comment #3 from Jakub Jelinek --- Note, removing the ! character makes it work.

[Bug fortran/119669] [15 Regression] ICE in compare_parameter since r15-7449

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119669 --- Comment #2 from Jakub Jelinek --- I can: /opt/notnfs/gcc-bisect/obj/gcc/f951.r15-9357 -quiet pr119669.f90 f951.r15-9357: internal compiler error: in compare_parameter, at fortran/interface.cc:2537 0x2d42e37 internal_error(char const*, ...)

  1   2   >