Fix get_elf_hwcap always return 0 on HarmonyOS NEXT. #5951
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 is a fix for
get_elf_hwcapon HarmonyOS NEXT device, see #5950 .By default,
get_elf_hwcapwill useget_elf_hwcap_from_proc_self_auxv, and it need to read/proc/self/auxvto get the hwcap.And on HarmonyOS NEXT, when build hap with debug type,
/proc/self/auxvis readable. But when build hap with release,/proc/self/auxvcan't read. That will makeg_hwcapsandg_hwcaps2to0when use release build type.HarmonyOS NEXT has
<sys/auxv.h>, so usegetauxval()in<sys/auxv.h>, just like android do.This issue will Influence the methods below:
Due my test, after the change,
cpuidandsve2art still0, others works fine.