-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
configure: use __ARM_ARCH to determine arm version #4123
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
configure: use __ARM_ARCH to determine arm version #4123
Conversation
'__ARM_ARCH_7M__' in cc_macros_cache or | ||
'__ARM_ARCH_7S__' in cc_macros_cache) | ||
return ('__ARM_ARCH' in cc_macros_cache and | ||
cc_macros_cache['__ARM_ARCH'] == '7') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could simplify this to return cc_macros_cache.get('__ARM_ARCH') == '7'
.
LGTM with a comment. |
@joaocgreis Not aware of such, no. |
ff3b1f0
to
8dabc4d
Compare
Updated, thanks for the reviews! Will land Tuesday if there are no further comments. |
Note: |
|
Before this change, configure used processor specific macro defines (like __ARM_ARCH_6M__) to detect the arm processor version. This changes configure to use __ARM_ARCH, that should be defined to the correct version. Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: nodejs#4123
8dabc4d
to
a7f5dfd
Compare
Before this change, configure used processor specific macro defines (like __ARM_ARCH_6M__) to detect the arm processor version. This changes configure to use __ARM_ARCH, that should be defined to the correct version. Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: #4123
Landed in |
Before this change, configure used processor specific macro defines (like __ARM_ARCH_6M__) to detect the arm processor version. This changes configure to use __ARM_ARCH, that should be defined to the correct version. Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: #4123
Before this change, configure used processor specific macro defines (like __ARM_ARCH_6M__) to detect the arm processor version. This changes configure to use __ARM_ARCH, that should be defined to the correct version. Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: #4123
Before this change, configure used processor specific macro defines (like __ARM_ARCH_6M__) to detect the arm processor version. This changes configure to use __ARM_ARCH, that should be defined to the correct version. Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: #4123
Before this change, configure used processor specific macro defines (like __ARM_ARCH_6M__) to detect the arm processor version. This changes configure to use __ARM_ARCH, that should be defined to the correct version. Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> PR-URL: nodejs#4123
Before this change, configure used processor specific macro defines (like
__ARM_ARCH_6M__
) to detect the arm processor version. This changes configure to use__ARM_ARCH
, that should be defined to the correct version.This is useful because configure may not expect the flag for a specific processor. Currently, if trying to cross compile optimizing to the Raspberry Pi 1 processor with
-mcpu=arm1176jzf-s
the detectedarm_version
will bedefault
(because it sets__ARM_ARCH_6ZK__
), and the generated binaries useless in that processor.@nodejs/platform-arm ARM processors currently on CI are ok with this change, but could there be some other processor or compiler that does not set
__ARM_ARCH
or sets it to something that we do not want? @mmalecki you authored the original function, do you know of any problem with this? (Thanks!)cc @nodejs/build
For reference: