: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: stammark at gcc dot gnu.org
Target Milestone: ---
Hi all,
This is likely a symptom of the WIP-ness of C23 and C++23 support in the
frontends, but see here:
https://godbolt.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112337
--- Comment #4 from Stam Markianos-Wright ---
Bisected to f55cdce3f8dd8503e080e35be59c5f5390f6d95e
Attached preprocessed source and a creduced-reproducer of it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112337
--- Comment #3 from Stam Markianos-Wright ---
Created attachment 56493
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56493=edit
Full preprocessor reproducer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112337
--- Comment #2 from Stam Markianos-Wright ---
Created attachment 56492
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56492=edit
creduced reproducer
Assignee: unassigned at gcc dot gnu.org
Reporter: stammark at gcc dot gnu.org
Target Milestone: ---
Hi all,
I found this ICE when compiling CMSIS-NN with latest trunk:
./build-arm-eabi-armv8.1-m.main+mve.fp+fp.dp/install/bin/arm-eabi-gcc
-mcpu=cortex-m55
~/gnu/CMSIS-NN/Source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110255
Stam Markianos-Wright changed:
What|Removed |Added
Resolution|--- |INVALID
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: stammark at gcc dot gnu.org
Target Milestone: ---
Hi all,
See: https://godbolt.org/z/53ME1fGfM
The compiler with the error is the one that is using -flax-vector-conversions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
Stam Markianos-Wright changed:
What|Removed |Added
Resolution|--- |FIXED
: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: stammark at gcc dot gnu.org
Target Milestone: ---
Hi all,
In the arm backend, for MVE targets we previously had this bug on the vcmp
patterns: https://gcc.gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107674
Stam Markianos-Wright changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177
--- Comment #5 from Stam Markianos-Wright ---
With the fix to MVE auto_inc having gone in as
ddc9b5ee13cd686c8674f92d46045563c06a23ea I have found that this fix keeps the
auto-inc on these predicated stores broken.
It seems to fail in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107674
--- Comment #3 from Stam Markianos-Wright ---
Thank you, Andre for fixing the Part 1 in this ticket :)
The part 2 we've found to be a regression since r13-416-g485a0ae0982abe and is
also the reason why the mve_*_memory_nodes tests are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108443
Stam Markianos-Wright changed:
What|Removed |Added
CC||stammark at gcc dot gnu.org
ity: minor
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: stammark at gcc dot gnu.org
Target Milestone: ---
I've detected a couple of minor issues when using
__attribute__((pcs("aapcs-vfp"))) in no-fp architectures
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10
Stam Markianos-Wright changed:
What|Removed |Added
CC||stammark at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714
Stam Markianos-Wright changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714
Stam Markianos-Wright changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
--- Comment #9 from Stam Markianos-Wright ---
> Clearly Helium+Linux on Godbolt is a bit confused
Yea, I agree -- it still shouldn't be an unintuitive front-end type clash
error, though!
I've posted another patch:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
--- Comment #7 from Stam Markianos-Wright ---
(In reply to Kevin Bracey from comment #6)
> Retesting the Godbolt on trunk, it's now worse - every line produces
> multiple not-very-informative errors:
>
> source>:7:9: error: '_Generic'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
Stam Markianos-Wright changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714
Stam Markianos-Wright changed:
What|Removed |Added
Last reconfirmed||2022-11-17
--- Comment #3 from
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: stammark at gcc dot gnu.org
Target Milestone: ---
We've found a couple of performance regressions with Arm MVE. These can be
seen here:
https
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
Stam Markianos-Wright changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |stammark at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017
Stam Markianos-Wright changed:
What|Removed |Added
CC||stammark at gcc dot gnu.org
: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: stammark at gcc dot gnu.org
Target Milestone: ---
Hi all,
I'm coming across a strange optimisation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
Stam Markianos-Wright changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |stammark at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
--- Comment #8 from Stam Markianos-Wright ---
I have a liiitle bit more progress here, but I have a question about
vect_get_smallest_scalar_type.
If we look at the comment before the function:
>/* Return the smallest scalar part of STMT_INFO.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
--- Comment #7 from Stam Markianos-Wright ---
(In reply to rsand...@gcc.gnu.org from comment #6)
> (In reply to Stam Markianos-Wright from comment #5)
> > I'm tempted to try and add a reverse:
> >
> > || multiple_p (*stmt_vectype_out,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
--- Comment #5 from Stam Markianos-Wright ---
(In reply to rsand...@gcc.gnu.org from comment #4)
> (In reply to Stam Markianos-Wright from comment #3)
> > Just started looking at this. I've narrowed it as the bug appearing with
> > commit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
--- Comment #3 from Stam Markianos-Wright ---
Just started looking at this. I've narrowed it as the bug appearing with commit
9b75f56d4b7951c60a6563964a65787b95bc.
I have yet to fire this up in gdb to see what's happening, but one test I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91816
Stam Markianos-Wright changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90249
--- Comment #14 from Stam Markianos-Wright ---
Was reminded that this was still open after many months. Have fixed the commit
and am in the process of backporting to gcc-8,9.(In reply to Stam
Markianos-Wright from comment #12)
> Was reminded
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90249
Stam Markianos-Wright changed:
What|Removed |Added
Assignee|stammark at gcc dot gnu.org|unassigned at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90249
Stam Markianos-Wright changed:
What|Removed |Added
CC||stammark at gcc dot gnu.org
CC||stammark at gcc dot gnu.org
Last reconfirmed||2020-10-15
--- Comment #1 from Stam Markianos-Wright ---
Also confirmed on today's trunk aarch64-none-elf
Seems to relate to use of that specific type of builtin or type of builtins (I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93300
Stam Markianos-Wright changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93300
Stam Markianos-Wright changed:
What|Removed |Added
Status|NEW |ASSIGNED
37 matches
Mail list logo
