clang: check that the global clang driver's riscv64 default flags make sense for Android #9
Comments
|
For C++:
|
|
For C programs:
|
Duplicate “check defaults for C++ programs at -O0” |
fixed, thanks. i assume the -O3 (which i don't think we use at all) was meant to be -O2 (which we use by default), so i've updated that too. |
appujee
changed the title
|
With the latest build that is probably close to the incoming release here are the flags $ clang-10059077/bin/clang -O0 -target riscv64-linux-android10000 test.c -c -v
$ ./clang-10059077/bin/clang -O2 -target riscv64-linux-android10000 test.c -c -v
|
|
$ clang-10059077/bin/clang++ -target riscv64-linux-android10000 test.cpp -c -v
$ ./clang-10059077/bin/clang++ -target riscv64-linux-android10000 test.cpp -c -v -O2
|
|
At For C programs, Note: The
For C++ programs,
|
|
At For C programs, Note: The
For C++ programs,
|
Bringing parity with aarch64-android google/android-riscv64#9 (comment) Reviewers: enh, danalbert, pirama, srhines Differential Revision: https://reviews.llvm.org/D150490
|
Now that https://reviews.llvm.org/D151512 has landed, the remaining differences in compiler flags w.r.t. AArch64 seem inconsequential. |
we've typically had bits of Android-specific configuration for the llvm targets, and we'll obviously want that to specify our base ABI, but we should run
clang -vor whatever and manually check that all the defaults make sense.The text was updated successfully, but these errors were encountered: