-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[compiler-rt] Only include asan on x86 architectures on Windows #137173
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
Conversation
This avoids building asan when targeting Windows on armv7 or aarch64. It is possible to build asan successfully for those configurations (since 5ea9dd8 and 0c39113), but asan isn't functional there. This change skips building asan for targets other than x86_32 and x86_64. By excluding asan from the build, we fix the "check-ubsan" target for armv7 and aarch64 Windows. If asan is included in the build, an ubsan-asan configuration gets added to the tests, and as asan isn't functional for these targets, it produces a lot of test failures even when just trying to run "check-ubsan".
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.
lgtm
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.
It looks good to me, too. My commit just made it compile on ARM Windows, but it never worked correctly, so it absolutely makes sense to disable it altogether on ARM Windows.
…#137173) This avoids building asan when targeting Windows on armv7 or aarch64. It is possible to build asan successfully for those configurations (since 5ea9dd8 and 0c39113), but asan isn't functional there. This change skips building asan for targets other than x86_32 and x86_64. By excluding asan from the build, we fix the "check-ubsan" target for armv7 and aarch64 Windows. If asan is included in the build, an ubsan-asan configuration gets added to the tests, and as asan isn't functional for these targets, it produces a lot of test failures even when just trying to run "check-ubsan".
…#137173) This avoids building asan when targeting Windows on armv7 or aarch64. It is possible to build asan successfully for those configurations (since 5ea9dd8 and 0c39113), but asan isn't functional there. This change skips building asan for targets other than x86_32 and x86_64. By excluding asan from the build, we fix the "check-ubsan" target for armv7 and aarch64 Windows. If asan is included in the build, an ubsan-asan configuration gets added to the tests, and as asan isn't functional for these targets, it produces a lot of test failures even when just trying to run "check-ubsan".
…#137173) This avoids building asan when targeting Windows on armv7 or aarch64. It is possible to build asan successfully for those configurations (since 5ea9dd8 and 0c39113), but asan isn't functional there. This change skips building asan for targets other than x86_32 and x86_64. By excluding asan from the build, we fix the "check-ubsan" target for armv7 and aarch64 Windows. If asan is included in the build, an ubsan-asan configuration gets added to the tests, and as asan isn't functional for these targets, it produces a lot of test failures even when just trying to run "check-ubsan".
…#137173) This avoids building asan when targeting Windows on armv7 or aarch64. It is possible to build asan successfully for those configurations (since 5ea9dd8 and 0c39113), but asan isn't functional there. This change skips building asan for targets other than x86_32 and x86_64. By excluding asan from the build, we fix the "check-ubsan" target for armv7 and aarch64 Windows. If asan is included in the build, an ubsan-asan configuration gets added to the tests, and as asan isn't functional for these targets, it produces a lot of test failures even when just trying to run "check-ubsan".
This avoids building asan when targeting Windows on armv7 or aarch64. It is possible to build asan successfully for those configurations (since 5ea9dd8 and 0c39113), but asan isn't functional there.
This change skips building asan for targets other than x86_32 and x86_64.
By excluding asan from the build, we fix the "check-ubsan" target for armv7 and aarch64 Windows. If asan is included in the build, an ubsan-asan configuration gets added to the tests, and as asan isn't functional for these targets, it produces a lot of test failures even when just trying to run "check-ubsan".