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

(LLVM) Invalid instruction exception on Skylake CPUs #2199

Closed
AniLeo opened this issue Oct 11, 2016 · 11 comments
Closed

(LLVM) Invalid instruction exception on Skylake CPUs #2199

AniLeo opened this issue Oct 11, 2016 · 11 comments

Comments

@AniLeo
Copy link
Member

AniLeo commented Oct 11, 2016

#2145 (comment)
http://www.emunewz.net/forum/showthread.php?tid=175430&pid=234029#pid234029

As referred above, opened an issue so it doesn't get forgotten.

@Nezarn
Copy link

Nezarn commented Oct 11, 2016

Haswell is fine tho. (i have a i5 4690k)

@Nekotekina
Copy link
Member

It's not SSSE3, it's invalid instruction (AVX-512 in this case)

@Nekotekina Nekotekina changed the title (Recompiler) Skylake/Haswell CPUs not being detected properly as having SSSE3. (LLVM) Invalid instruction exception on Skylake CPUs Oct 11, 2016
@Nezarn
Copy link

Nezarn commented Oct 11, 2016

Then how come after changing that line, LLVM worked on Skylake for that Chinese guy?

Also Skylake (i3,i5,i7) doesn't have AVX-512. (only Xeon and Canonlake CPUs (and canonlake isn't here until 2017 Q2)

@Nekotekina
Copy link
Member

You misunderstand something

@Nekotekina
Copy link
Member

Because this is exactly what I meant

@Nekotekina
Copy link
Member

It's invalid instruction exactly because mentioned Skylake doesn't have AVX-512

@Nezarn
Copy link

Nezarn commented Oct 11, 2016

Then how come LLVM works on Haswell? Haswell doesn't have AVX-512 either.

Or i have a magical CPU that has AVX-512? LOL.

@Nekotekina
Copy link
Member

Because it's a bug in LLVM. When it compiles for haswell, it uses correct instructions.

@Nezarn
Copy link

Nezarn commented Oct 11, 2016

Then why not use that workaround you posted in another issue? (or just update LLVM so maybe it got fixed in the meantime?)

@Nekotekina
Copy link
Member

I will not test LLVM 3.9 immediately. Need to check its memory consumption, and this bug may be fixed as well. If it's fixed then we don't need any workaround.

@raven02
Copy link
Contributor

raven02 commented Jan 28, 2017

@AniLeo , is this issue fixed by #2269 ?

@AniLeo AniLeo closed this as completed Jan 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants