[Bug c/105863] RFE: C23 #embed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105863 --- Comment #11 from Joseph S. Myers --- It makes the changes more complicated (everything that handles CONSTRUCTORs, whether to output them to assembly or to extract values for optimization etc., needs to handle the new tree), but yes, having

[Bug c/115109] Incorrect type of enumeration constant in redeclaration of enumeration constant (C23)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115109 Joseph S. Myers changed: What|Removed |Added Status|UNCONFIRMED |NEW CC|

[Bug c/105863] RFE: C23 #embed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105863 --- Comment #9 from Joseph S. Myers --- The most straightforward and most important case to optimize is the one where the #embed expansion lies entirely inside a single character array initializer (possibly with some integer constants before or

[Bug c/81756] type attributes silently ignored on type declarations

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81756 --- Comment #3 from Joseph S. Myers --- This sort of "???" comment about existing practice means that some past change (in this case, the one adding support for [[]] attributes) was aiming to avoid perturbing how the compiler behaved for

[Bug c/114873] Incorrect warning generated for [*] array when in atomic or typeof type specifier for a parameter declaration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114873 --- Comment #4 from Joseph S. Myers --- These are not meant to be valid C (although the relevant requirement isn't a Constraint, so a diagnostic isn't required); see the discussion in DR#341.

[Bug c/114869] GCC says nullptr_t is a C built in but it should be in

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114869 Joseph S. Myers changed: What|Removed |Added Last reconfirmed||2024-04-29 CC|

[Bug c/114816] Non-standard behavior with void arguments

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114816 --- Comment #1 from Joseph S. Myers --- Note that it's not possible to define a function with such parameters ("After adjustment, the parameters in a parameter type list in a function declarator that is part of a definition of that function

[Bug c/114808] Qualified void return type is not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808 --- Comment #7 from Joseph S. Myers --- Yes, this is deliberate following the resolution of DR#423 which means qualifiers are ignored on function return types (it's still diagnosed in pre-C11 modes).

[Bug c/114746] With FLT_EVAL_METHOD = 2, -fexcess-precision=fast reduces the precision of floating-point constants and floating-point constant expressions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114746 --- Comment #3 from Joseph S. Myers --- The actual effect of -fexcess-precision=fast is more like "outside the back end, pretend excess precision doesn't exist, but the back end might use it anyway" (complicated a bit by having genuine excess

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

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114730 --- Comment #3 from Joseph S. Myers --- When implementing C23 enums with fixed underlying types I tried to ensure that enums with underlying type bool were handled consistently with bool (cf. bug 96496 where they're not always handled

[Bug c/114657] Invalid type conversion from some _BitInt bit-fields

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114657 --- Comment #3 from Joseph S. Myers --- https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2958.htm has my analysis of the various notions of "type" used in relation to bit-fields and the questions of what expressions are considered to have

[Bug c/114526] ISO C does not prohibit extensions: fix misconception.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114526 --- Comment #15 from Joseph S. Myers --- There are several statements such as "Any pointer type may be converted to an integer type." and "A pointer to an object type may be converted to a pointer to a different object type.", that allow

[Bug c/114526] ISO C does not prohibit extensions: fix misconception.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114526 --- Comment #11 from Joseph S. Myers --- I think that simply failing to say whether a value of type X may be converted to type Y is clearly enough for it at least to be unspecified whether or when such conversions are possible in a cast at all

[Bug libquadmath/114533] libquadmath: printf: fix misaligned access on args

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114533 --- Comment #7 from Joseph S. Myers --- Note also that in glibc, _Float128 support in printf code can only be used in limited circumstances: either on powerpc64le, as one of the multiple supported long double formats there, or through the

[Bug c/114526] ISO C does not prohibit extensions: fix misconception.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114526 --- Comment #8 from Joseph S. Myers --- "rejects", in the ISO C sense, only applies to errors and pedwarns in GCC; not to warnings conditional on -pedantic (of which there are also some, but which don't turn into errors with -pedantic). If you

[Bug c/114526] ISO C does not prohibit extensions: fix misconception.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114526 --- Comment #5 from Joseph S. Myers --- The -pedantic documentation was updated to reflect reality - that the option is about more than just when diagnostics are required by ISO C ("forbidden extensions" can be taken, in the C case, as meaning

[Bug c/112571] [13 Regression] ICE with nested redefinition of enum

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112571 Joseph S. Myers changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug tree-optimization/114469] gcc.dg/torture/bitint-64.c failure with -O2 -flto -std=c23 -fwrapv

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114469 --- Comment #1 from Joseph S. Myers --- I'd expect _Atomic _BitInt(5) to follow the same ABI (regarding upper bits being defined or not) as plain _BitInt(5), and any simplification needs to deal with that. (In principle for atomics with

[Bug tree-optimization/114465] "x % const1 % const2" should be optimized if const1 % const2 == 0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114465 --- Comment #1 from Joseph S. Myers --- Note that transforming x % 1 % -1 to x % -1 wouldn't strictly be valid (because of undefined behavior from INT_MIN % -1), though hopefully cases with constant 1 or -1 get optimized to 0 anyway and the

[Bug middle-end/114347] wrong constant folding when casting __bf16 to int

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114347 --- Comment #4 from Joseph S. Myers --- I think it's correct that conversions (explicit or implicit) from a value with excess precision convert only once; they don't first remove excess range and precision and then convert to the target type.

[Bug c/114266] No -pedantic diagnostic for zero-sized array in compound literals

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114266 Joseph S. Myers changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug middle-end/94083] inefficient soft-float x!=Inf code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94083 --- Comment #6 from Joseph S. Myers --- Contrary to what was claimed in bug 66462, I don't think there ever was a fixed patch. Note that in bug 66462 comment 19, "June" is June 2017 but "November" is November 2016 - the "November" one is the

[Bug libquadmath/114140] quadmath fminq/fmaxq with signaling_NaN not work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114140 --- Comment #2 from Joseph S. Myers --- Returning a quiet NaN when either argument is a signaling NaN is correct at least for C (fmin/fmax correspond to IEEE 754-2008 operations, *not* the new IEEE 754-2019 operations which are

[Bug tree-optimization/111770] predicated loads inactive lane values not modelled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111770 --- Comment #6 from Joseph S. Myers --- X + 0. -> X is invalid for FP with signed zero or signaling NaN, and also gets the wrong quantum exponent for decimal FP unless the zero has the maximum possible quantum exponent (which is not what you

[Bug preprocessor/114007] gcc chokes on __has_cpp_attribute(clang::unsafe_buffer_usage)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114007 --- Comment #16 from Joseph S. Myers --- I think it's clear that __has_c_attribute(gnu::unused) should only return 1 if the [[gnu::unused]] syntax is actually parsed. (An unavoidable limitation if it might return 1 in pre-C23 modes is that if

[Bug libstdc++/113450] [14 Regression] std/format/functions/format.cc FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113450 --- Comment #17 from Joseph S. Myers --- The tests that GCC's internal notion of the types agrees with the headers are in gcc.dg/c99-stdint-5.c and gcc.dg/c99-stdint-6.c.

[Bug libstdc++/114018] std::nexttoward is not implemented for C++23-FP-Types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114018 --- Comment #4 from Joseph S. Myers --- I don't know what's expected for C++, but for C, TS 18661-3 and C23 don't have versions of nexttoward for _FloatN or _FloatNx (recall that the second argument of nexttoward has type long double

[Bug c/113887] no support for %w128 length modifiers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113887 --- Comment #11 from Joseph S. Myers --- As I said in comment#2, I prefer a constant suffix for __int128 to the wb/uwb hack - I think it's cleaner, as well as allowing int128_t to work properly on all the targets that support __int128 but have

[Bug c/113887] no support for %w128 length modifiers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113887 --- Comment #5 from Joseph S. Myers --- Compiler and library are not in practice independent for this issue. GCC typically provides for freestanding compilations and forwards to a libc version for hosted compilations, and in both cases it

[Bug c/113887] no support for %w128 length modifiers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113887 --- Comment #2 from Joseph S. Myers --- https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643237.html has my notes on things that need supporting, in , and by implication in printf and scanf, to support __int128 as an extended integer

[Bug c/113825] missing warning for omitted parameter names in function definitions (c23 extension)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113825 Joseph S. Myers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/113776] [14 regression] postgresql-16.1 build failure with -Werror=vla in configure test since r14-8641

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113776 Joseph S. Myers changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c/113776] [14 regression] postgresql-16.1 build failure with -Werror=vla in configure test since r14-8641

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113776 Joseph S. Myers changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED

[Bug c/113455] ROUNDING: IEEE Standard: Missing decimal rounding mode 'nearest, ties away from zero' for decimalxxx datatypes.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113455 --- Comment #6 from Joseph S. Myers --- -frounding-math is only relevant for arithmetic that occurs as-if at runtime in the abstract machine. Conversion of constants to their type (or a type with excess range and precision as indicated by

[Bug target/113720] [14 Regression] internal compiler error: in extract_insn, at recog.cc:2812 targeting alpha-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113720 Joseph S. Myers changed: What|Removed |Added CC||jsm28 at gcc dot gnu.org,

[Bug c/112571] [13/14 Regression] ICE with nested redefinition of enum

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112571 Joseph S. Myers changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jsm28 at gcc dot gnu.org

[Bug c++/113674] [11/12/13/14 Regression] [[____attr____]] causes internal compiler error: in decl_attributes, at attribs.cc:776

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113674 --- Comment #5 from Joseph S. Myers --- C supports _Noreturn (and thus ___Noreturn__) as an attribute name, so that code with "#define noreturn _Noreturn" (probably from stdnoreturn.h) works with C23 [[noreturn]].

[Bug c/111911] [11/12/13 Regression] ICE with integer overflow converting to _Bool

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111911 Joseph S. Myers changed: What|Removed |Added Summary|[11/12/13/14 Regression]|[11/12/13 Regression] ICE

[Bug c/111059] [11/12/13 Regression] ICE: in gimplify_expr, at gimplify.cc:17253

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111059 Joseph S. Myers changed: What|Removed |Added Summary|[11/12/13/14 Regression]|[11/12/13 Regression] ICE:

[Bug c/111911] [11/12/13/14 Regression] ICE with integer overflow converting to _Bool

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111911 Joseph S. Myers changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jsm28 at gcc dot gnu.org

[Bug c/111059] [11/12/13/14 Regression] ICE: in gimplify_expr, at gimplify.cc:17253

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111059 Joseph S. Myers changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jsm28 at gcc dot gnu.org

[Bug target/113578] Incorrect sign printed for -nan on RISC-V

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113578 --- Comment #2 from Joseph S. Myers --- If a conversion from float to double (for passing in variable arguments) occurs at runtime on RISC-V, that will produce a positive-signed NaN (that's what the RISC-V floating-point instructions do). Cf.

[Bug other/111287] doc: "strict ISO mode" definition is not up-to-date

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111287 --- Comment #3 from Joseph S. Myers --- "even in strict ISO C90 mode" is used, correctly, when referring to C90 mode as the one with the fewest built-in functions; it's talking about __builtin_*, which are valid in all standards modes. "except

[Bug target/113484] Add support for _Float16 type on PowerPC

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113484 --- Comment #1 from Joseph S. Myers --- It would of course be necessary to define the ABI used for _Float16 (and _Complex _Float16) argument passing and return (in each PowerPC ABI for which we support use of this feature).

[Bug c/113455] ROUNDING: IEEE Standard: Missing decimal rounding mode 'nearest, ties away from zero' for decimalxxx datatypes.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113455 --- Comment #3 from Joseph S. Myers --- If you're linking with the version of the DFP arithmetic functions (__bid_a3 etc.) in libdfp rather than the libgcc version - check the link order carefully to make sure the right version is linked in

[Bug c/113455] ROUNDING: IEEE Standard: Missing decimal rounding mode 'nearest, ties away from zero' for decimalxxx datatypes.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113455 --- Comment #1 from Joseph S. Myers --- The decimal rounding mode is set with fe_dec_setround. libdfp provides that function and an fenv.h wrapper with constant definitions including FE_DEC_TONEARESTFROMZERO. Providing that library is outside

