https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
--- Comment #7 from uecker at gcc dot gnu.org ---
What is strange is that not updating TYPE_CANONICAL also seems wrong even
before C23, because then it seems we should be able to get pointers with
different TYPE_CANONICAL which are compatible
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
--- Comment #7 from kargls at comcast dot net ---
(In reply to anlauf from comment #6)
> (In reply to kargls from comment #5)
> > The pointers to expr->symtree is NULL. This new patch catches your example.
>
> It does, but behaves weird for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33068
Andrew Pinski changed:
What|Removed |Added
Known to work||13.1.0
--- Comment #3 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25548
Andrew Pinski changed:
What|Removed |Added
Known to fail||
Keywords|accepts-invalid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113765
--- Comment #8 from GCC Commits ---
The master branch has been updated by Eugene Rozenfeld :
https://gcc.gnu.org/g:fe385c219994f6d5c1ffe00bcaf5a62c3d18caaf
commit r14-9780-gfe385c219994f6d5c1ffe00bcaf5a62c3d18caaf
Author: Eugene Rozenfeld
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89305
--- Comment #2 from Andrew Pinski ---
I should note even though the other examples of DR 253 seems to be correctly
accepting now; this one still fails.
Note also EDG rejects this even though accepting the other examples of DR 253
issues; maybe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57820
Andrew Pinski changed:
What|Removed |Added
Status|SUSPENDED |NEW
--- Comment #6 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60284
Andrew Pinski changed:
What|Removed |Added
Status|SUSPENDED |NEW
--- Comment #2 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10118
--- Comment #12 from Andrew Pinski ---
Hmm, clang accepts this also for -std=c++17 (and above).
While EDG accepts this for --c++11 (and above).
Is this valid in C++11+ or C++17+ now?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40771
--- Comment #4 from Andrew Pinski ---
AARCH64 vectorization looks decent too:
```
dup v31.8h, w0
adrpx2, .LC0
adrpx0, .LC1
adrpx1, .LANCHOR0
ldr q30, [x2, #:lo12:.LC0]
ldr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29231
Andrew Pinski changed:
What|Removed |Added
CC||iains at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28141
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28017
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114576
--- Comment #4 from Thiago Macieira ---
(In reply to Jakub Jelinek from comment #3)
> vaesenc etc. instructions can be used even if just -maes -mavx, not just
> -mvaes -mavx512vl.
Correct, that's just VEX-prefixed AESNI instructions.
VAES
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47048
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40988
--- Comment #3 from Andrew Pinski ---
One more note the Linux kernel sources has been corrected already.
They do now:
asm volatile(__ASM_SIZE(btr) " %2,%1"
CC_SET(c)
: CC_OUT(c) (oldbit)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114576
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40988
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101865
Peter Bergner changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|willschm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36512
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358
--- Comment #15 from Adrian Bunk ---
(In reply to Tobias Burnus from comment #11)
> RFC draft patch – also to solve an offload problem with atomic and nvptx
> libgomp:
> https://gcc.gnu.org/pipermail/gcc-patches/2020-October/556297.html
> See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32775
Andrew Pinski changed:
What|Removed |Added
Keywords||documentation
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34629
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99426
--- Comment #7 from Patrick Palka ---
There's a patch pending review at
https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647203.html
Until that's merged, one should be able to work around this error with a trunk
compiler by using
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23872
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86466
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86466
--- Comment #1 from Andrew Pinski ---
Created attachment 57870
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57870=edit
testcase
Please next time attach or place the testcase inline instead of just linking to
godbolt, we were just lucky
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86303
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to kargls from comment #5)
> The pointers to expr->symtree is NULL. This new patch catches your example.
It does, but behaves weird for some other cases. Try:
program main
complex
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86027
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84017
Andrew Pinski changed:
What|Removed |Added
CC||subscribe at teskor dot de
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85919
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85919
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85620
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81652
Bug 81652 depends on bug 85620, which changed state.
Bug 85620 Summary: Missing ENDBR after swapcontext
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85620
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85236
--- Comment #7 from Andrew Pinski ---
clang does not implement this intrinsics either and there is no issue filed
there about it either (I am kinda of shocked).
Note ICX (which is the new ICC but with using clang/LLVM) does and it calls
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93672
--- Comment #3 from Jonathan Wakely ---
So maybe:
--- a/libstdc++-v3/src/c++98/istream.cc
+++ b/libstdc++-v3/src/c++98/istream.cc
@@ -112,7 +112,10 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
basic_istream::
ignore(streamsize __n, int_type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85236
--- Comment #6 from Andrew Pinski ---
https://www.intel.com/content/www/us/en/docs/intrinsics-guide/index.html#!=undefined=SVML=_mm256_atan2_ps_expand=393
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114577
Bug ID: 114577
Summary: Inefficient codegen for SVE/NEON bridge
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87477
Bug 87477 depends on bug 113363, which changed state.
Bug 113363 Summary: ICE on ASSOCIATE and unlimited polymorphic function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113363
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113363
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84210
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
--- Comment #6 from uecker at gcc dot gnu.org ---
Hm, this is enough:
const struct S * x;
struct S {};
void f(const struct S **);
The TYPE_CANONICAL of the pointer type depends on TYPE_CANONICAL of the target.
So it seems if I set it for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114065
--- Comment #11 from Nicolas Boulenguez ---
Created attachment 57869
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57869=edit
Ada: import nanosleep from System.OS_Primitives.Timed_Delay
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114065
--- Comment #10 from Nicolas Boulenguez ---
Created attachment 57868
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57868=edit
Ada: drop unneeded darwin, solaris, x32 variants of System.OS_Primitives
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114065
--- Comment #9 from Nicolas Boulenguez ---
Created attachment 57867
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57867=edit
Ada: drop unneeded posix2008 variant of System.Parameters
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114065
--- Comment #8 from Nicolas Boulenguez ---
Created attachment 57866
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57866=edit
Ada: drop unneeded x32 variant of System.Linux
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114065
--- Comment #7 from Nicolas Boulenguez ---
Hello.
The attached suggestions (based on gcc-13/13.2.0) might solve the current
issue, or at least simplify the investigation, but they are so intrusive that I
would like a quick review by experts
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114576
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114065
Nicolas Boulenguez changed:
What|Removed |Added
CC||nicolas at debian dot org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93672
--- Comment #2 from Jonathan Wakely ---
On second thoughts, I don't think that fix is right.
istream::ignore takes an int_type for the delimiter, so passing it a char_type
with a negative value will confuse it. For example, str.ignore(n,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114576
Andrew Pinski changed:
What|Removed |Added
Summary|[13 |[14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80719
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114576
Bug ID: 114576
Summary: [13 regression][config/i386] GCC 14/trunk emits
VEX-prefixed AES instruction without AVX enabled
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79219
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79217
--- Comment #7 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #6)
> I saw a proposal for C23 (I think it was C23) for arbitrary bit size
> integers. I don't know if that included big integers either.
It does and _BitInt(128) is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78926
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93672
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114572
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-04-03
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107916
Andrew Pinski changed:
What|Removed |Added
CC||ajidala at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Bug 88670 depends on bug 100745, which changed state.
Bug 100745 Summary: GCC generates suboptimal assembly from vector extensions on
AArch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100745
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100745
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Bug 88670 depends on bug 114570, which changed state.
Bug 114570 Summary: GCC doesn't perform good loop invariant code motion for
very long vector operations.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114570
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107916
Andrew Pinski changed:
What|Removed |Added
CC||liuhongt at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114570
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114415
--- Comment #4 from Vladimir Makarov ---
(In reply to Jakub Jelinek from comment #3)
> BTW, with additional -mno-red-zone there is still movement of these insns,
>
The problem is even bigger. Live range splitting uses a standard insn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114510
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93565
--- Comment #31 from Wilco ---
(In reply to Andrew Pinski from comment #29)
> Looking back at this one, I (In reply to Wilco from comment #8)
> > Here is a much simpler example:
> >
> > void f (int *p, int y)
> > {
> > int a = y & 14;
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88607
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |9.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
--- Comment #5 from Jakub Jelinek ---
Oops, return stmt missing:
struct S foo (const struct S *);
struct S {};
struct S bar (const struct S **) { return (struct S) {}; }
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114575
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
--- Comment #4 from Jakub Jelinek ---
Slightly cleaned up testcase:
struct S foo (const struct S *);
struct S {};
struct S bar (const struct S **) {}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114536
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114247
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114515
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114575
Bug ID: 114575
Summary: [14 Regression] SVE addressing modes broken since
g:839bc42772ba7af66af3bd16efed4a69511312ae
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114569
--- Comment #2 from Jason Liam ---
(In reply to Marek Polacek from comment #1)
> So the code should compile.
But https://timsong-cpp.github.io/cppwp/n4950/dcl.ptr#4.sentence-2 says:
> [Note 1: [...] Forming a function pointer type is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114537
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112397
--- Comment #12 from GCC Commits ---
The releases/gcc-13 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:ae11f0154116f4e5fa8769b1ea1600b1b1c22958
commit r13-8577-gae11f0154116f4e5fa8769b1ea1600b1b1c22958
Author: Iain Sandoe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112297
--- Comment #4 from GCC Commits ---
The releases/gcc-13 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:44514fde12e2a8f75fca88fdd6ff7a0e678ac966
commit r13-8573-g44514fde12e2a8f75fca88fdd6ff7a0e678ac966
Author:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632
--- Comment #26 from Iain Sandoe ---
NOTE: I adjusted the PR lines in the commit header so that the commits get
reflected on the PR.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632
--- Comment #25 from GCC Commits ---
The releases/gcc-13 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:e95ab9e60ce1d9aa7751d79291133fd5af9209d7
commit r13-8572-ge95ab9e60ce1d9aa7751d79291133fd5af9209d7
Author:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632
--- Comment #24 from GCC Commits ---
The releases/gcc-13 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:68057560ff1fc0fb2df38c2f9627a20c9a8da5c5
commit r13-8571-g68057560ff1fc0fb2df38c2f9627a20c9a8da5c5
Author:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114552
Jakub Jelinek changed:
What|Removed |Added
Summary|[13/14 Regression] wrong|[13 Regression] wrong code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114569
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571
--- Comment #3 from Pierre Ossman ---
And another odd case; gcc 5 complains about this:
> const char *a;
> a = NULL;
but not:
> const char *a = NULL;
gcc 13 complains about neither, and clang about both.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
Summary|[14 regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114115
--- Comment #15 from Jan Hubicka ---
> Fixed for GCC 14 so far
It is simple patch, so backporting is OK after a week in mainline.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114115
H.J. Lu changed:
What|Removed |Added
Known to work||14.0
--- Comment #14 from H.J. Lu ---
Fixed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114115
--- Comment #13 from GCC Commits ---
The master branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:cab32bacaea268ec062b1fb4fc662d90c9d1cfce
commit r14-9775-gcab32bacaea268ec062b1fb4fc662d90c9d1cfce
Author: H.J. Lu
Date: Mon Feb 26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111966
Tobias Burnus changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114555
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114573
--- Comment #2 from Pierre Ossman ---
Indeed. It is part of an effort to have a more modern C++ style in TigerVNC.
One item was preferring nullptr over NULL, and this issue became an obstacle
there.
Right now, we did a #pragma, but if there is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
--- Comment #2 from Sam James ---
Reduced:
```
struct X509_algor_st sk_X509_ALGOR_copyfunc(const struct X509_algor_st *);
struct X509_algor_st {
} PKCS8_pkey_get0(const struct X509_algor_st **) {
}
```
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114485
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113956
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=114574
--- Comment #1 from Sam James ---
reducing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114568
--- Comment #5 from Maxim Kuvyrkov ---
Looking at this problem more, I think the issue is due to ARM target trying
hard to avoid UNSUPPORTED tests, instead of embracing them.
For the vectorization NEON check we have ...
===
proc
ith-build-config='bootstrap-O3
bootstrap-lto'
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240403 (experimental)
8455d6f6cd43b7b143ab9ee19437452fceba9cc9 (Gentoo 14.0. p, commit
7bbfb01a32b73842f8908de028703510a0e12057)
```
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114551
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
1 - 100 of 142 matches
Mail list logo
