https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99422
Bug ID: 99422
Summary: [11 Regression] ICE in extract_constrain_insn building
glibc pthread_create
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ice-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100184
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44677
Joseph S. Myers changed:
What|Removed |Added
CC||eyalroz1 at gmx dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97602
Bug ID: 97602
Summary: #line overflow check incomplete
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: accepts-invalid
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97604
Bug ID: 97604
Summary: Bad digit separators accepted in pp-numbers
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97635
Bug ID: 97635
Summary: binary-to-DFP conversions incorrect
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97635
--- Comment #1 from Joseph S. Myers ---
With some analysis of the worst cases (for every possible pair of source and
target exponents) using continued fractions, it would also be possible to
determine a single precision value that is always corre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97683
Bug ID: 97683
Summary: [11 Regression] nios2 assembler branch offset errors
building glibc
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: assemble-fai
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97882
Joseph S. Myers changed:
What|Removed |Added
Last reconfirmed||2020-11-17
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95630
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97602
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82359
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100353
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83873
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97604
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100792
Joseph S. Myers changed:
What|Removed |Added
Version|tree-ssa|12.0
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101170
Bug ID: 101170
Summary: [12 Regression] ICE in df_ref_record building libgomp
for ColdFire
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-vali
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101212
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23144
Joseph S. Myers changed:
What|Removed |Added
CC||muecker at gwdg dot de
--- Comment #27
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: nor
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
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.
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: Ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106282
Joseph S. Myers changed:
What|Removed |Added
Target Milestone|--- |10.5
Summary|m68k: Problem
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&action=edit
preprocessed source
Preprocessed source attached.
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&action=edit
generated assembly
Assembly output attached.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105180
Joseph S. Myers changed:
What|Removed |Added
Summary|K&R style definition does |[9/10/11/12 Regression] K&R
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
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++ version
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.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21343
Joseph S. Myers changed:
What|Removed |Added
CC||pavel.morozkin at gmail dot com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106797
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36113
Joseph S. Myers changed:
What|Removed |Added
Target Milestone|--- |13.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107164
Joseph S. Myers changed:
What|Removed |Added
Target Milestone|--- |13.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107314
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
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|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103031
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
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: assembl
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 rele
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|---
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: ice-on-va
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102133
Bug ID: 102133
Summary: [12 Regression] ICE in set_rtl building libgcc
__muldc3 for 32-bit SPARC
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102127
Joseph S. Myers changed:
What|Removed |Added
CC||jsm28 at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102630
Bug ID: 102630
Summary: [12 Regression] Spurious -Warray-bounds with named
address space
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: rejects-valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102821
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88727
Joseph S. Myers changed:
What|Removed |Added
CC||pavel.morozkin at gmail dot com
--- Co
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: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61469
Joseph S. Myers changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61469
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105671
Joseph S. Myers changed:
What|Removed |Added
Summary|Unexplained "undefined |[11/12/13 Regression]
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: ice-on-valid-cod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105866
Joseph S. Myers changed:
What|Removed |Added
Version|12.0|13.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105866
Joseph S. Myers changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
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: lto
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103722
Joseph S. Myers changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
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 DEC_EV
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113776
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113776
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113825
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
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 type
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 needs
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 n
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 independent
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.
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 it
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 get
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
fminimum/fmaximum
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 *old
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114266
Joseph S. Myers changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
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.
T
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 unde
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 _BitInt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112571
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
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 t
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
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 sharin
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 (
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 certain
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65213
Joseph S. Myers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110664
Joseph S. Myers changed:
What|Removed |Added
Target Milestone|--- |14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116130
--- Comment #12 from Joseph S. Myers ---
N3096 is a very old draft with lots of mistakes. Use N3220 instead (it has no
technical changes relative to C23, though it's also missing many late editorial
fixes required by ISO).
Composite types for c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116199
Bug ID: 116199
Summary: [15 Regression] reload ICE building glibc for m68k
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116244
Bug ID: 116244
Summary: [15 Regression] reload ICE building libstdc++ for
coldfire
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796
--- Comment #13 from Joseph S. Myers ---
Everything available with __attribute__ is also available with [[]];
__attribute__((foo)) is [[gnu::foo]]. You *do* need to ensure that the
[[gnu::foo]] is placed in the right syntactic position for the e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108796
--- Comment #15 from Joseph S. Myers ---
The [[]] syntax is supported in C from GCC 10 onwards (in C++ in older versions
as well). What's new in GCC 14 is that you can use it with :: in pre-C23 modes
(with previous versions you needed -std=gnu2x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112358
--- Comment #8 from Joseph S. Myers ---
If it's a false positive, it's reasonable to work around in glibc using the
libc-diag.h macros (DIAG_PUSH_NEEDS_COMMENT / DIAG_IGNORE_NEEDS_COMMENT /
DIAG_POP_NEEDS_COMMENT) - but that would need an approp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116631
--- Comment #2 from Joseph S. Myers ---
The specification for underspecified declarations (auto and constexpr) says "if
anywhere within the sequence of tokens making up the declaration identifiers
that are not ordinary are declared, the behavior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
--- Comment #5 from Joseph S. Myers ---
It's doubtful that this is a bug. You could define __builtin_choose_expr so the
unselected operand only needs to be a balanced token sequence (with no commas
unless nested inside () [] {}), but it's less cl
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 speci
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 consistent
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 pr
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).
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 shal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114869
Joseph S. Myers changed:
What|Removed |Added
Last reconfirmed||2024-04-29
CC|
1 - 100 of 225 matches
Mail list logo