-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[WIP] Fix Vectorization Flags (long-term / playground) #2426
Closed
svenevs
wants to merge
3
commits into
PointCloudLibrary:master
from
svenevs:vectorization-and-intel-fixes
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we be populating the compiler options instead. I'm just talking semantics here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, long-term these should be public compile options assuming you want consuming projects to inherit them (which we should). I just mirrored what the other compilers do here, but since this one is going to be a longer-term effort definitely yes.
I think a more explicit option
PCL_SSE_FLAGS
orPCL_VECTORIZATION_FLAGS
orPCL_PLATFORM_FLAGS
or something should be added (cached empty string variable, not anoption
call). Usage would be something likecmake .. -DPCL_SSE_FLAGS="-march=native"
orcmake .. -DPCL_SSE_FLAGS="-xavx512"
or whatever, probably allow it to be a list. Then instead of guarding against"${CMAKE_CXX_FLAGS}" STREQUAL ""
, we would do something likeRealistically, creating a
pcl-interface
target is the right thing to do here -- all libs link against that, so we actually would dotarget_compile_options(pcl-interface INTERFACE ${PCL_SSE_FLAGS})
. No need to special-case on compilers. Working with lists is preferred, no need to convert to strings. When you dotarget_link_libraries(pcl PUBLIC pcl-interface)
, theINTERFACE_*_
properties propagate frompcl-interface
topcl
:)