This is an archive of the discontinued LLVM Phabricator instance.

[RISCV] Add test for small vector copies
ClosedPublic

Authored by luke on May 23 2023, 7:16 AM.

Diff Detail

Event Timeline

luke created this revision.May 23 2023, 7:16 AM
Herald added a project: Restricted Project. · View Herald TranscriptMay 23 2023, 7:16 AM
luke requested review of this revision.May 23 2023, 7:16 AM
reames accepted this revision.May 23 2023, 8:53 AM

LGTM, with the following additions:

  1. Add one test with volatile load
  2. Add one test with volatile store
  3. Add one test with atomic load or store
This revision is now accepted and ready to land.May 23 2023, 8:53 AM
luke added a comment.May 23 2023, 10:04 AM

LGTM, with the following additions:

  1. Add one test with volatile load
  2. Add one test with volatile store
  3. Add one test with atomic load or store

Just to double check, it should be ok to perform scalarization on volatile/atomic stores right? That's what D150717 already does

This revision was landed with ongoing or failed builds.May 24 2023, 2:25 AM
This revision was automatically updated to reflect the committed changes.
luke added a comment.May 24 2023, 2:27 AM

LGTM, with the following additions:

  1. Add one test with volatile load
  2. Add one test with volatile store
  3. Add one test with atomic load or store

Just to double check, it should be ok to perform scalarization on volatile/atomic stores right? That's what D150717 already does

I was only able to add the volatile tests, since there atomic loads/stores don't seem to be permitted for vector types

LGTM, with the following additions:

  1. Add one test with volatile load
  2. Add one test with volatile store
  3. Add one test with atomic load or store

Just to double check, it should be ok to perform scalarization on volatile/atomic stores right? That's what D150717 already does

Generally, no. If this is triggering for volatile memory ops, we should probably disable it. There's no profit to be had here, and only risk.