Don't distinguish between i586/i686 #301
Merged
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.
This was historically done as the contents of the
i686
module wouldn'tactually compile on i586 for various reasons. I believe I've tracked this down
to #300 where LLVM refuses to compile a function using the
x86_mmx
typewithout actually enabling the
mmx
feature (sort of reasonably so!). Thiscommit will now compile in both the
i586
andi686
modules of this crate intothe
i586-unknown-linux-gnu
target, and the relevant functions now also enablethe
mmx
feature if they're using the__m64
type.I believe this is uncovering a more widespread problem where the
__m64
isn'tusable outside the context of
mmx
-enabled functions. The i686 and x86_64targets have this feature enabled by default which is why it's worked there, but
they're not enabled for the i586 target. We'll probably want to consider this
when stabilizing!