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
-valid-code
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: jason at gcc dot gnu.org
Target Milestone: ---
Target: m68k-linux-gnu
Created
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
: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
Target Milestone: ---
variably_modified_type_p fails to detect an array type as variably modified if
the array and its element type are of constant size
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: aoliva at gcc dot gnu.org
Target Milestone: ---
Target: ia64
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
||r9-2326-gede9446c26a929
CC||jsm28 at gcc dot gnu.org
--- Comment #2 from Joseph S. Myers ---
My glibc bot has been failing for ColdFire since some time between commits
79d38dd46e6b07e5a90ab25df1438eb0918eb475 and
f56d48b2471c388401174029324e1f4c4b84fcdb
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
Severity: normal
Priority: P3
Component: preprocessor
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
Target Milestone: ---
When generating dependencies with -M -MP, the phony target for the first
included header
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|---
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
Target: x86_64-* i?86-* ia64-*
Compiling the
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: stefansf at linux dot ibm.com
Target Milestone: ---
Target: ia64-*-*
Created attachment
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
: assemble-failure
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
Target: m68k*-*-*
Created
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|---
-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: vmakarov at gcc dot gnu.org
Target Milestone: ---
Target: sh4*-*-*
Created
-on-valid-code
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: liuhongt at gcc dot gnu.org
Target Milestone: ---
Target: sparc
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
-valid
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: msebor at gcc dot gnu.org
Target Milestone: ---
Target: x86_64-*-*
Created attachment
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
: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
One of the recent fixes to avoid inappropriate constant folding with
|unassigned at gcc dot gnu.org |jsm28 at gcc dot gnu.org
--- Comment #10 from Joseph S. Myers ---
I'm working on implementing this C2x feature for GCC 13.
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
ssion]
|reference" error|Unexplained "undefined
||reference" error
CC| |jsm28 at gcc dot gnu.org
Component|c++ |libstdc++
-code
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: roger at nextmovesoftware dot com
Target Milestone: ---
Target: mips*-*-*
Created
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|---
: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
The LTO merging of options from different input files was broken by:
commit 227a2ecf663d69972b851f51f1934d18927b62cd
Author: Martin
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
|unassigned at gcc dot gnu.org |jsm28 at gcc dot gnu.org
Last reconfirmed||2024-02-07
Ever confirmed|0 |1
--- Comment #3 from Joseph S. Myers ---
Testing a patch.
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
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: law at gcc dot gnu.org
Target Milestone: ---
Target: m68k-*-*
Created attachment 58807
--> ht
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: law at gcc dot gnu.org
Target Milestone: ---
Target: m68k-*-*
Created attachment
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|
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.
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 construc
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115109
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
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 a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115311
--- Comment #1 from Joseph S. Myers ---
This definitely wouldn't work for glibc; we freely use -fno-builtin- when
e.g. aliasing double and long double functions when the formats are the same,
where GCC gives an error if it has the functions as b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115307
--- Comment #7 from Joseph S. Myers ---
Note the difference between __builtin_isinf (C standard semantics, returns
unspecified nonzero value for an infinity) and __builtin_isinf_sign (stricter
semantics returning 1 for +Inf and -1 for -Inf).
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|---
501 - 600 of 747 matches
Mail list logo
