[Bug bootstrap/92002] [10 regression] -Wuninitialized warning in gcc/wide-int.cc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92002 Eric Botcazou changed: What|Removed |Added Target|sparcv9-sun-solaris2.11 |sparcv9-*-*

[Bug tree-optimization/91975] worse code for small array copy using pointer arithmetic than array indexing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91975 --- Comment #4 from Richard Biener --- Author: rguenth Date: Mon Oct 7 07:53:45 2019 New Revision: 276645 URL: https://gcc.gnu.org/viewcvs?rev=276645=gcc=rev Log: 2019-10-07 Richard Biener PR tree-optimization/91975 *

[Bug c++/92010] New: gcc internal error since 8x on warning write-strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92010 Bug ID: 92010 Summary: gcc internal error since 8x on warning write-strings Product: gcc Version: 9.2.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug ada/91995] gnat miscompilation and bootstrap failure on m68k-linux

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91995 Eric Botcazou changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug tree-optimization/91975] worse code for small array copy using pointer arithmetic than array indexing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91975 --- Comment #5 from Richard Biener --- So in addition to the unrolling heuristics we can see that at -O2 PRE defeats memcpy detection for g0 and f0 (but PRE does nothing to g1 and f1). At -O3 PRE avoids this transform because of heuristics

[Bug rtl-optimization/91994] [10 Regression] r276327 breaks -mvzeroupper

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91994 --- Comment #7 from rsandifo at gcc dot gnu.org --- Author: rsandifo Date: Mon Oct 7 08:36:06 2019 New Revision: 276648 URL: https://gcc.gnu.org/viewcvs?rev=276648=gcc=rev Log: [i386] Make the vzeroupper pattern describe its effects (PR91994)

[Bug c++/92009] [10 Regression] ICE: Segmentation fault (in is_really_empty_class)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92009 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug c++/92011] New: '' may be used uninitialized in this function with std::optional()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92011 Bug ID: 92011 Summary: '' may be used uninitialized in this function with std::optional() Product: gcc Version: 9.2.0 Status: UNCONFIRMED Severity: normal

[Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)

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

[Bug c++/92009] [10 Regression] ICE: Segmentation fault (in is_really_empty_class)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92009 Jakub Jelinek changed: What|Removed |Added Status|ASSIGNED|NEW CC|

[Bug rtl-optimization/91860] [10 Regression] ICE: in decompose, at rtl.h:2279 with -Og -fipa-cp -g --param=max-combine-insns=3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91860 --- Comment #7 from Zdenek Sojka --- Created attachment 47003 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47003=edit testcase that does not need any special compiler flag $ riscv64-unknown-linux-gnu-gcc -O2 -g testcase.c during RTL

[Bug fortran/42118] Slow forall

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42118 --- Comment #10 from Lionel GUEZ --- (In reply to kargl from comment #9) > Fortran 2018 has declared FORALL to be an obsolescent feature. > I doubt that anyone will ever try to improve the performance > of FORALL, because the next standard is

[Bug fortran/92004] [10 Regression] Rejection of different ranks for dummy array argument where actual argument is an element

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92004 Richard Biener changed: What|Removed |Added Priority|P3 |P4 Version|unknown

[Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug rtl-optimization/91994] [10 Regression] r276327 breaks -mvzeroupper

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91994 rsandifo at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug target/91970] arm: 64bit int to double conversion does not respect rounding mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91970 --- Comment #7 from nsz at gcc dot gnu.org --- i think the code snippet i posted is more efficient and significantly smaller than using libgcc (which also sounds hard to wire up to do the right thing). the code sequence can possibly be even

[Bug c++/92010] [8/9/10 Regression] gcc internal error since 8x on warning write-strings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92010 Jakub Jelinek changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug tree-optimization/92005] [10 Regression] switch code generation regression

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

[Bug target/77918] S390: Floating point comparisons don't raise invalid for unordered operands.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77918 --- Comment #7 from iii at gcc dot gnu.org --- Author: iii Date: Mon Oct 7 15:01:15 2019 New Revision: 276660 URL: https://gcc.gnu.org/viewcvs?rev=276660=gcc=rev Log: Introduce can_vcond_compare_p function z13 supports only non-signaling

[Bug rtl-optimization/91994] [10 Regression] r276327 breaks -mvzeroupper

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91994 Uroš Bizjak changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[Bug other/91879] --with-build-time-tools doesn't work as expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879 --- Comment #28 from Stas Sergeev --- (In reply to jos...@codesourcery.com from comment #22) > The build system design is that where A and B are both built at the same > time, and the build of B uses A, it should use the *newly built* copy of A

[Bug c++/92012] internal compiler error while using range v3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92012 Marek Polacek changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org --- Comment

[Bug c++/92013] New: _mm_broadcastsd_pd missing in avx2intrin.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92013 Bug ID: 92013 Summary: _mm_broadcastsd_pd missing in avx2intrin.h Product: gcc Version: 9.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug target/77918] S390: Floating point comparisons don't raise invalid for unordered operands.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77918 --- Comment #6 from iii at gcc dot gnu.org --- Author: iii Date: Mon Oct 7 14:59:00 2019 New Revision: 276659 URL: https://gcc.gnu.org/viewcvs?rev=276659=gcc=rev Log: Allow COND_EXPR and VEC_COND_EXPR condtions to trap Right now gimplifier

[Bug c++/92012] New: internal compiler error while using range v3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92012 Bug ID: 92012 Summary: internal compiler error while using range v3 Product: gcc Version: 9.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug fortran/84487] [8/9 Regression] Large rodate section increase in 465.tonto with r254427

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84487 --- Comment #27 from Thomas Koenig --- Author: tkoenig Date: Mon Oct 7 20:10:22 2019 New Revision: 276672 URL: https://gcc.gnu.org/viewcvs?rev=276672=gcc=rev Log: 2019-10-07 Thomas Koenig Backport from trunk PR fortran/84487

[Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163 Bug 26163 depends on bug 84487, which changed state. Bug 84487 Summary: [8/9 Regression] Large rodate section increase in 465.tonto with r254427 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84487 What|Removed

[Bug other/84613] [meta-bug] SPEC compiler performance issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84613 Bug 84613 depends on bug 84487, which changed state. Bug 84487 Summary: [8/9 Regression] Large rodate section increase in 465.tonto with r254427 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84487 What|Removed

[Bug fortran/84487] [8/9 Regression] Large rodate section increase in 465.tonto with r254427

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

[Bug target/91275] __builtin_crypto_vpmsumd gives different results -O[123] vs -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91275 Bill Schmidt changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #20 from Bill Schmidt

[Bug target/91275] __builtin_crypto_vpmsumd gives different results -O[123] vs -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91275 --- Comment #18 from Bill Schmidt --- Author: wschmidt Date: Mon Oct 7 20:50:05 2019 New Revision: 276678 URL: https://gcc.gnu.org/viewcvs?rev=276678=gcc=rev Log: [gcc] 2019-10-07 Bill Schmidt Backport from mainline

[Bug c++/91930] [10 Regression] internal compiler error: in lazily_declare_fn, at cp/method.c:2423 with -fconcepts

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91930 ensadc at mailnesia dot com changed: What|Removed |Added CC||ensadc at mailnesia dot com

[Bug other/91879] --with-build-time-tools doesn't work as expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879 --- Comment #30 from Stas Sergeev --- (In reply to jos...@codesourcery.com from comment #29) > A common way of doing that is to make $host and $build textually different > (after passing through config.sub) while still logically the same. E.g.

[Bug fortran/84487] [8/9 Regression] Large rodate section increase in 465.tonto with r254427

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84487 --- Comment #28 from Thomas Koenig --- Author: tkoenig Date: Mon Oct 7 20:12:00 2019 New Revision: 276673 URL: https://gcc.gnu.org/viewcvs?rev=276673=gcc=rev Log: 2019-10-07 Thomas Koenig Backport from trunk PR fortran/84487

[Bug fortran/92020] New: Improve handling of __def_init / xfail of typebound_call_22.f03

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92020 Bug ID: 92020 Summary: Improve handling of __def_init / xfail of typebound_call_22.f03 Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal

[Bug target/91275] __builtin_crypto_vpmsumd gives different results -O[123] vs -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91275 Bill Schmidt changed: What|Removed |Added Status|NEW |RESOLVED Known to work|

[Bug fortran/91984] Handling of __def_init_*

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91984 --- Comment #1 from Thomas Koenig --- *** Bug 92020 has been marked as a duplicate of this bug. ***

[Bug fortran/92020] Improve handling of __def_init / xfail of typebound_call_22.f03

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

[Bug fortran/91984] Handling of __def_init_*

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91984 --- Comment #2 from Thomas Koenig --- Of course, don't forget the xfail on typebound_call_22.f03.

[Bug target/91970] arm: 64bit int to double conversion does not respect rounding mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91970 --- Comment #8 from joseph at codesourcery dot com --- The code snippet you posted looks like exactly what libgcc2.c would typically do for __floatundidf. Given that, I'd prefer building the relevant function from libgcc2.c rather than having

[Bug fortran/66910] allocatable character in derived type gives segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66910 Thomas Koenig changed: What|Removed |Added Last reconfirmed|2015-09-06 00:00:00 |2019-10-7 --- Comment #2 from Thomas

[Bug other/91879] --with-build-time-tools doesn't work as expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879 --- Comment #29 from joseph at codesourcery dot com --- On Mon, 7 Oct 2019, stsp at users dot sourceforge.net wrote: > Is there any way to convince the build system that the > resulting compiler is alien and cannot be used? I think A common

[Bug target/91275] __builtin_crypto_vpmsumd gives different results -O[123] vs -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91275 --- Comment #17 from Bill Schmidt --- Author: wschmidt Date: Mon Oct 7 19:34:41 2019 New Revision: 276669 URL: https://gcc.gnu.org/viewcvs?rev=276669=gcc=rev Log: [gcc] 2019-10-07 Bill Schmidt Backport from mainline

[Bug target/91829] compatibility.cc: syntax error lea (%pc, _GLOBAL_OFFSET_TABLE@GOTPC), a4 ignored

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91829 --- Comment #3 from Jon Daniel --- replacing `return "lea (%%pc, _GLOBAL_OFFSET_TABLE_@GOTPC), %0";` with `return "lea (%%pc, #_GLOBAL_OFFSET_TABLE_@GOTPC), %0";`

[Bug target/51751] COMPLEX16 tests fail in Lapack

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

[Bug ipa/60243] IPA is slow on large cgraph tree

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60243 --- Comment #26 from Martin Jambor --- With new IPA-SRA, the situation has improved quite a bit, see below where old-ipa-sra is trunk r275981 and new-ipa-sra is trunk r275982 (arrival of new IPA-SRA): $ /usr/bin/time -f 'real=%e user=%U'

[Bug middle-end/92016] New: excess errors in Wstringop-overflow-17.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92016 Bug ID: 92016 Summary: excess errors in Wstringop-overflow-17.c Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/91275] __builtin_crypto_vpmsumd gives different results -O[123] vs -O0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91275 --- Comment #16 from Bill Schmidt --- Author: wschmidt Date: Mon Oct 7 18:23:20 2019 New Revision: 276667 URL: https://gcc.gnu.org/viewcvs?rev=276667=gcc=rev Log: [gcc] 2019-10-07 Bill Schmidt Backport from mainline