[Bug tree-optimization/113379] `MIN == MAX` should be optimzed to `a == b`

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113379 --- Comment #2 from Joseph S. Myers --- Note that some of these aren't valid for floating point in the presence of NaNs.

[Bug rtl-optimization/113098] [14 Regression] LRA ICE building glibc for mips

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113098 Joseph S. Myers changed: What|Removed |Added Status|RESOLVED|REOPENED Last reconfirmed|

[Bug rtl-optimization/113234] missing folding to builtin_isunordered if manual nan comparison is used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113234 --- Comment #1 from Joseph S. Myers --- Note that if flag_signaling_nans, __builtin_isnan should not raise exceptions for signaling NaN argument (bug 66462), but ==, != and __builtin_isunordered should raise exceptions for signaling NaN

[Bug tree-optimization/113189] `(-X * Y) * -X` can be optimized to `(X * Y) * X`

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113189 --- Comment #2 from Joseph S. Myers --- If Y is INT_MIN and X is -1, removing the negations introduces undefined behavior in the first example (-(-1) * INT_MIN * -(-1) is valid, -1 * INT_MIN * -1 has undefined behavior). For floating types,

[Bug middle-end/113130] `abs(a) == b` could be expanded as `(a == b || a == -b)`

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113130 --- Comment #1 from Joseph S. Myers --- Note that the first example (and the suggested one with ABS_EXPR) has undefined behavior for a == INT_MIN, while the second has undefined behavior for c == INT_MIN (and is also not equivalent to the first

[Bug rtl-optimization/113098] New: [14 Regression] LRA ICE building glibc for mips

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113098 Bug ID: 113098 Summary: [14 Regression] LRA ICE building glibc for mips Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal

[Bug rtl-optimization/113097] New: [14 Regression] LRA ICE building glibc for arc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113097 Bug ID: 113097 Summary: [14 Regression] LRA ICE building glibc for arc Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal

[Bug middle-end/112909] New: [14 Regression] glibc -Wuninitialized build failure for i686-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112909 Bug ID: 112909 Summary: [14 Regression] glibc -Wuninitialized build failure for i686-gnu Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug target/112753] New: [14 Regression] unrecognizable insn building glibc for s390x

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112753 Bug ID: 112753 Summary: [14 Regression] unrecognizable insn building glibc for s390x Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords:

[Bug c/107954] Support -std=c23/gnu23 as aliases of -std=c2x/gnu2x

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107954 Joseph S. Myers changed: What|Removed |Added Target Milestone|--- |14.0 Status|NEW

[Bug tree-optimization/112358] New: [14 Regression] glibc -Wstringop-overflow= build failure

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112358 Bug ID: 112358 Summary: [14 Regression] glibc -Wstringop-overflow= build failure Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug target/87281] qsort checking ICE in ia64_reorg building libgo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87281 --- Comment #15 from Joseph S. Myers --- Created attachment 56496 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56496=edit Test that started failing on 20 July 2023 Another instance of this ICE appeared in my glibc bot on 20 July;

[Bug target/87281] [14 Regression] qsort checking ICE in ia64_reorg building libgo

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87281 Joseph S. Myers changed: What|Removed |Added Last reconfirmed|2019-06-14 00:00:00 |2023-11-2 Target Milestone|---

[Bug c/110664] -std=c2x -pedantic-errors pedwarns on _Float128

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110664 Joseph S. Myers changed: What|Removed |Added Target Milestone|--- |14.0 Resolution|---

[Bug middle-end/87403] [Meta-bug] Issues that suggest a new warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403 Bug 87403 depends on bug 65213, which changed state. Bug 65213 Summary: Extend -Wmissing-declarations to variables [i.e. add -Wmissing-variable-declarations] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65213 What|Removed

[Bug c/65213] Extend -Wmissing-declarations to variables [i.e. add -Wmissing-variable-declarations]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65213 Joseph S. Myers changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/106282] [10/11/12/13 Regression] m68k: Problem with thread-local storage and -mcpu=5206 since r9-2326-gede9446c26a929

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106282 Joseph S. Myers changed: What|Removed |Added Target Milestone|--- |10.5 Summary|m68k:

