Skip to content

[DebugInfo] Require 64-bit arch for debug info fragment LIT tests #67699

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

Merged
merged 2 commits into from
Aug 10, 2023

Conversation

asavonic
Copy link
Contributor

@asavonic asavonic commented Aug 3, 2023

These tests depend on the target layout, and there were issues reported for Android armv7 (see #66744) and watchOS (#66879) targets.

These tests depend on the target layout, and there were issues reported for
Android armv7 (see swiftlang#66744) and watchOS (swiftlang#66879) targets.
@asl
Copy link
Contributor

asl commented Aug 3, 2023

@swift-ci please test

@asl asl requested a review from felipepiovezan August 3, 2023 06:41
@@ -3,7 +3,7 @@
// Checking the below on 32 bit architectures would be cumbersome: each
// fragment is 32 bits long, which changes the number of checks as well as the
// arithmethic on the bounds of each fragment.
// UNSUPPORTED: OS=watchos
// REQUIRES: CPU=arm64 || CPU=x86_64
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see several tests that also check for arm64e, not needed here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, added arm64e targets as well.

@asl
Copy link
Contributor

asl commented Aug 3, 2023

@swift-ci please test

@ahoppen
Copy link
Member

ahoppen commented Aug 9, 2023

@swift-ci Please test

@asl asl merged commit f3c6eae into swiftlang:main Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants