https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106481
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71775
--- Comment #3 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:c23a9c87cc62bd177fd0d4db6ad34b34e1b9a31f
commit r13-1942-gc23a9c87cc62bd177fd0d4db6ad34b34e1b9a31f
Author: Roger Sayle
Date: Wed Au
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #21 from Kewen Lin ---
I didn't look into this in details, but something in the culprit commit caught
my eyes, take altivec_vmrghh as example:
Before the patch, the pattern
[(set (match_operand:V8HI 0 "register_operand" "=v")
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47949
--- Comment #5 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:fc6ef90173478521982e9df3831a06ea85b4f41e
commit r13-1945-gfc6ef90173478521982e9df3831a06ea85b4f41e
Author: Roger Sayle
Date: Wed Au
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #22 from rguenther at suse dot de ---
On Wed, 3 Aug 2022, linkw at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
>
> --- Comment #21 from Kewen Lin ---
> I didn't look into this in details, but somet
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #11 from Mathieu Malaterre ---
(In reply to Uroš Bizjak from comment #10)
> The reason the test fails with gcc-12 is that gcc-12 enabled
> auto-vectorisation for -O2.
I can make the symptoms go away by doing: `-O2 -fno-tree-vectoriz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105924
Lin-Hui Ye changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #2 from Lin-Hui Ye ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #23 from Kewen Lin ---
> Ideally we would avoid semantic difference of RTL depending on the target.
> If that's not avoidable there should be target macros/hooks that specify
> the desired semantics.
Not sure, IMHO it seems it doe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
Richard Biener changed:
What|Removed |Added
CC||rearnsha at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106499
--- Comment #23 from Martin Liška ---
> If may I ask yet another question 😋
Sure, don't hesitate ;)
> Martin can you tell how did you manage to diagnose that it was exactly that
> cause in this case?
I noticed we spent time in inliner (perf t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187
--- Comment #49 from CVS Commits ---
The master branch has been updated by Richard Earnshaw :
https://gcc.gnu.org/g:64ce76d940501cb04d14a0d36752b4f93473531c
commit r13-1948-g64ce76d940501cb04d14a0d36752b4f93473531c
Author: Richard Earnshaw
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106511
Bug ID: 106511
Summary: [13 Regression] New -Werror=maybe-uninitialized since
r13-1268-g8c99e307b20c502e
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106511
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2022-08-03
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187
Richard Earnshaw changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rearnsha at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #25 from rsandifo at gcc dot gnu.org
---
AIUI the rules are:
- GCC vector lane numbers always correspond to memory array indices.
For example, lane 0 always comes first in memory.
- On big-endian targets, vector loads and stores
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079
--- Comment #9 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:4e5ca7ff8c9afd3c38245aa6b939cd3ae49bf1fe
commit r12-8653-g4e5ca7ff8c9afd3c38245aa6b939cd3ae49bf1fe
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #26 from rsandifo at gcc dot gnu.org
---
> describes a different option on big-endian and little-endian
should have said: describes a different instruction. In other words,
the mapping of gimple to RTL operations is fixed, but the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106512
Bug ID: 106512
Summary: String optimization underflows in
std::string::operator+ inlining
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99888
--- Comment #2 from Kewen Lin ---
Created attachment 53405
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53405&action=edit
untested patch
With the attached patch, for -fpatchable-function-entry=5,2 it gets:
foo:
.LFB0:
.cfi_start
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106512
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Jonathan Wakely changed:
What|Removed |Added
CC||hi at jdoubleu dot de
--- Comment #16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106499
--- Comment #24 from Tomasz Kłoczko ---
Thank you :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106513
Bug ID: 106513
Summary: bswap is incorrectly generated
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106513
--- Comment #1 from Andreas Schwab ---
This subexpression has undefined behaviour: (((int64_t) 0xff) << 56).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
--- Comment #11 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:18eecb8c4a97716d4bc4890b05c91f172fadc7b3
commit r10-10928-g18eecb8c4a97716d4bc4890b05c91f172fadc7b3
Author: Jonathan Wa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748
--- Comment #12 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:18eecb8c4a97716d4bc4890b05c91f172fadc7b3
commit r10-10928-g18eecb8c4a97716d4bc4890b05c91f172fadc7b3
Author: Jonathan Wa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98421
--- Comment #4 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:de802e4736613a585dcfd508acf73033f18aa4da
commit r10-10932-gde802e4736613a585dcfd508acf73033f18aa4da
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #12 from Mathieu Malaterre ---
Created attachment 53406
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53406&action=edit
main function with no-tree-optimize attribute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #13 from Mathieu Malaterre ---
Created attachment 53407
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53407&action=edit
main function with no-tree-optimize attribute
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322
--- Comment #14 from Mathieu Malaterre ---
I can make the symptom go away with a single function attribute:
```
% diff -u *
--- /tmp/ii/mul_test.cc.ii.bad 2022-08-03 12:29:41.192263306 +
+++ /tmp/ii/mul_test.cc.ii.good 2022-08-03 12:29:41.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106513
--- Comment #2 from Krister Walfridsson ---
(In reply to Andreas Schwab from comment #1)
> This subexpression has undefined behaviour: (((int64_t) 0xff) << 56).
I thought that was allowed in GCC as the manual says
(https://gcc.gnu.org/onlinedoc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103133
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|11.3|10.5
--- Comment #12 from Jonathan Wa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748
--- Comment #13 from Jonathan Wakely ---
Fixed for 11.3 and 10.5 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98421
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|11.3|10.5
--- Comment #5 from Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105844
--- Comment #9 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:8a57deb926cd660c2eae7ed621d61a301ae0d523
commit r12-8654-g8a57deb926cd660c2eae7ed621d61a301ae0d523
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92978
--- Comment #9 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:8a57deb926cd660c2eae7ed621d61a301ae0d523
commit r12-8654-g8a57deb926cd660c2eae7ed621d61a301ae0d523
Author: Jonathan Wakel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105957
--- Comment #4 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:2ef2de76dae5cac14e0de77ca7205e43be03ab22
commit r12-8655-g2ef2de76dae5cac14e0de77ca7205e43be03ab22
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105995
--- Comment #7 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:e562236851e06091256593aa0d3fbda60a28e45b
commit r12-8657-ge562236851e06091256593aa0d3fbda60a28e45b
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104443
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:1a9681e60964c7f7ce0892e14745e6dcf6100157
commit r12-8660-g1a9681e60964c7f7ce0892e14745e6dcf6100157
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106248
--- Comment #10 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:7a0ed28d4feb450f1ede5b52b57793a5df5b19fe
commit r12-8659-g7a0ed28d4feb450f1ede5b52b57793a5df5b19fe
Author: Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106248
--- Comment #11 from Jonathan Wakely ---
Backported for 12.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105844
--- Comment #10 from Jonathan Wakely ---
Backported for 12.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105995
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|13.0|12.2
--- Comment #8 from Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104443
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|13.0|12.2
--- Comment #7 from Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105957
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106514
Bug ID: 106514
Summary: [12/13 Regression] ranger slowness in path query
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106514
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |12.2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
Bug ID: 106515
Summary: [13 regression] gcc.dg/debug/btf/btf-int-1.c fails
after r13-1937-g5df04a7aa837a1
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
Jose E. Marchesi changed:
What|Removed |Added
CC||jose.marchesi at oracle dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
--- Comment #2 from Jose E. Marchesi ---
Don't bother I just reproduced the issue in powerpc64le-linux-gnu.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
--- Comment #3 from Jose E. Marchesi ---
This is due to having not so good regular expressions in the test btf-int-1.c
and to a slightly different way than the powerpc backend has to comment lines
in assembly.
Working on a fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516
Bug ID: 106516
Summary: New test case gcc.dg/pr104992.c fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104992
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106514
--- Comment #1 from Andrew Macleod ---
(In reply to Richard Biener from comment #0)
>
> Part of the sub-optimality is probably the equiv chain becoming very long
> (can we simply limit that?) and clearing bits in all the very many
> bitmaps li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106515
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jose E. Marchesi :
https://gcc.gnu.org/g:f0688c82ba8206a3d8960eb1d4821dc6a5f2a9f4
commit r13-1951-gf0688c82ba8206a3d8960eb1d4821dc6a5f2a9f4
Author: Jose E. Marchesi
Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91674
Richard Earnshaw changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105090
Richard Earnshaw changed:
What|Removed |Added
CC||andij.cr at gmail dot com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105090
Richard Earnshaw changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106517
Bug ID: 106517
Summary: RISC-V: Inefficient Generated Code for Floating Point
to Integer Rounds
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #27 from Segher Boessenkool ---
IMO what vec_select calls element 0 is always in the first argument of the
vec_concat it works on, in BE as well as LE. But yes this is quite
underdefined
in our documentation, and who know what is ac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106069
--- Comment #28 from Segher Boessenkool ---
(In reply to rsand...@gcc.gnu.org from comment #25)
> - On big-endian targets, vector loads and stores are assumed to put the
> first memory element at the most significant end of the vector register
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25521
--- Comment #9 from Jose E. Marchesi ---
So I got feedback from the clang/llvm folks on this.
As you can see in [1] they asked the WG14 reflectors about the footnote 135 in
the C18 spec and their conclusion is that there is no normative objectio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99888
--- Comment #3 from Segher Boessenkool ---
Your second option isn't correct: all these nops should be consecutive. Your
option 1 is fine :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106514
--- Comment #2 from CVS Commits ---
The master branch has been updated by Andrew Macleod :
https://gcc.gnu.org/g:19ffb35d17474bb4dd3eb78963c28d10b5362321
commit r13-1952-g19ffb35d17474bb4dd3eb78963c28d10b5362321
Author: Andrew MacLeod
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106518
Bug ID: 106518
Summary: Exchange/swap aware register allocation (generate xchg
in reload)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhanceme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106519
Bug ID: 106519
Summary: [13 Regression] internal compiler error: in
gimple_phi_arg, at gimple.h:4594 by r13-1950
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106519
seurer at gcc dot gnu.org changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106520
Bug ID: 106520
Summary: 2+ index expressions in build_op_subscript are
incorrectly interpreted as comma expression
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
-bootstrap
--enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
--with-system-zlib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20220803 (experimental) [maste
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106519
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43301
Eric Gallager changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106502
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106516
Kewen Lin changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106502
--- Comment #7 from Jonathan Wakely ---
The way I found the bug might be, but the bug itself is nothing to do with
that.
76 matches
Mail list logo