[Bug target/103370] [12/13 Regression] Assembler error building glibc for ColdFire soft-float

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103370 --- Comment #9 from Joseph S. Myers --- The glibc build failure has done away and come back at least once since my previous comment. It came back (I think the most recent time) with commit 4fa25a7eb322f0a003c1eb15680c71ece345e01e Author:

[Bug debug/106746] [13 Regression] '-fcompare-debug' failure (length) with -O2 -fsched2-use-superblocks since r13-2041-g6624ad73064de241

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106746 --- Comment #22 from Joseph S. Myers --- The fix introduced a regression building glibc for ia64-linux-gnu, see bug 108484.

[Bug target/108484] New: [13 Regression] ICE building glibc for ia64 in cselib_subst_to_values, at cselib.cc:2148

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108484 Bug ID: 108484 Summary: [13 Regression] ICE building glibc for ia64 in cselib_subst_to_values, at cselib.cc:2148 Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug c/108375] New: [10/11/12/13 Regression] Some variably modified types not detected as such

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108375 Bug ID: 108375 Summary: [10/11/12/13 Regression] Some variably modified types not detected as such Product: gcc Version: 13.0 Status: UNCONFIRMED Severity:

[Bug c++/107148] [10/11/12/13 Regression] ICE in bot_manip, at cp/tree.cc:3252

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107148 Joseph S. Myers changed: What|Removed |Added CC||jsm28 at gcc dot gnu.org --- Comment

[Bug c/61469] language feature: Support for enum underlying type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61469 Joseph S. Myers changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c/61469] language feature: Support for enum underlying type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61469 Joseph S. Myers changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug c/107314] [13 Regression] New -Wsign-compare since r13-3360-g3b3083a598ca3f4b

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107314 Joseph S. Myers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/107164] No pedantic warning for declaration just referring to a previously-declared enum type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107164 Joseph S. Myers changed: What|Removed |Added Target Milestone|--- |13.0 Resolution|---

[Bug c/36113] fix C enumerators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36113 Joseph S. Myers changed: What|Removed |Added Target Milestone|--- |13.0 Resolution|---

[Bug middle-end/107088] New: [13 Regression] cselib ICE building __trunctfxf2 on ia64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107088 Bug ID: 107088 Summary: [13 Regression] cselib ICE building __trunctfxf2 on ia64 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code

[Bug c++/107080] New: ICE in verify_symtab_nodes using _Float64x with long double

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107080 Bug ID: 107080 Summary: ICE in verify_symtab_nodes using _Float64x with long double Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code

[Bug c/106797] Improvement: diagnose undefined behavior: not all declarations that refer to the same object or function have compatible type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106797 Joseph S. Myers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/21343] [10/11/12/13 Regression] incompatible internal linkage declarations in different scopes not diagnosed

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21343 Joseph S. Myers changed: What|Removed |Added CC||pavel.morozkin at gmail dot com ---

[Bug target/103370] [12/13 Regression] Assembler error building glibc for ColdFire soft-float

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103370 --- Comment #8 from Joseph S. Myers --- This build failure has come back on GCC mainline, some time between commit 3cab897a67af120aa18efa7ddd7ee49b9a29e5dd and 7f5ec900e53f6c7f7c06c641b4fb303ebdc83785.

[Bug c++/106646] [C++23] P2437R1 - Support for #warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106646 --- Comment #1 from Joseph S. Myers --- Enabled for C2x (i.e. stopped -pedantic diagnosing it) with commit d7c3000147c1d8090f66a2baf4623d2c0dfe8eb6 - C++ will presumably want to adjust the diagnostics as well as enabling for relevant C++

[Bug target/103722] [12 Regression] ICE in extract_constrain_insn building glibc for SH4

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103722 Joseph S. Myers changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug lto/106129] [12 Regression] LTO option merging broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106129 Joseph S. Myers changed: What|Removed |Added Last reconfirmed||2022-06-30 Ever confirmed|0

[Bug lto/106129] New: [12/13 Regression] LTO option merging broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106129 Bug ID: 106129 Summary: [12/13 Regression] LTO option merging broken Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug middle-end/105866] [13 Regression] ICE in emit_move_insn building glibc for MIPS

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105866 Joseph S. Myers changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug middle-end/105866] [13 Regression] ICE in emit_move_insn building glibc for MIPS

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105866 Joseph S. Myers changed: What|Removed |Added Version|12.0|13.0 Target Milestone|---

[Bug middle-end/105866] New: [13 Regression] ICE in emit_move_insn building glibc for MIPS

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105866 Bug ID: 105866 Summary: [13 Regression] ICE in emit_move_insn building glibc for MIPS Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords:

[Bug libstdc++/105671] [11/12/13 Regression] Unexplained "undefined reference" error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105671 Joseph S. Myers changed: What|Removed |Added Summary|Unexplained "undefined |[11/12/13 Regression]

[Bug libgcc/105669] DFP to HF (_Float16) conversions use incorrect rounding

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105669 Joseph S. Myers changed: What|Removed |Added Last reconfirmed||2022-05-20 Ever confirmed|0

[Bug preprocessor/105412] New: [10/11/12 Regression] Missing phony target with -MP for first include when compiling from stdin

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105412 Bug ID: 105412 Summary: [10/11/12 Regression] Missing phony target with -MP for first include when compiling from stdin Product: gcc Version: 12.0 Status: UNCONFIRMED

[Bug c/105180] [9/10/11/12 Regression] K style definition does not evaluate array size

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105180 Joseph S. Myers changed: What|Removed |Added Summary|K style definition does |[9/10/11/12 Regression] K

[Bug target/104829] [12 Regression] Pure 32-bit PowerPC build broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104829 --- Comment #9 from Joseph S. Myers --- Created attachment 52598 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52598=edit generated assembly Assembly output attached.

[Bug target/104829] [12 Regression] Pure 32-bit PowerPC build broken

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104829 --- Comment #8 from Joseph S. Myers --- Created attachment 52597 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52597=edit preprocessed source Preprocessed source attached.

[Bug preprocessor/104147] [9/10/11/12 Regression] C preprocessor may remove the standard required whitespace between the preprocessing tokens

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104147 Joseph S. Myers changed: What|Removed |Added Known to fail||3.2.3 Known to work|

[Bug target/103722] New: [12 Regression] ICE in extract_constrain_insn building glibc for SH4

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103722 Bug ID: 103722 Summary: [12 Regression] ICE in extract_constrain_insn building glibc for SH4 Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords:

[Bug c++/19992] -fhosted/-ffreestanding for C++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19992 Joseph S. Myers changed: What|Removed |Added Known to fail||4.2.0 Target Milestone|---

[Bug target/103370] [12 Regression] Assembler error building glibc for ColdFire soft-float

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103370 --- Comment #4 from Joseph S. Myers --- It seems this glibc build failure disappeared between commit b880d1514c1e3dd75a6ea311a5cc956742bd713c and commit 8e836af61b7027c0819da62c12a8d18b7c46f3fc. (Not verified that the GCC change was what's

[Bug target/103370] New: [12 Regression] Assembler error building glibc for ColdFire soft-float

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103370 Bug ID: 103370 Summary: [12 Regression] Assembler error building glibc for ColdFire soft-float Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords:

[Bug c/103031] [12 Regression] Missing static initializer folding with -frounding-math

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103031 Joseph S. Myers changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug middle-end/103031] New: [12 Regression] Missing static initializer folding with -frounding-math

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103031 Bug ID: 103031 Summary: [12 Regression] Missing static initializer folding with -frounding-math Product: gcc Version: 12.0 Status: UNCONFIRMED Severity:

[Bug c/88727] Diagnostics improvement: Detection of undefined behaviour. Incomplete type in tenative definition with internal linkage. [-Wtentative-definition-incomplete-type]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88727 Joseph S. Myers changed: What|Removed |Added CC||pavel.morozkin at gmail dot com ---

[Bug c/102821] Tentative definition of variable with internal linkage has incomplete non-array type: missing diagnostics

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102821 Joseph S. Myers changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW

  1   2   >