https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|9.3 |9.4
--- Comment #12 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #11 from Richard Biener ---
Created attachment 46880
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46880=edit
prototype
This improves code-gen to use pextrw where possible but that doesn't make any
measurable difference on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #10 from Richard Biener ---
Can't really decipher what clang does here. it seems to handle even/odd
lanes separately, doing 24 vpextrb stores per loop iteration. Possibly
simply an interleaving scheme...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #9 from Richard Biener ---
(In reply to Richard Biener from comment #8)
> The most trivial improvement is likely to recognize the vector parts we can
> store via HImode. There's already support for that but only if we can
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #8 from Richard Biener ---
The most trivial improvement is likely to recognize the vector parts we can
store via HImode. There's already support for that but only if we can
uniformly
use HImode and not a mix of sizes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #7 from rguenther at suse dot de ---
On Wed, 11 Sep 2019, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
>
> Jakub Jelinek changed:
>
>What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #6 from rguenther at suse dot de ---
On Wed, 11 Sep 2019, ubizjak at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
>
> --- Comment #5 from Uroš Bizjak ---
> (In reply to Richard Biener from comment #3)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #5 from Uroš Bizjak ---
(In reply to Richard Biener from comment #3)
> Reducing the VF here should be the goal. For the particular case "filling"
> the holes with neutral data and blending in the original values at store time
> will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #3 from Richard Biener ---
Reducing the VF here should be the goal. For the particular case "filling"
the holes with neutral data and blending in the original values at store time
will likely be optimal. So do
tem = vector load
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
--- Comment #2 from Richard Biener ---
Errr, before we _dont_ vectorize.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91735
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*
13 matches
Mail list logo
