Skip to content
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

Minor fixes for Intel C/C++ compilers #330

Merged
merged 3 commits into from
Apr 13, 2022
Merged

Conversation

amadio
Copy link
Collaborator

@amadio amadio commented Apr 11, 2022

No description provided.

@bernhardmgruber
Copy link
Collaborator

I am fine with the commit streamlining the MayAlias implementation.

For the other two commits dropping the obsolete instruction sets: could you please move those to a separate PR and also inspect the C++ source code whether there is any special handling of those instruction sets if they are available? Thx!

amadio added 2 commits April 12, 2022 10:07
Even AMD processors use FMA3 these days, so on most CPUs
FMA4 is "broken". CPUs supporting XOP and FMA4 are mostly
obsolete.
Also, disable warnings about attributes, same as for GCC.
@amadio
Copy link
Collaborator Author

amadio commented Apr 12, 2022

Ok, rather than remove, I just conditionally enable the compilation of the XOP+FMA4 targets. This is enough to get rid of the warnings with the Intel compiler, which cannot do XOP+FMA4. I think since all changes here are related to improving things with the Intel compiler, it's ok to keep them together in this pull request, no?

Fixes the warning below when building with the Intel compiler:

CMake Warning at cmake/VcMacros.cmake:503 (message):
  The following unknown targets where listed in the ONLY list of
  vc_compile_for_all_implementations: 'SSE+XOP+FMA4;AVX+XOP+FMA4;AVX+XOP+FMA'
Call Stack (most recent call first):
  CMakeLists.txt:121 (vc_compile_for_all_implementations)
@bernhardmgruber bernhardmgruber merged commit 6125a37 into VcDevel:1.4 Apr 13, 2022
@amadio
Copy link
Collaborator Author

amadio commented Apr 13, 2022

This actually caused a warning with MSVC, so I was waiting to merge until I got that fixed... Ok I can add the fix afterwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants