https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110292
--- Comment #5 from Yann Droneaud ---
Hi,
Thanks a lot for the quick analysis of my issue.
(In reply to Andrew Pinski from comment #4)
> Note -Wstrict-aliasing=1 actually does warn:
OK, and -Wall enables -Wstrict-aliasing which defaults to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110294
--- Comment #1 from CTC <19373742 at buaa dot edu.cn> ---
Created attachment 55353
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55353=edit
The compiler output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110294
Bug ID: 110294
Summary: Segmentation fault with '-O3 -fno-dce
-fno-toplevel-reorder -fno-tree-dce -fno-tree-pta
-fno-tree-sink -ftoplevel-reorder'
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110293
--- Comment #2 from Andrew Pinski ---
Some more generally for the ==/!= cases for CSTs:
x == (x == CST) -> CST == 0 ? 0 : (CST == 1 ? (x==0||x==1) : x != 0)
x == (x != CST) -> CST == 1 ? 0 : (CST == 0 ? (x==0||x==1) : x != 1)
x != (x == CST) ->
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110293
--- Comment #1 from Andrew Pinski ---
Here are the signed versions of />=:
`s < (s != 0)` is `s < 0`
`s <= (s != 0)` is `s <= 1`
`s > (s != 0)` is `s > 1`
`s >= (s != 0)` is `s >= 0`
`s < (s == 0)` is `s <= 0`
`s <= (s == 0)` is `s <= 0`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110265
--- Comment #2 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:d0cf0c6c8449009697ad29dd7cb60e7f655628f2
commit r14-1899-gd0cf0c6c8449009697ad29dd7cb60e7f655628f2
Author: Pan Li
Date: Fri Jun 16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110219
--- Comment #4 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> Dup of bug 110266.
>
> *** This bug has been marked as a duplicate of bug 110266 ***
I should say that bug has a better testcase than one which you need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110266
Andrew Pinski changed:
What|Removed |Added
CC||zsojka at seznam dot cz
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110219
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110264
--- Comment #4 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:dd6e1cbac8682106c5167c105f2807014288b852
commit r14-1898-gdd6e1cbac8682106c5167c105f2807014288b852
Author: Juzhe-Zhong
Date: Fri Jun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110293
Bug ID: 110293
Summary: Some `A CMP (A NEEQ 0)` is not simplified in some
cases
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110228
--- Comment #11 from Andrew Pinski ---
>From the duplicate bug report analysis:
# RANGE [irange] short int [0, 1] NONZERO 0x1
# n_lsm.35_15 = PHI <_10(9), n_lsm.35_45(12)>
...
# RANGE [irange] short int [0, 1] NONZERO 0x1
# n_lsm.35_45
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110286
--- Comment #3 from Andrew Pinski ---
In this case we have:
# RANGE [irange] short int [0, 1] NONZERO 0x1
# n_lsm.35_15 = PHI <_10(9), n_lsm.35_45(12)>
...
# RANGE [irange] short int [0, 1] NONZERO 0x1
# n_lsm.35_45 = PHI
# RANGE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110228
Andrew Pinski changed:
What|Removed |Added
CC||shaohua.li at inf dot ethz.ch
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110286
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110286
--- Comment #1 from Andrew Pinski ---
phiopt match-simplify trying:
n_lsm_flag.36_58 != 0 ? n_lsm.35_15 : 1
Matching expression match.pd:1990, gimple-match-5.cc:23
Matching expression match.pd:1990, gimple-match-5.cc:23
Matching
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54089
--- Comment #76 from Oleg Endo ---
(In reply to Alexander Klepikov from comment #75)
> I found that patch incorrectly works when '-O0 -fmove-loop-invariants' flags
> are set. Stock loop optimization passes do not run when '-O0' is specified
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110280
--- Comment #4 from Andrew Pinski ---
(gdb) p debug_gimple_stmt(stmt)
_41 = [vec_unpack_lo_expr] _40;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110280
--- Comment #3 from Andrew Pinski ---
#6 0x0087710b in const_unop (code=VEC_UNPACK_LO_EXPR, type=, arg0=) at ../../gcc/fold-const.cc:1954
1954gcc_assert (known_eq (out_nelts, TYPE_VECTOR_SUBPARTS (type)));
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110285
David Malcolm changed:
What|Removed |Added
Summary|-Wanalyzer-infinite-recursi |-Wanalyzer-infinite-recursi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110292
Andrew Pinski changed:
What|Removed |Added
Resolution|WONTFIX |INVALID
--- Comment #4 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110292
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110292
--- Comment #2 from Andrew Pinski ---
aliasing violations are known not to be warned about nor have a runtime
sanitizer either.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110283
--- Comment #2 from Andrew Pinski ---
As an aside, Eigen has some maybe wrong code in it:
```
# 55 "../../eigen-3.3.4/Eigen/src/Core/arch/SSE/PacketMath.h" 3 4
typedef __m128 Packet4f;
typedef __m128i Packet4i;
typedef __m128d Packet2d;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110292
Yann Droneaud changed:
What|Removed |Added
CC||yann at droneaud dot fr
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110292
Bug ID: 110292
Summary: undefined value due to strict aliasing without warning
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110006
waffl3x changed:
What|Removed |Added
CC||waffl3x at protonmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110271
--- Comment #7 from Sergei Trofimovich ---
I confirm the fix also fixes pycryptodome-3.17.0 package build. Thank you!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110291
--- Comment #1 from waffl3x ---
I opened Bug 110006 and forgot to check before submitting, looking over at it,
I'm pretty sure it's the same bug, and if not, then probably related.
https://godbolt.org/z/7zoWfG4Ws I checked their reproduction
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110291
Bug ID: 110291
Summary: [11.1 Regression] constraint on friend operator
template causes bizarre duplication of RHS template
parameter that is passed to the requires expression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109541
--- Comment #20 from CVS Commits ---
The releases/gcc-13 branch has been updated by Vladimir Makarov
:
https://gcc.gnu.org/g:5568d224f2e179b8e91a90fa4fba10bd8a7f963d
commit r13-7451-g5568d224f2e179b8e91a90fa4fba10bd8a7f963d
Author: Vladimir
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92887
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110290
--- Comment #1 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #0)
> It appears that there never was such a restriction in the standard.
There actually was a restriction in F2003, mentioned by Tobias in pr49802#c1:
C528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92178
--- Comment #14 from anlauf at gcc dot gnu.org ---
I looked at cases with character arguments, and it appears that there is a
general issue with (lack or improper) generation of temporaries. Consider:
program p
implicit none
character(4),
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110290
Bug ID: 110290
Summary: Assumed-length character dummy with VALUE attribute
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110271
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110289
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79173
--- Comment #22 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:2b4e0415ad664cdb3ce87d1f7eee5ca26911a05b
commit r14-1896-g2b4e0415ad664cdb3ce87d1f7eee5ca26911a05b
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110271
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:5b67116a85298bbe358b036d34ad23119cebbdac
commit r14-1895-g5b67116a85298bbe358b036d34ad23119cebbdac
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
--- Comment #6 from Alexander Monakov ---
Huh? Just compile the supplied testcases without avx512, you'll see proper
stack realignment.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107900
Paul Thomas changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
--- Comment #5 from H.J. Lu ---
GCC doesn't align stack for Windows. As a workaround, one can pass
-muse-unaligned-vector-move to newer assembler.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110288
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110276
--- Comment #3 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://gcc.gnu.org/pipermail/gcc-patches/2023-June/622019.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772
Bug 86772 depends on bug 86793, which changed state.
Bug 86793 Summary: mips port needs updating for CVE-2017-5753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86793
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86793
Richard Earnshaw changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110287
--- Comment #2 from Jan Hubicka ---
With patch in PR110289 to optimize the std::max int MAX_EXPR and the throw
commented out I get:
size_type std::vector >::_M_check_len
(const struct vector * const this, size_type __n, const char * __s)
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110289
--- Comment #2 from Jan Hubicka ---
This patch fixes the problem
diff --git a/gcc/passes.def b/gcc/passes.def
index c9a8f19747b..faa5208b26b 100644
--- a/gcc/passes.def
+++ b/gcc/passes.def
@@ -88,6 +88,8 @@ along with GCC; see the file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31985
--- Comment #4 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:95020d33ad6991fe4fbdccf70e7133116cac68f4
commit r14-1892-g95020d33ad6991fe4fbdccf70e7133116cac68f4
Author: Roger Sayle
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110215
--- Comment #5 from CVS Commits ---
The master branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:154c69039571c66b3a6d16ecfa9e6ff22942f59f
commit r14-1891-g154c69039571c66b3a6d16ecfa9e6ff22942f59f
Author: Vladimir N. Makarov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110289
--- Comment #1 from Jan Hubicka ---
This is caused by the way libstdc++ defines max:
constexpr
inline const _Tp&
max(const _Tp& __a, const _Tp& __b)
{
if (__a < __b)
return __b;
return __a;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105617
--- Comment #21 from Michael_S ---
(In reply to Mason from comment #20)
> Doh! You're right.
> I come from a background where overlapping/aliasing inputs are heresy,
> thus got blindsided :(
>
> This would be the optimal code, right?
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110289
Bug ID: 110289
Summary: Phiprop may be good idea in early opts
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110287
--- Comment #1 from Jan Hubicka ---
Another problem is:
D.27747 = _8;
if (__n.3_2 > _8)
goto ; [34.00%]
else
goto ; [66.00%]
[local count: 364926196]:
[local count: 1073312330]:
# _18 = PHI <(4), &__n(5)>
_3 = *_18;
d program
Compiler Explorer example: https://godbolt.org/z/Evrnose5o
The same program works in gfortran 10.4, crashes in 11+, including trunk (GNU
Fortran
(Compiler-Explorer-Build-gcc-7ff793415f55fa9a92f348fecb8c75ac8acc8b87-binutils-2.40)
14.0.0 20230616 (experimental)).
A minimum of two elem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110287
Bug ID: 110287
Summary: _M_check_len is expensive
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109849
--- Comment #14 from Jan Hubicka ---
One interesting situation is:
void std::vector >::push_back (struct
vector * const this, const struct value_type & __x)
{
struct __normal_iterator D.27894;
struct pair * _1;
struct pair * _2;
struct
--disable-multilib --disable-bootstrap
--enable-languages=c,c++
--prefix=/zdata/shaoli/compilers/ccbuilder-compilers/gcc-27612ce352921d74086102d9ad4d3e011923f837
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230616 (experimental) (GCC)
$
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110285
--- Comment #3 from Ariel Cabello Mateos <080ariel at gmail dot com> ---
Created attachment 55349
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55349=edit
Preprocessed source of test2.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110285
--- Comment #2 from Ariel Cabello Mateos <080ariel at gmail dot com> ---
Created attachment 55348
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55348=edit
test2.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110285
--- Comment #1 from Ariel Cabello Mateos <080ariel at gmail dot com> ---
Created attachment 55347
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55347=edit
test1.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110285
Bug ID: 110285
Summary: -Wanalyzer-infinite-loop false positive.
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54089
--- Comment #75 from Alexander Klepikov
---
I found that patch incorrectly works when '-O0 -fmove-loop-invariants' flags
are set. Stock loop optimization passes do not run when '-O0' is specified
desipte '-fmove-loop-invariants' is set. I'll do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110104
--- Comment #4 from Mason ---
I confirm that trunk now emits the same code for testcase1 and testcase2.
Thanks Jakub and Roger, great work!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110276
Martin Jambor changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110284
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |14.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110284
Bug ID: 110284
Summary: [14 Regression] Bootstrap failures with m2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110062
--- Comment #6 from Richard Biener ---
Btw, we would also be able to vectorize just the red and green channel:
t.c:18:27: note: * Analysis succeeded with vector mode V4SF
t.c:18:27: note: SLPing BB part
t.c:18:27: note: Costing subgraph:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110283
--- Comment #1 from Pilar Latiesa ---
Created attachment 55345
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55345=edit
preprocessed code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110283
Bug ID: 110283
Summary: Bogus Warray-bounds
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104024
--- Comment #6 from Kewen Lin ---
(In reply to Martin Jambor from comment #5)
> I have just seen a similar ICE with a ppc64le cross-compiler. Running
>
> ~/cross/bin/ppc64le-linux-gnu-gcc
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110278
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110269
Bug 110269 depends on bug 110278, which changed state.
Bug 110278 Summary: [14 Regression] FAIL: gcc.dg/tree-ssa/pr103257-1.c
scan-tree-dump-times optimized "link_error" 0 from r14-1880-g827e208fa64771
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110278
--- Comment #4 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:69b04fe7445c88edafd6983e28353a158e4314b5
commit r14-1883-g69b04fe7445c88edafd6983e28353a158e4314b5
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110243
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110243
--- Comment #2 from Richard Biener ---
[local count: 5636687]:
+ _141 = (int) _5;
+ _144 = _141 * 2;
+ ivtmp.22_136 = (unsigned int) _144;
...
[local count: 51242611]:
- # d.7_1 = PHI <0(26), _48(23)>
+ # ivtmp.22_17 = PHI
...
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110281
--- Comment #7 from CTC <19373742 at buaa dot edu.cn> ---
(In reply to Jakub Jelinek from comment #6)
> That requires detailed analysis nobody performed yet. csmith is known to
> generate invalid programs sometimes, especially with some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110281
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110281
--- Comment #5 from CTC <19373742 at buaa dot edu.cn> ---
Could you please do me a favor to confirm whether this phenomenon indicates a
bug or a normal behavior? Actually, I also found other optimization sequences
with -fstrict-aliasing which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110282
--- Comment #1 from CTC <19373742 at buaa dot edu.cn> ---
Created attachment 55344
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55344=edit
The compiler output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110282
Bug ID: 110282
Summary: Segmentation fault with specific optimizations
Product: gcc
Version: 11.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110281
--- Comment #4 from Richard Biener ---
clang produces the same behavior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110281
--- Comment #3 from Richard Biener ---
-fno-strict-aliasing avoids the issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110281
Richard Biener changed:
What|Removed |Added
Known to fail||10.4.1, 11.3.0, 12.2.1,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110219
--- Comment #2 from Zdenek Sojka ---
This seems to have been fixed between r14-1822 (BAD) and r14-1881 (GOOD).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110281
--- Comment #1 from CTC <19373742 at buaa dot edu.cn> ---
Created attachment 55342
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55342=edit
The compiler output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110281
Bug ID: 110281
Summary: wrong code with '-O3'
Product: gcc
Version: 11.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110278
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110278
--- Comment #2 from Richard Biener ---
And x != (typeof x)(x == 0) is always true, the only other related one I could
come up with. That's optimized for _Bool but not integer types.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110278
Richard Biener changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110280
ktkachov at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109766
--- Comment #3 from Roger Sayle ---
For the record a solution was proposed at
https://gcc.gnu.org/pipermail/gcc-patches/2023-May/618197.html
but this approach failed review at
https://gcc.gnu.org/pipermail/gcc-patches/2023-May/618278.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110280
--- Comment #1 from Mathieu Malaterre ---
Created attachment 55340
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55340=edit
preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110279
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110280
Bug ID: 110280
Summary: internal compiler error: in const_unop, at
fold-const.cc:1884
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
--- Comment #4 from Alexander Monakov ---
Further reduced:
void f()
{
int c[4] = { 0, 0, 0, 0 };
int cc[8] = { 0 };
asm("" :: "m"(c), "m"(cc));
}
Also reproducible with -march=skylake-avx512 or even plain -mavx512f,
retitling.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110276
Richard Biener changed:
What|Removed |Added
Version|unknown |13.1.1
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110275
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
Version|unknown
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110279
Bug ID: 110279
Summary: Regressions on aarch64 cause by handing FMA in reassoc
(510.parest_r, 508.namd_r)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110278
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
Target
1 - 100 of 110 matches
Mail list logo
