Skip to content

Fix some rebranch test failures on main #81279

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 6 commits into from
May 6, 2025

Conversation

AnthonyLatsis
Copy link
Collaborator

@AnthonyLatsis AnthonyLatsis commented May 4, 2025

This is intended to reduce future conflicts with rebranch. These commits are picked from #81190.

…stream LLVM

This attribute was introduced in
7eca38ce76d5d1915f4ab7e665964062c0b37697 (llvm-project).

Match it using a wildcard regex, since it is not relevant to these
tests.

This is intended to reduce future conflicts with rebranch.
… upstream LLVM

The current pattern does not match a ')' inside the argument list. This
will no longer work because `nocapture` became `captures(none) in
29441e4f5fa5f5c7709f7cf180815ba97f611297 (llvm-project).

Use a wildcard regex instead. Doing so does not compromise the test
because the `unnamed_addr` attribute we are guarding against can appear
only after the argument list.

This is intended to reduce future conflicts with rebranch.
…te in upstream LLVM

The parameter attribute was introduced in
5ece35df8586d0cb8c104a9f44eaae771de025f5 (llvm-project) and is expected
here according to the lowered function bodies.

Match it using a wildcard regex, since it is not relevant to these
tests.

This is intended to reduce future conflicts with rebranch.
…in upstream LLVM

The `captures(ret: address, provenance)` parameter attribute is expected
because these functions either immediately return the pointer argument
or pass it as an argument to another such parameter. See
https://llvm.org/docs/LangRef.html#parameter-attributes.

Match it using a wildcard regex, since it is not relevant to these
tests.

This is intended to reduce future conflicts with rebranch.
…pstream LLVM

The attribute is `range(i8 -127, -128)`. The documentation specifies
that the range can wrap, meaning that for i8 [-127, -128) is equivalent
to [-127, 127). This is expected for a function that simply increments a
i8 value. See https://llvm.org/docs/LangRef.html#parameter-attributes.

Match it using a wildcard regex, since it is not relevant to this test.

This is intended to reduce future conflicts with rebranch.
@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please smoke test

…in upstream LLVM

`alias nocapture swiftself` -> `alias swiftself captures(none)`.

`nocapture` became `captures(none)` in
29441e4f5fa5f5c7709f7cf180815ba97f611297 (llvm-project).

This is intended to reduce future conflicts with rebranch.
@AnthonyLatsis AnthonyLatsis force-pushed the fix-rebranch-on-main branch from 623b3f3 to 76333e2 Compare May 4, 2025 06:01
Copy link
Contributor

@aschwaighofer aschwaighofer left a comment

Choose a reason for hiding this comment

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

LGTM

@AnthonyLatsis
Copy link
Collaborator Author

@swift-ci please smoke test

@AnthonyLatsis AnthonyLatsis enabled auto-merge May 6, 2025 19:13
@AnthonyLatsis AnthonyLatsis merged commit 4517a6e into swiftlang:main May 6, 2025
3 checks passed
@AnthonyLatsis AnthonyLatsis deleted the fix-rebranch-on-main branch May 7, 2025 01:19
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.

None yet

2 participants