-
Notifications
You must be signed in to change notification settings - Fork 257
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
Unknown directive when building OpenSSL MIPS #286
Labels
Comments
3 tasks
a252539783
pushed a commit
to a252539783/aosp-platform-ndk
that referenced
this issue
May 3, 2017
Test: ./validate.py Bug: android/ndk#259 Bug: android/ndk#286 Change-Id: I86bef3c731f85f8997157daa0692983300c5e101 (cherry picked from commit b544896)
a252539783
pushed a commit
to a252539783/aosp-platform-ndk
that referenced
this issue
May 3, 2017
Test: ./validate.py Bug: android/ndk#259 Bug: android/ndk#286 Change-Id: I86bef3c731f85f8997157daa0692983300c5e101
yan12125
pushed a commit
to yan12125/python3-android
that referenced
this issue
May 18, 2017
An exception: due to android/ndk#286, OpenSSL on MIPS still uses -fno-integrated-as
yan12125
pushed a commit
to yan12125/python3-android
that referenced
this issue
May 18, 2017
Like android/ndk#286, MIPS64 requires -fno-integrated-as, too. It's clang default in r15 beta2. Here I write it explicitly to make things clear.
Is this fixed by the updated clang in r15 beta2? |
@fornwall: Clang's integrated assembler is still incompatible with OpenSSL git-master on MIPS. I didn't check stable releases. |
That's fine though, just use |
MIPS is deprecated as of r16. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When building OpenSSL MIPS with Clang, compiling a MIPS file leads to "unknown directive"
aes-mips.s is a generated source. See https://gist.github.com/yan12125/ea5bf41fdf504cdd212de3fff51a24ed
Steps to reproduce:
First save this patch as use-integrated-as-in-mips.patch
Environment Details
Not all of these will be relevant to every bug, but please provide as much
information as you can.
The text was updated successfully, but these errors were encountered: