https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107062
--- Comment #5 from Francois-Xavier Coudert ---
Fixed on trunk:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=31d7c8bc2630e1b5a35ccce97ac862c4920ba582
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107062
Francois-Xavier Coudert changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128
Bug ID: 107128
Summary: armhf: floatn-common.h:214:9: error: multiple types in
one declaration
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
Eric Botcazou changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128
--- Comment #2 from Mathieu Malaterre ---
> Gcc 13 requires some (older) glibc headers to be fixed up .
I could not reproduce it under my Debian amd64/chroot. I'll check with doko@d.o
then.
Sorry for the noise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107119
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #10 from Richard Earnshaw ---
That sounds broadly sensible. One optimization might be to check if the
exception trapping is already enabled, then you can skip the read/set/restore
dance entirely in that case. That might be more effi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107110
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107094
Martin Liška changed:
What|Removed |Added
CC||doko at gcc dot gnu.org
--- Comment #2 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107112
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
Resolu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107120
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2022-10-03
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107109
Martin Liška changed:
What|Removed |Added
Summary|ICE on valid code at -O1 on |[13 Regression] ICE on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
--- Comment #4 from Martin Liška ---
Yes, the change landed to upstream as 3776db9a4fd2080d23d6a5f52e405eea44558761
and thus should be part of what I merged in r13-2269-g600413c4f3d703.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #4 from Martin Liška ---
> Yes, the change landed to upstream as 3776db9a4fd2080d23d6a5f52e405eea44558761
> and thus should be part of what I merged in r13-2269-g600413c4f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
--- Comment #6 from Martin Liška ---
(In reply to r...@cebitec.uni-bielefeld.de from comment #5)
> > --- Comment #4 from Martin Liška ---
> > Yes, the change landed to upstream as
> > 3776db9a4fd2080d23d6a5f52e405eea44558761
> > and thus shoul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107126
--- Comment #7 from Jonathan Wakely ---
https://wg21.link/cwg1435 introduced the wording that allows this (which can
still be seen in the context for the [class.dtor] changes in CWG 2337):
"in a declaration at namespace scope or in a friend dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127
--- Comment #2 from Martin Liška ---
Reduced test-case:
$ cat x.i
int *loopy_kernel_expr9;
void loopy_kernel() {
_Complex var_e9_11;
double var_e9_15;
;
;
double var_e9_6;
;
loopy_kernel_expr9[0] /
var_e9_6 *
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
--- Comment #7 from Eric Botcazou ---
> I mean to submit a patch cherry-picking that one shortly.
OK, thanks in advance.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107000
--- Comment #18 from Mikael Morin ---
(In reply to anlauf from comment #14)
>
> We could walk through the elements of each array passed to reduce_binary
> and check the types of the elements there, or do this check in a somewhat
> more clever w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128
--- Comment #3 from Mathieu Malaterre ---
> some (older) glibc
By older what do you mean exactly ? It seems my system provides glibc 2.35:
malat@amdahl /tmp % apt-cache policy libc6-dev
libc6-dev:
Installed: 2.35-1
Candidate: 2.35-1
Vers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107128
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107000
--- Comment #19 from Mikael Morin ---
(In reply to anlauf from comment #17)
> (In reply to anlauf from comment #16)
> > Created attachment 53651 [details]
> > Revised patch
>
> Unfortunately this regresses on gfortran.dg/pr91552.f90, e.g.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107129
Bug ID: 107129
Summary: [13 Regression] False positive -Wstringop-overflow
warning with -O2 or -O3
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107129
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
std
gcc version 13.0.0 20221003 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107130
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2022-10-03
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107130
--- Comment #2 from Zdenek Sojka ---
(In reply to Martin Liška from comment #1)
> Started with r13-2900-g001c60ccfeaf9a48.
Nice, so ffs() with a propagated constant argument now does a popcount()
instead?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107130
--- Comment #3 from Martin Liška ---
> Nice, so ffs() with a propagated constant argument now does a popcount()
> instead?
It should not. The problem is op_cfn_popcount is shared by both popcount and
ffs, but the newly added transformation is v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107130
Martin Liška changed:
What|Removed |Added
Target Milestone|--- |13.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106949
--- Comment #2 from Anton Fedorov ---
Created attachment 53654
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53654&action=edit
potential fix
I checked with the HEAD (43faf3e5445b571731e52faa1be085ecd0a09323) and the
issue is still there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
Rainer Orth changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107119
Maxim Kuvyrkov changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
cxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r13-3023-20221003092645-g31d7c8bc263-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.0 20221003 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107118
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96830
--- Comment #10 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #9)
> Reduced to show Clang's confusion: https://godbolt.org/z/E1Kq4Gfed
Reported as https://github.com/llvm/llvm-project/issues/58124
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
--- Comment #9 from Martin Liška ---
I can't see the commit in git history, have you pushed the revision?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
Martin Liška changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107109
--- Comment #3 from CVS Commits ---
The master branch has been updated by Andrew Macleod :
https://gcc.gnu.org/g:f41d1b39a6443fad38c36af34b1baa384954ca80
commit r13-3031-gf41d1b39a6443fad38c36af34b1baa384954ca80
Author: Andrew MacLeod
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107132
Bug ID: 107132
Summary: a temporary object with an x-value is not destroyed
and is bound to a variable
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107109
Andrew Macleod changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107126
Jason Merrill changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
--- Comment #11 from CVS Commits ---
The master branch has been updated by Rainer Orth :
https://gcc.gnu.org/g:77d0627c244f7520bf74ec9cf2a8b69c32b6d30d
commit r13-3033-g77d0627c244f7520bf74ec9cf2a8b69c32b6d30d
Author: Rainer Orth
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
--- Comment #12 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #9 from Martin Liška ---
> I can't see the commit in git history, have you pushed the revision?
I hadn't. Seems I shouldn't work on a holiday ;-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105531
Rainer Orth changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f1b51f68f8ac6c63e352dda8599aed01634212de
commit r13-3034-gf1b51f68f8ac6c63e352dda8599aed01634212de
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #8 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:18f176d0b25591e2880bc5ef453ce0834f9e0e2a
commit r13-3037-g18f176d0b25591e2880bc5ef453ce0834f9e0e2a
Author: Arsen ArsenoviÄ
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106953
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:6885e7e4eef65c657cd8baa0f5e7ebe7231ac984
commit r13-3038-g6885e7e4eef65c657cd8baa0f5e7ebe7231ac984
Author: Arsen ArsenoviÄ
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:25ebfdb774c0e8cc6c55e02644ee2cb157ce29d7
commit r13-3040-g25ebfdb774c0e8cc6c55e02644ee2cb157ce29d7
Author: Jonathan Wakely
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:25ebfdb774c0e8cc6c55e02644ee2cb157ce29d7
commit r13-3040-g25ebfdb774c0e8cc6c55e02644ee2cb157ce29d7
Author: Jonathan Wakely
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #9 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:46eb2860942a29b40822570cb6625620f69ed30e
commit r13-3039-g46eb2860942a29b40822570cb6625620f69ed30e
Author: Arsen ArsenoviÄ
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #12 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:7cc9022f8d5c5cc02cc4f8af2f27184a81536fcf
commit r13-3043-g7cc9022f8d5c5cc02cc4f8af2f27184a81536fcf
Author: Arsen ArsenoviÄ
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107131
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107104
Hannes Hauswedell changed:
What|Removed |Added
CC||h2+bugs at fsfe dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19992
Bug 19992 depends on bug 103626, which changed state.
Bug 103626 Summary: _GLIBCXX_HOSTED should respect -ffreestanding
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
What|Removed |Added
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106953
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106749
Bug 106749 depends on bug 106953, which changed state.
Bug 106953 Summary: C++23 add new headers for freestanding
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106953
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107104
--- Comment #2 from Jonathan Wakely ---
(In reply to Hannes Hauswedell from comment #1)
> It seems that __builtin_constant_p does not indicate whether something *can
> be* a constant but whether *it is* a constant.
Correct.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107059
--- Comment #30 from seurer at gcc dot gnu.org ---
Any more progress on this? Builds still fail on powerpc64 LE.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107059
--- Comment #31 from Jakub Jelinek ---
Still waiting for review.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107130
Aldy Hernandez changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |aldyh at gcc dot gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107130
--- Comment #5 from Aldy Hernandez ---
Created attachment 53656
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53656&action=edit
untested patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107114
--- Comment #1 from Andrew Macleod ---
Looks like something in the change is causing the loop analysis to not be able
to count the iterations.
> Analyzing # of iterations of loop 1
> exit condition [1, + , 1] != 0
> bounds on difference of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #37 from H. Peter Anvin ---
One would assume that there would be __foo__ aliases for the attribute names
like all the other ones.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56314
--- Comment #6 from H. Peter Anvin ---
Unfortunately that's not really possible given the way the way the level does
runtime patching (which isn't going to change, sorry.) At the very least we
would need a *lot* more compiler support to give LTO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=772
--- Comment #23 from Andrew Pinski ---
Part of the C++ front-end issues was fixed with
r13-3046-gc823366fdb9069a54a37a3b18b65a4fa69feabfd . I didn't look to see if
all were fixed though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107133
Bug ID: 107133
Summary: _GLIBCXX_USE_C99_STDINT_TR1 macro is not defined for
--disable-hosted-libstdcxx without libc
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107133
--- Comment #1 from cqwrteur ---
cstdint does not do anything since the macro is not defined
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107133
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104605
--- Comment #5 from Jonathan Wakely ---
*** Bug 107133 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104605
--- Comment #6 from Jonathan Wakely ---
(In reply to cqwrteur from comment #0)
> Also stdint.h in GCC is not correctly defined without -ffreestanding flag.
You can just use -ffreestanding now, and you'll get GCC's own stdint header.
-languages=c,c++ --enable-multilib
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20221003 (experimental) (GCC)
x86_64-elf-g++ -c b.cc -std=c++23
In file included from
/home/cqwrteur/toolchains/native/x86_64-elf/x86_64-elf/include/c++/13.0.0/cstdint:41
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104605
--- Comment #7 from Jonathan Wakely ---
Created attachment 53657
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53657&action=edit
Use predefined macros to define freestanding
I have this patch locally, but I don't think the changes are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107134
--- Comment #1 from Jonathan Wakely ---
With current trunk, you need to use -ffreestanding if you are compiling for
freestanding.
--without-headers --disable-hosted-libstdcxx says to build a freestanding
library, that doesn't tell the compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107114
--- Comment #2 from Jeffrey A. Law ---
Which is just uber-weird. The change in question removes a little subloop
which becomes unreachable. Why that would cause us to be unable to analyze the
remaining key loop for the IV's range is a complete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107135
Bug ID: 107135
Summary: array::at() method should not be in for
freestanding C++
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107134
--- Comment #2 from Jonathan Wakely ---
Although we could do:
#if ! _GLIBCXX_HOSTED
#include
#else
#include_next
#endif
to make it work.
: plugins
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
I've just been having a go at compiling the new linux-6.0 kernel
with a recent trunk gcc. I get
/home/dcb/gcc/results.20221003/lib/gcc/x86_64-pc-linux-gnu/13.0.0/p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107136
David Binderman changed:
What|Removed |Added
CC||ppalka at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107114
--- Comment #3 from Andrew Macleod ---
yeah, we just invoke the loop analyzer and pick up what it tells us. From VRP2
point of view, it is just not getting the info supplied from the loop
optimizer.
I see dom3 removes some code and I see
< f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107120
Arseny Solokha changed:
What|Removed |Added
CC||asolokha at gmx dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107136
Andrew Pinski changed:
What|Removed |Added
Version|12.0|13.0
--- Comment #2 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107136
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Component|plugins
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107114
--- Comment #4 from Jeffrey A. Law ---
I'll double check, but IIRC we throw away the loop structures at the end of DOM
and they're supposed to be rebuilt (which appears to be happening as we
re-construct LCSSA).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107136
--- Comment #3 from Andrew Pinski ---
This is most likely the fix but I don't have time to test it right now"
diff --git a/gcc/cp/Make-lang.in b/gcc/cp/Make-lang.in
index 38d8eeed1f0..aa84d6827be 100644
--- a/gcc/cp/Make-lang.in
+++ b/gcc/cp/Mak
$ cp ./gcc/cp/cp-trait.def
../results.20221003/lib/gcc/x86_64-pc-linux-gnu/13.0.0/plugin/include/cp/
[/home/dcb/gcc/trunk.git] $
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104605
--- Comment #8 from cqwrteur ---
(In reply to Jonathan Wakely from comment #7)
> Created attachment 53657 [details]
> Use predefined macros to define freestanding
>
> I have this patch locally, but I don't think the changes are
> actually nec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107123
--- Comment #1 from Andrew Pinski ---
Yes GCC does not do deduction on the vector size attribute currently.
This part of the extension is not documented one way or the other either
because nobody thought of this right now.
One easy way around t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107123
Andrew Pinski changed:
What|Removed |Added
Keywords||documentation
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107123
--- Comment #2 from milasudril at gmail dot com ---
> It would be nice to standardized the vector attribute.
Good features to have:
constexpr std::size (and also std::ssize)
template
inline constexpr std::is_simd_type_v = ...;
namespace std {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107135
Arsen Arsenović changed:
What|Removed |Added
CC||arsen at aarsen dot me
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107131
--- Comment #2 from Andrew Pinski ---
Note there is a missed optimization here (unrelated to the wrong code):
_32 = o_13(D) == 0;
_35 = (long int) _32;
_36 = -_35;
_109 = (long long unsigned int) _36;
_102 = _109 > 10439075533421201520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107000
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Attachment #53651|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104605
--- Comment #9 from Jonathan Wakely ---
is freestanding, but isn't listed as being required for
freestanding C++. That doesn't mean we can't provide it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107135
--- Comment #2 from Jonathan Wakely ---
We should make it terminate though, there's no definition of
__throw_out_of_range_fmt.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107137
Bug ID: 107137
Summary: (unsigned)-(int)(bool_var) should be optimized to
-(unsigned)bool_var
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: missed-o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107131
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> Let me file that as a seperate bug.
Created PR 107137.
1 - 100 of 159 matches
Mail list logo
