-
-
Notifications
You must be signed in to change notification settings - Fork 829
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
[CMake] Add support for using Eigen alignment with AppleClang #1219
Merged
fabiencastan
merged 1 commit into
alicevision:develop
from
p12tic:eigen-alignment-apple-clang
Sep 16, 2022
Merged
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
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.
I'm wondering if these flags for eigen memory alignment shouldn't be a property of each target instead rather than added like this.
I'm not sure that if the library is then used as a 3rd party the flag added with AddCompilerFlag will be propagated.
Usually, if we add a flag this way (take -Wall as an example) it only applies for the current build, but if the library, once built, is used to link with another project the flag is not added automatically. It's up to the host project. In the case of warning is not an issue, but for flags that change the behavior of the code, it could.
And sadly we have a lot of template code in AV which could be compiled again by the other project. So potentially the other project is compiling this code with a different set of flags and at the same time using also compiled code of the library with another set of flags. That could turn ugly.
Any thoughts?
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.
I agree in principle, but I think in this particular case the work needed would outweigh the benefit due to the following reasons:
AV_EIGEN_MEMORY_ALIGNMENT
. Presumably the user knows what it does and will adjust their own project flags accordingly.