[Bug fortran/92017] New: ICE in gfc_expr_attr, at fortran/primary.c:2674

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92017 Bug ID: 92017 Summary: ICE in gfc_expr_attr, at fortran/primary.c:2674 Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/92019] New: [10 Regression] ICE in find_inquiry_ref, at expr.c:1790

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92019 Bug ID: 92019 Summary: [10 Regression] ICE in find_inquiry_ref, at expr.c:1790 Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal

[Bug c++/92013] _mm_broadcastsd_pd missing in avx2intrin.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92013 --- Comment #1 from H.J. Lu --- _mm_broadcastsd_pd is mapped to MOVDDUP __m128d _mm_movedup_pd (__m128d a); which is available with SSE3.

[Bug c++/92015] [9/10 Regression] internal compiler error: in cxx_eval_array_reference, at cp/constexpr.c:2568

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92015 Marek Polacek changed: What|Removed |Added Keywords||ice-on-valid-code

[Bug tree-optimization/91734] gcc skip an if statement with "-O1 -ffast-math"

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

[Bug c++/92011] '' may be used uninitialized in this function with std::optional()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92011 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org See

Re: [Bug rtl-optimization/91994] [10 Regression] r276327 breaks -mvzeroupper

"ubizjak at gmail dot com" writes: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91994 > > --- Comment #10 from Uroš Bizjak --- > Richard, since vzeroupper clobbers only xmm0-xmm15 (xmm0-xmm7 on 32it > targets), > shouldn't we use SSE_REGS instead of ALL_SSE_REGS here: > > Index: i386.c >

[Bug rtl-optimization/91994] [10 Regression] r276327 breaks -mvzeroupper

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91994 --- Comment #11 from richard.sandiford at arm dot com --- "ubizjak at gmail dot com" writes: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91994 > > --- Comment #10 from Uroš Bizjak --- > Richard, since vzeroupper clobbers only xmm0-xmm15

[Bug c++/92015] New: internal compiler error: in cxx_eval_array_reference, at cp/constexpr.c:2568

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92015 Bug ID: 92015 Summary: internal compiler error: in cxx_eval_array_reference, at cp/constexpr.c:2568 Product: gcc Version: 9.1.0 Status: UNCONFIRMED Severity:

[Bug rtl-optimization/91994] [10 Regression] r276327 breaks -mvzeroupper

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91994 --- Comment #10 from Uroš Bizjak --- Richard, since vzeroupper clobbers only xmm0-xmm15 (xmm0-xmm7 on 32it targets), shouldn't we use SSE_REGS instead of ALL_SSE_REGS here: Index: i386.c

[Bug tree-optimization/90839] Detect lsb ones counting loop (final value replacement?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90839 --- Comment #4 from Dmitrij Pochepko --- (In reply to Andrew Pinski from comment #3) > ... I haven't tracked deepsjeng data passed for logL function specifically. I only measured totals. It might be not directly related to logL code execution

[Bug c++/92013] _mm_broadcastsd_pd missing in avx2intrin.h

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92013 --- Comment #2 from DrTroll at gmx dot de --- @H.J. Lu I am aware, that _mm_broadcastsd_pd does the same as _mm_movedup_pd. However, maybe others are not. The fact that _mm_broadcastsd_pd is listed in the intel intrinsics guide and won't compile

[Bug fortran/92018] New: ICE in gfc_conv_constant_to_tree, at fortran/trans-const.c:370

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92018 Bug ID: 92018 Summary: ICE in gfc_conv_constant_to_tree, at fortran/trans-const.c:370 Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal

[Bug middle-end/92014] New: [10 Regression] bogus warning: writing 8 bytes into a region of size 1 in timezone/zic.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92014 Bug ID: 92014 Summary: [10 Regression] bogus warning: writing 8 bytes into a region of size 1 in timezone/zic.c Product: gcc Version: 9.0 Status: UNCONFIRMED

[Bug middle-end/92014] [10 Regression] bogus warning: writing 8 bytes into a region of size 1 in timezone/zic.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92014 Martin Sebor changed: What|Removed |Added Keywords||diagnostic

[Bug c++/92001] missing -Wclass-memaccess with array as first argument to memset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92001 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug libbacktrace/88745] Darwin lacks an implementation for libbacktrace

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745 --- Comment #4 from Eric Gallager --- (In reply to Ian Lance Taylor from comment #3) > filetype.awk is just an AWK script. See > https://www.gnu.org/software/gawk/manual/gawk.html. A Mach-O file starts > with 0xfeedface (32-bit Mach-O) or

[Bug fortran/92006] storage_size() returns incorrect value on unlimited polymorphic variable (CLASS(*)) when passed a CHARACTER variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92006 --- Comment #4 from Steve Kargl --- On Tue, Oct 08, 2019 at 03:22:01AM +, urbanjost at comcast dot net wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92006 > > --- Comment #3 from urbanjost at comcast dot net --- > (In reply to kargl

[Bug tree-optimization/91532] [SVE] Redundant predicated store in gcc.target/aarch64/fmla_2.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91532 --- Comment #2 from prathamesh3492 at gcc dot gnu.org --- Author: prathamesh3492 Date: Mon Oct 7 23:44:49 2019 New Revision: 276681 URL: https://gcc.gnu.org/viewcvs?rev=276681=gcc=rev Log: 2019-10-07 Prathamesh Kulkarni Richard

[Bug middle-end/92014] [10 Regression] bogus warning: writing 8 bytes into a region of size 1 in timezone/zic.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92014 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #1 from Martin Sebor

[Bug c++/92001] missing -Wclass-memaccess with array as first argument to memset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92001 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #2 from Martin Sebor

[Bug libbacktrace/88745] Darwin lacks an implementation for libbacktrace

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745 --- Comment #2 from Eric Gallager --- (In reply to Eric Gallager from comment #1) > I tried to start doing this in my fork of gdb but I didn't get very far; > here's a brief TODO: > > 1. Get filetype.awk to recognize mach-o binaries > 2. Add a

[Bug libbacktrace/88745] Darwin lacks an implementation for libbacktrace

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745 Ian Lance Taylor changed: What|Removed |Added CC||ian at airs dot com --- Comment #3

[Bug other/91879] --with-build-time-tools doesn't work as expected

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91879 --- Comment #31 from Stas Sergeev --- (In reply to jos...@codesourcery.com from comment #29) > A common way of doing that is to make $host and $build textually different > (after passing through config.sub) while still logically the same.

[Bug fortran/92006] storage_size() returns incorrect value on unlimited polymorphic variable (CLASS(*)) when passed a CHARACTER variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92006 --- Comment #3 from urbanjost at comcast dot net --- (In reply to kargl from comment #2) > Depends on, if not a duplicate, of 84006 84006 is showing an ICE when calling STORAGE_SIZE() with an unallocated variable, which I believe is invalid

[Bug c/46635] c-family/c-common.c uses BITS_PER_UNIT in lieu of TYPE_PRECISION (char_type_node)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46635 --- Comment #2 from Eric Gallager --- (In reply to Jorn Wolfgang Rennecke from comment #1) > As Joseph S. Myers bentioned in comment 1 of PR46633, (this is the last bug open blocking that one, btw)

[Bug other/46633] [meta-bug] frontends use BITS_PER_UNIT when they mean TYPE_PRECISION (char_type_node)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46633 --- Comment #2 from Eric Gallager --- Does "frontends" in the title really need to be pluralized when there's only one left?

[Bug c++/80518] -Wsuggest-override does not warn about missing override on destructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80518 --- Comment #8 from Eric Gallager --- (In reply to Jonathan Wakely from comment #7) > The guideline might be changing: > https://github.com/isocpp/CppCoreGuidelines/pull/1448 > If that pull request is merged we might want to change