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

Already on GitHub? Sign in to your account

LDC should not enable host CPU features by default #323

Closed
svenstaro opened this Issue Apr 1, 2013 · 2 comments

Comments

Projects
None yet
2 participants
Contributor

svenstaro commented Apr 1, 2013

Judging by this issue posted by one of our users, there seems to be a problem with ldc currently picking best available flags on the host CPU. Arch uses -march=x86_64 for x86_64 so nothing fancy. It surely shouldn't enable AVX but apparently it does. The system I build this package on has AVX support. This might explain it. It is as though ldc uses -march=native.

This doesn't seem to be a downstream packaging problem on my side. Can you guys investigate please? The bug report I linked includes some helpful information.

Owner

klickverbot commented Apr 1, 2013

Yep, we should definitely do the equivalent of -mtune=generic by default.

@ghost ghost assigned klickverbot May 7, 2013

Owner

klickverbot commented May 7, 2013

On it, just need a few quiet minutes to sit down and commit this.

I chose to just take the code from Clang.

Maybe this should be abstracted to into LLVM.

klickverbot added a commit to klickverbot/ldc that referenced this issue May 9, 2013

klickverbot added a commit to klickverbot/ldc that referenced this issue May 9, 2013

klickverbot added a commit to klickverbot/ldc that referenced this issue May 9, 2013

klickverbot added a commit to klickverbot/ldc that referenced this issue May 9, 2013

klickverbot added a commit to klickverbot/ldc that referenced this issue May 9, 2013

klickverbot added a commit to klickverbot/ldc that referenced this issue May 9, 2013

redstar pushed a commit that referenced this issue Sep 27, 2014

Merge pull request #323 from jmdavis/equals_t
Added note to equals_t and hash_t.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment