https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416
--- Comment #1 from Rainer Orth ---
Created attachment 57757
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57757=edit
testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114416
Bug ID: 114416
Summary: SPARC V9 struct return with floating-point members
violates ABI
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101523
--- Comment #39 from Segher Boessenkool ---
(In reply to Richard Biener from comment #37)
> Created attachment 57753 [details]
> quick attempt at a limit
>
> So like this?
Hrm. It should be possible to not have the same test 28 times. Just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101523
--- Comment #38 from Segher Boessenkool ---
(In reply to Richard Biener from comment #36)
> > No, it definitely should be done. As I showed back then, it costs less than
> > 1%
> > extra compile time on *any platform* on average, and it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #24 from Jakub Jelinek ---
Created attachment 57756
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57756=edit
gcc14-pr111736-ubsan.patch
Untested ubsan patch.
nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240321 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114397
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114397
--- Comment #2 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:59b6cece54f33ac4994834d01e18269856576556
commit r14-9592-g59b6cece54f33ac4994834d01e18269856576556
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114401
--- Comment #2 from Jonathan Wakely ---
There's another bug in the node move assignment operator, so I'll fix that too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114405
Jakub Jelinek changed:
What|Removed |Added
Attachment #57747|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114203
Richard Biener changed:
What|Removed |Added
Known to work||13.2.1
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114070
--- Comment #12 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:a3ff14ac4804be400a52dcf630f0de2d57cae835
commit r13-8481-ga3ff14ac4804be400a52dcf630f0de2d57cae835
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114203
--- Comment #4 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:a729b1227bc8c84cd91a3b8c9c9d11bc43d415de
commit r13-8482-ga729b1227bc8c84cd91a3b8c9c9d11bc43d415de
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112718
--- Comment #5 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:dd1948d467dc25b9b462b173ec40b95f6aa51356
commit r13-8477-gdd1948d467dc25b9b462b173ec40b95f6aa51356
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114070
--- Comment #11 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:a9a425df628ab80374cc6a132d39e470bc78c8bc
commit r13-8480-ga9a425df628ab80374cc6a132d39e470bc78c8bc
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114027
--- Comment #16 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:bd276b5340563182f7d95c383196fdd6fb7e6a1d
commit r13-8479-gbd276b5340563182f7d95c383196fdd6fb7e6a1d
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113910
--- Comment #18 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:9a19811ea1e9b3024c0f41b074d71679088bb2d7
commit r13-8478-g9a19811ea1e9b3024c0f41b074d71679088bb2d7
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #23 from GCC Commits ---
The releases/gcc-13 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:6d5eb47849bcf9aecefacf7d7e4767750b1ec83b
commit r13-8476-g6d5eb47849bcf9aecefacf7d7e4767750b1ec83b
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114410
--- Comment #7 from Cristian VOICA ---
I've found a flag that sounds closer to my needs: -Wcast-qual
As the issue seems to me to come from the need to stay compatible with C I
think this flag does a pretty decent job to hint at the problem.
:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114396
--- Comment #22 from GCC Commits ---
The releases/gcc-13 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:199b021a38f30b681e0dbecd2d0296beabd50b13
commit r13-8475-g199b021a38f30b681e0dbecd2d0296beabd50b13
Author: liuhongt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114410
--- Comment #6 from Cristian VOICA ---
makes sense, thx!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114414
Filip Kastl changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114414
Bug ID: 114414
Summary: [14 Regression] 15-18% exec time slowdown of 433.milc
on Zen2
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114410
--- Comment #5 from Jonathan Wakely ---
No, because a (T) style cast can do almost anything. In this case it's
equivalent to
const_cast(static_cast(a->m_i))
which is valid code.
-Wold-style-cast will warn about using any form of (T) cast,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114413
Bug ID: 114413
Summary: BB SLP sub-graph merging fails to CSE nodes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114396
--- Comment #21 from Andrew Pinski ---
(In reply to JuzheZhong from comment #19)
> I think it's better to add pr114396.c into vect testsuite instead of x86
> target test since it's the bug not only happens on x86.
Actually I think a testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114396
--- Comment #20 from Hongtao Liu ---
(In reply to JuzheZhong from comment #19)
> I think it's better to add pr114396.c into vect testsuite instead of x86
> target test since it's the bug not only happens on x86.
Sure, there's no target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114396
--- Comment #19 from JuzheZhong ---
I think it's better to add pr114396.c into vect testsuite instead of x86 target
test since it's the bug not only happens on x86.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114396
--- Comment #18 from GCC Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:ac2f8c2a367151fc0410f904339c475a953cffc8
commit r14-9591-gac2f8c2a367151fc0410f904339c475a953cffc8
Author: liuhongt
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113950
--- Comment #5 from GCC Commits ---
The releases/gcc-13 branch has been updated by jeevitha :
https://gcc.gnu.org/g:27eb6e81e6e578da9f9947d3f96c0fa58971fe7f
commit r13-8474-g27eb6e81e6e578da9f9947d3f96c0fa58971fe7f
Author: Jeevitha
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #22 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:134ef2a8cac1a5cc718739bd7d3b3472947c80d6
commit r14-9590-g134ef2a8cac1a5cc718739bd7d3b3472947c80d6
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112697
Filip Kastl changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #10 from Filip Kastl ---
I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
--- Comment #1 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114411
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114411
--- Comment #2 from Richard Biener ---
r14-9412-g3e3e4156a5f93e would be likely (but there's a lot of changes in that
range)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #21 from Jakub Jelinek ---
(In reply to Jakub Jelinek from comment #20)
> Though, talking about address spaces, guess we also need to change ubsan.cc,
> so that for targetm.addr_space.zero_address_valid (as) case it actually
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114409
--- Comment #6 from Richard Biener ---
The alternative is "bisceting" with -fdbg-cnt=vect_loop (IIRC there were some
ICEs reported when using that, so YMMV)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114408
Richard Biener changed:
What|Removed |Added
Known to work||12.3.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114412
Bug ID: 114412
Summary: [14 Regression] 7% slowdown of 436.cactusADM on
aarch64
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114411
--- Comment #1 from Filip Kastl ---
The CPU is Ampere Altra - Neoverse N1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114411
Bug ID: 114411
Summary: [14 Regression] 12% exec time slowdown of 433.milc on
aarch64
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114410
--- Comment #4 from Cristian VOICA ---
I'm also trying to understand another thing.
Perhaps you can point me to where to read more about it as I was not expecting
casting to a non-const reference to work for a member in a const object.
Is
Linux... Parsing ELF... Performing relocations... done.
> Booting the kernel (entry_offset: 0x).
> [0.00] Linux version 6.8.0-11485-ge1826833c3a9 (uros@localhost)
> (xgcc (GCC) 14.0.1 20240321 (experimental) [master r14-9588-g415091f0909],
> GNU ld version 2.40-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 114268, which changed state.
Bug 114268 Summary: [14 Regression] 5% exec time regression in 454.calculix on
Aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114268
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114268
Filip Kastl changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
ff from annotating *any* gs: prefixed address.
>
> I'll test your patch from Comment #13 ASAP.
Weee, it works!
Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel (entry_offset: 0x0000).
[0.00] Linux version 6.8.0-11485-ge1826833c3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114410
--- Comment #3 from Cristian VOICA ---
be aware that is initial issue mentions "If the type of r is changed to const
int&, the program correctly compiles with GCC"
I have this in my code as well but this is not always what programmer wants as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113141
Andrew Pinski changed:
What|Removed |Added
CC||cvoica at gmail dot com
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114410
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114410
Andrew Pinski changed:
What|Removed |Added
URL|https://godbolt.org/#z:OYLg |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114410
Bug ID: 114410
Summary: compiler issue in reference_binding when using rvalue
reference to member of const object
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #18 from Jakub Jelinek ---
(In reply to rguent...@suse.de from comment #17)
> On Thu, 21 Mar 2024, ubizjak at gmail dot com wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
> >
> > --- Comment #16 from Uro? Bizjak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92080
--- Comment #11 from Andrew Pinski ---
(In reply to Richard Biener from comment #6)
> Similar when vectorizing
>
> int a[4096];
>
> void foo ()
> {
> for (int i = 1; i < 4095; ++i)
> a[i] = 42;
> }
This was actually reported by me in PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #17 from rguenther at suse dot de ---
On Thu, 21 Mar 2024, ubizjak at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
>
> --- Comment #16 from Uro? Bizjak ---
> (In reply to Richard Biener from comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92080
--- Comment #10 from Richard Biener ---
But it's even simpler than the cited case - the mode has the same size (for the
latest testcase, not for the original one, of course).
It's also that after reload a zeroing of V4SImode will also zero ymm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101523
--- Comment #37 from Richard Biener ---
Created attachment 57753
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57753=edit
quick attempt at a limit
So like this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101523
--- Comment #36 from Richard Biener ---
(In reply to Segher Boessenkool from comment #35)
> (In reply to Richard Biener from comment #34)
> > The change itself looks reasonable given costs, though maybe 2 -> 2
> > combinations should not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #16 from Uroš Bizjak ---
(In reply to Richard Biener from comment #13)
> The original testcase is fixed, appearantly slapping 'extern' on the int
> makes it not effective.
>
> Possibly better amend the
>
> if (VAR_P (inner) &&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92080
--- Comment #9 from Hongtao Liu ---
> If we were to expose that vpxor before postreload we'd likely CSE but
> we have
>
> 5: xmm0:V4SI=const_vector
> REG_EQUIV const_vector
> 6: [`b']=xmm0:V4SI
> 7: xmm0:V8HI=const_vector
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101523
--- Comment #35 from Segher Boessenkool ---
(In reply to Richard Biener from comment #34)
> The change itself looks reasonable given costs, though maybe 2 -> 2
> combinations should not trigger when the cost remains the same? In
> this case it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92080
--- Comment #8 from rguenther at suse dot de ---
On Thu, 21 Mar 2024, liuhongt at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92080
>
> Hongtao Liu changed:
>
>What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #15 from Richard Biener ---
(In reply to Richard Biener from comment #13)
> The original testcase is fixed, appearantly slapping 'extern' on the int
> makes it not effective.
>
> Possibly better amend the
>
> if (VAR_P (inner)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113727
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113727
--- Comment #24 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:9d6ff6f1ea2ae7fc32ec9fbd0554fb06238ed045
commit r14-9589-g9d6ff6f1ea2ae7fc32ec9fbd0554fb06238ed045
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
--- Comment #14 from Richard Biener ---
That also fixes
int foo (int __seg_gs *m)
{
return *m;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
Richard Biener changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
--- Comment #13 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92080
Hongtao Liu changed:
What|Removed |Added
CC||liuhongt at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736
Uroš Bizjak changed:
What|Removed |Added
Priority|P3 |P1
--- Comment #12 from Uroš Bizjak ---
101 - 169 of 169 matches
Mail list logo
