Skip to content

[SYCL] Disable vectorizers in early optimizations #2402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

AlexeySachkov
Copy link
Contributor

No description provided.

@AlexeySachkov
Copy link
Contributor Author

/summary:run

Copy link
Contributor

@bader bader left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, change the default value of SLPVectorize in SYCL mode to off, so we can still control SLP vectorizer using compiler options.
Basically, move the change to the driver/FE and add a regression test.

@bader
Copy link
Contributor

bader commented Sep 1, 2020

BTW, it make sense to disable loop vectorizer by default as well.

Moved changes to clang driver, added test
@AlexeySachkov
Copy link
Contributor Author

/summary:run

bader
bader previously approved these changes Sep 1, 2020
Copy link
Contributor

@bader bader left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, although I think the criteria for turning on/off optimizations should be target triple, rather than language mode.
I expect similar issues for SPIR target in OpenCL mode.

@AlexeySachkov AlexeySachkov marked this pull request as ready for review September 2, 2020 13:17
@AlexeySachkov AlexeySachkov changed the title [TESTING] [SYCL] Disable SLP Vectorizer in early optimizations [SYCL] Disable vectorizers in early optimizations Sep 2, 2020
@bader
Copy link
Contributor

bader commented Sep 2, 2020

@mdtoguchi, @AGindinson, could you take a look, please?

@keryell
Copy link
Contributor

keryell commented Sep 3, 2020

@aisoard @Ralender I am wondering whether this is good or bad for performance on Xilinx FPGA...

Copy link
Contributor

@AGindinson AGindinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@bader
Copy link
Contributor

bader commented Sep 3, 2020

@aisoard @Ralender I am wondering whether this is good or bad for performance on Xilinx FPGA...

@AlexeySachkov, I would prefer if we disable vectorizers only for SPIR target as I noted here. So if Xilinx FPGA uses different triple, it can still control the default behavior. NOTE: NVPTX, doesn't completely disables the vectorizer - https://github.com/intel/llvm/blob/sycl/llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h#L65. It's not clear what is the impact on performance for NVPTX.

@keryell, note, this patch changes the default value, but vectorizers still can be enabled via command line options.

@AlexeySachkov
Copy link
Contributor Author

@AlexeySachkov, I would prefer if we disable vectorizers only for SPIR target as I noted here. So if Xilinx FPGA uses different triple, it can still control the default behavior. NOTE: NVPTX, doesn't completely disables the vectorizer - https://github.com/intel/llvm/blob/sycl/llvm/lib/Target/NVPTX/NVPTXTargetTransformInfo.h#L65. It's not clear what is the impact on performance for NVPTX.

Ok, let's submit this patch as-is for now and I will prepare a follow-up PR to address your comment (submitted #2421 to track that and discuss)

@bader
Copy link
Contributor

bader commented Sep 3, 2020

Thanks!

@bader bader merged commit 20921b1 into intel:sycl Sep 3, 2020
bader added a commit to bader/llvm that referenced this pull request Oct 12, 2020
This reverts commit 20921b1.

Previous changes make this commit unnecessary.
@AlexeySachkov AlexeySachkov deleted the private/asachkov/disable-slp-in-early-optimizations branch February 25, 2021 12:26
kbenzie pushed a commit to kbenzie/intel-llvm that referenced this pull request Feb 17, 2025
[DevASAN][CPU] bugfix for mmap return value check.
Chenyang-L pushed a commit that referenced this pull request Feb 18, 2025
[DevASAN][CPU] bugfix for mmap return value check.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants