https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
Chris Elrod changed:
What|Removed |Added
CC||elrodc at gmail dot com
--- Comment #29 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
--- Comment #30 from Chris Elrod ---
> #if defined(__clang__)
> #define MULTIVERSION
> \
> __attribute__((target_clones("avx512dq", "avx2", "default")))
> #else
> #define MULTIVERSION
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
--- Comment #32 from Chris Elrod ---
Ha, I accidentally misreported my gcc version. I was already using 12.1.1.
Using x86-64-v4 worked, excellent! Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114276
Bug ID: 114276
Summary: Trapping on aligned operations when using vector
builtins + `-std=gnu++23 -fsanitize=address
-fstack-protector-strong`
Product: gcc
Versi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114276
--- Comment #1 from Chris Elrod ---
Created attachment 57652
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57652&action=edit
assembly from adding `-S`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110027
--- Comment #9 from Chris Elrod ---
> Interestingly this seems to be only reproducible on Arch Linux. Other gcc
> 13.1.1 builds, Fedora for instance, seem to behave correctly.
I haven't tried that reproducer on Fedora with gcc 13.2.1, which c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111493
Bug ID: 111493
Summary: [concepts] multidimensional subscript operator inside
requires is broken
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111493
--- Comment #2 from Chris Elrod ---
Note that it also shows up in gcc-13. I put gcc-14 as the version to indicate
that I confirmed it is still a problem on latest trunk. Not sure what the
policy is on which version we should report.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93008
--- Comment #14 from Chris Elrod ---
To me, an "inline" function is one that the compiler inlines.
It just happens that the `inline` keyword also means both comdat semantics, and
possibly hiding the symbol to make it internal (-fvisibility-inline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
Bug ID: 112824
Summary: Stack spills and vector splitting with vector builtins
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
--- Comment #1 from Chris Elrod ---
Here I have added a godbolt example where I manually unroll the array, where
GCC generates excellent code https://godbolt.org/z/sd4bhGW7e
I'm not sure it is 100% optimal, but with an inner Dual size of `7`, on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
--- Comment #2 from Chris Elrod ---
https://godbolt.org/z/3648aMTz8
Perhaps a simpler diff is that you can reproduce by uncommenting the pragma,
but codegen becomes good with it.
template
constexpr auto operator*(OuterDualUA2 a, OuterDualUA2
b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
--- Comment #3 from Chris Elrod ---
> I thought I hit the important cases, but my non-minimal example still gets
> unnecessary register splits and stack spills, so maybe I missed places, or
> perhaps there's another issue.
Adding the unroll p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
--- Comment #6 from Chris Elrod ---
Hongtao Liu, I do think that one should ideally be able to get optimal codegen
when using 512-bit builtin vectors or vector intrinsics, without needing to set
`-mprefer-vector-width=512` (and, currently, also
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824
--- Comment #8 from Chris Elrod ---
> If it's designed the way you want it to be， another issue would be like,
> should we lower 512-bit vector builtins/intrinsic to ymm/xmm when
> -mprefer-vector-width=256, the answer is we'd rather not.
To
15 matches
Mail list logo
