add tests for thumb interworking - #153153

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm
Mar 2, 2026
Merged

add tests for thumb interworking#153153
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes#151946

thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.

cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise

I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.

@rustbot

Copy link
Copy Markdown
Collaborator

The run-make-support library was changed

cc @jieyouxu

@rustbotrustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 26, 2026
@rust-log-analyzer

This comment has been minimized.

@rustbotrustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 26, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

@theemathas why was this closed?

@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I'm assuming it was closed on accident then?

@folkertdevfolkertdev reopened this Feb 27, 2026
@rustbotrustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 27, 2026
@theemathas

Copy link
Copy Markdown
Contributor

I've never seen this PR before. Don't know what happened.

@thejpster

Copy link
Copy Markdown
Contributor

I don’t know the details of the test infra so I can’t comment there. The examples look good but perhaps:

  • it could be renamed ‘thumb-interworking’ because that’s the target flag
  • The a32 and t32 files can be merged into one, with entry calling six functions
  • The test could be extended to all targets with thumb-interworking enabled?

I also wondered if the hash in the thunk name was stable or if we needed to Wildcard it?

Comment threadtests/run-make/thumb-calling-arm/rmake.rs Outdated
@jieyouxu

Copy link
Copy Markdown
Member

@rustbot author

@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2026
@rustbot

Copy link
Copy Markdown
Collaborator

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@folkertdevfolkertdev left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Good points @thejpster, I've renamed and added tests using the arm targets.

@rustbot ready

View changes since this review

Comment threadtests/run-make/thumb-interworking/rmake.rs
@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 1, 2026
@thejpster

thejpster commented Mar 1, 2026

Copy link
Copy Markdown
Contributor

Looks good to me. You could also add:

  • armv6-none-eabi
  • armv6-none-eabihf
  • thumbv6-none-eabi
  • armv7r-none-eabi
  • armv7r-none-eabihf
  • thumbv7r-none-eabi
  • thumbv7r-none-eabihf
  • armv7a-none-eabi
  • armv7a-none-eabihf
  • thumbv7a-none-eabi
  • thumbv7a-none-eabihf
  • armv8r-none-eabihf
  • thumbv8r-none-eabihf

But I wouldn't block this PR on that - they can be added later.

and in particular for naked functions in that scenario
@folkertdevfolkertdev changed the title add tests for thumb calling arm codeadd tests for thumb interworkingMar 2, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I think this is ready then

@jieyouxujieyouxu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 5 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
Failed merges:
- #151864 (Implement AST -> HIR generics propagation in delegation)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 9 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 059ecc1...

Workflow: https://github.com/rust-lang/rust/actions/runs/22590534046

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153303.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 11 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 3600963...

Workflow: https://github.com/rust-lang/rust/actions/runs/22591476163

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153304.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors
rust-borsBot merged commit 6d16e3b into rust-lang:mainMar 2, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 2, 2026
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
rust-timer added a commit that referenced this pull request Mar 5, 2026
Rollup merge of #153396 - folkertdev:run-make-minicore, r=jieyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in #153153.
github-actionsBot pushed a commit to rust-lang/rust-analyzer that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/miri that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Mar 9, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
ghaaj pushed a commit to ghaaj/polygrammar that referenced this pull request Aug 7, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- rust-lang/rust#153153 (add tests for thumb interworking)
- rust-lang/rust#151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- rust-lang/rust#151962 (Fix next-solver ICE on PointeeSized goals)
- rust-lang/rust#153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- rust-lang/rust#153161 (Rejig `rustc_with_all_queries!`)
- rust-lang/rust#153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- rust-lang/rust#153273 (vec/mod.rs: add missing period in "ie." in docs)
- rust-lang/rust#153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- rust-lang/rust#153293 (library: std: process: skip tests on Hermit)
- rust-lang/rust#153301 (Do not ping kobzol on rustc-dev-guide changes)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-makeArea: port run-make Makefiles to rmake.rsS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk

7 participants

@folkertdev@rustbot@rust-log-analyzer@theemathas@thejpster@jieyouxu@JonathanBrouwer
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

add tests for thumb interworking - #153153

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm
Mar 2, 2026
Merged

add tests for thumb interworking#153153
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes#151946

thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.

cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise

I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.

@rustbot

Copy link
Copy Markdown
Collaborator

The run-make-support library was changed

cc @jieyouxu

@rustbotrustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 26, 2026
@rust-log-analyzer

This comment has been minimized.

@rustbotrustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 26, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

@theemathas why was this closed?

@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I'm assuming it was closed on accident then?

@folkertdevfolkertdev reopened this Feb 27, 2026
@rustbotrustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 27, 2026
@theemathas

Copy link
Copy Markdown
Contributor

I've never seen this PR before. Don't know what happened.

@thejpster

Copy link
Copy Markdown
Contributor

I don’t know the details of the test infra so I can’t comment there. The examples look good but perhaps:

  • it could be renamed ‘thumb-interworking’ because that’s the target flag
  • The a32 and t32 files can be merged into one, with entry calling six functions
  • The test could be extended to all targets with thumb-interworking enabled?

I also wondered if the hash in the thunk name was stable or if we needed to Wildcard it?

Comment threadtests/run-make/thumb-calling-arm/rmake.rs Outdated
@jieyouxu

Copy link
Copy Markdown
Member

@rustbot author

@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2026
@rustbot

Copy link
Copy Markdown
Collaborator

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@folkertdevfolkertdev left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Good points @thejpster, I've renamed and added tests using the arm targets.

@rustbot ready

View changes since this review

Comment threadtests/run-make/thumb-interworking/rmake.rs
@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 1, 2026
@thejpster

thejpster commented Mar 1, 2026

Copy link
Copy Markdown
Contributor

Looks good to me. You could also add:

  • armv6-none-eabi
  • armv6-none-eabihf
  • thumbv6-none-eabi
  • armv7r-none-eabi
  • armv7r-none-eabihf
  • thumbv7r-none-eabi
  • thumbv7r-none-eabihf
  • armv7a-none-eabi
  • armv7a-none-eabihf
  • thumbv7a-none-eabi
  • thumbv7a-none-eabihf
  • armv8r-none-eabihf
  • thumbv8r-none-eabihf

But I wouldn't block this PR on that - they can be added later.

and in particular for naked functions in that scenario
@folkertdevfolkertdev changed the title add tests for thumb calling arm codeadd tests for thumb interworkingMar 2, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I think this is ready then

@jieyouxujieyouxu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 5 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
Failed merges:
- #151864 (Implement AST -> HIR generics propagation in delegation)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 9 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 059ecc1...

Workflow: https://github.com/rust-lang/rust/actions/runs/22590534046

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153303.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 11 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 3600963...

Workflow: https://github.com/rust-lang/rust/actions/runs/22591476163

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153304.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors
rust-borsBot merged commit 6d16e3b into rust-lang:mainMar 2, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 2, 2026
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
rust-timer added a commit that referenced this pull request Mar 5, 2026
Rollup merge of #153396 - folkertdev:run-make-minicore, r=jieyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in #153153.
github-actionsBot pushed a commit to rust-lang/rust-analyzer that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/miri that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Mar 9, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
ghaaj pushed a commit to ghaaj/polygrammar that referenced this pull request Aug 7, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- rust-lang/rust#153153 (add tests for thumb interworking)
- rust-lang/rust#151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- rust-lang/rust#151962 (Fix next-solver ICE on PointeeSized goals)
- rust-lang/rust#153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- rust-lang/rust#153161 (Rejig `rustc_with_all_queries!`)
- rust-lang/rust#153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- rust-lang/rust#153273 (vec/mod.rs: add missing period in "ie." in docs)
- rust-lang/rust#153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- rust-lang/rust#153293 (library: std: process: skip tests on Hermit)
- rust-lang/rust#153301 (Do not ping kobzol on rustc-dev-guide changes)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-makeArea: port run-make Makefiles to rmake.rsS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk

7 participants

@folkertdev@rustbot@rust-log-analyzer@theemathas@thejpster@jieyouxu@JonathanBrouwer
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

add tests for thumb interworking - #153153

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm
Mar 2, 2026
Merged

add tests for thumb interworking#153153
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes#151946

thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.

cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise

I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.

@rustbot

Copy link
Copy Markdown
Collaborator

The run-make-support library was changed

cc @jieyouxu

@rustbotrustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 26, 2026
@rust-log-analyzer

This comment has been minimized.

@rustbotrustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 26, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

@theemathas why was this closed?

@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I'm assuming it was closed on accident then?

@folkertdevfolkertdev reopened this Feb 27, 2026
@rustbotrustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 27, 2026
@theemathas

Copy link
Copy Markdown
Contributor

I've never seen this PR before. Don't know what happened.

@thejpster

Copy link
Copy Markdown
Contributor

I don’t know the details of the test infra so I can’t comment there. The examples look good but perhaps:

  • it could be renamed ‘thumb-interworking’ because that’s the target flag
  • The a32 and t32 files can be merged into one, with entry calling six functions
  • The test could be extended to all targets with thumb-interworking enabled?

I also wondered if the hash in the thunk name was stable or if we needed to Wildcard it?

Comment threadtests/run-make/thumb-calling-arm/rmake.rs Outdated
@jieyouxu

Copy link
Copy Markdown
Member

@rustbot author

@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2026
@rustbot

Copy link
Copy Markdown
Collaborator

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@folkertdevfolkertdev left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Good points @thejpster, I've renamed and added tests using the arm targets.

@rustbot ready

View changes since this review

Comment threadtests/run-make/thumb-interworking/rmake.rs
@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 1, 2026
@thejpster

thejpster commented Mar 1, 2026

Copy link
Copy Markdown
Contributor

Looks good to me. You could also add:

  • armv6-none-eabi
  • armv6-none-eabihf
  • thumbv6-none-eabi
  • armv7r-none-eabi
  • armv7r-none-eabihf
  • thumbv7r-none-eabi
  • thumbv7r-none-eabihf
  • armv7a-none-eabi
  • armv7a-none-eabihf
  • thumbv7a-none-eabi
  • thumbv7a-none-eabihf
  • armv8r-none-eabihf
  • thumbv8r-none-eabihf

But I wouldn't block this PR on that - they can be added later.

and in particular for naked functions in that scenario
@folkertdevfolkertdev changed the title add tests for thumb calling arm codeadd tests for thumb interworkingMar 2, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I think this is ready then

@jieyouxujieyouxu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 5 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
Failed merges:
- #151864 (Implement AST -> HIR generics propagation in delegation)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 9 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 059ecc1...

Workflow: https://github.com/rust-lang/rust/actions/runs/22590534046

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153303.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 11 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 3600963...

Workflow: https://github.com/rust-lang/rust/actions/runs/22591476163

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153304.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors
rust-borsBot merged commit 6d16e3b into rust-lang:mainMar 2, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 2, 2026
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
rust-timer added a commit that referenced this pull request Mar 5, 2026
Rollup merge of #153396 - folkertdev:run-make-minicore, r=jieyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in #153153.
github-actionsBot pushed a commit to rust-lang/rust-analyzer that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/miri that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Mar 9, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
ghaaj pushed a commit to ghaaj/polygrammar that referenced this pull request Aug 7, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- rust-lang/rust#153153 (add tests for thumb interworking)
- rust-lang/rust#151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- rust-lang/rust#151962 (Fix next-solver ICE on PointeeSized goals)
- rust-lang/rust#153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- rust-lang/rust#153161 (Rejig `rustc_with_all_queries!`)
- rust-lang/rust#153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- rust-lang/rust#153273 (vec/mod.rs: add missing period in "ie." in docs)
- rust-lang/rust#153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- rust-lang/rust#153293 (library: std: process: skip tests on Hermit)
- rust-lang/rust#153301 (Do not ping kobzol on rustc-dev-guide changes)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-makeArea: port run-make Makefiles to rmake.rsS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk

7 participants

@folkertdev@rustbot@rust-log-analyzer@theemathas@thejpster@jieyouxu@JonathanBrouwer
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

add tests for thumb interworking - #153153

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm
Mar 2, 2026
Merged

add tests for thumb interworking#153153
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes#151946

thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.

cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise

I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.

@rustbot

Copy link
Copy Markdown
Collaborator

The run-make-support library was changed

cc @jieyouxu

@rustbotrustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 26, 2026
@rust-log-analyzer

This comment has been minimized.

@rustbotrustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 26, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

@theemathas why was this closed?

@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I'm assuming it was closed on accident then?

@folkertdevfolkertdev reopened this Feb 27, 2026
@rustbotrustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 27, 2026
@theemathas

Copy link
Copy Markdown
Contributor

I've never seen this PR before. Don't know what happened.

@thejpster

Copy link
Copy Markdown
Contributor

I don’t know the details of the test infra so I can’t comment there. The examples look good but perhaps:

  • it could be renamed ‘thumb-interworking’ because that’s the target flag
  • The a32 and t32 files can be merged into one, with entry calling six functions
  • The test could be extended to all targets with thumb-interworking enabled?

I also wondered if the hash in the thunk name was stable or if we needed to Wildcard it?

Comment threadtests/run-make/thumb-calling-arm/rmake.rs Outdated
@jieyouxu

Copy link
Copy Markdown
Member

@rustbot author

@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2026
@rustbot

Copy link
Copy Markdown
Collaborator

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@folkertdevfolkertdev left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Good points @thejpster, I've renamed and added tests using the arm targets.

@rustbot ready

View changes since this review

Comment threadtests/run-make/thumb-interworking/rmake.rs
@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 1, 2026
@thejpster

thejpster commented Mar 1, 2026

Copy link
Copy Markdown
Contributor

Looks good to me. You could also add:

  • armv6-none-eabi
  • armv6-none-eabihf
  • thumbv6-none-eabi
  • armv7r-none-eabi
  • armv7r-none-eabihf
  • thumbv7r-none-eabi
  • thumbv7r-none-eabihf
  • armv7a-none-eabi
  • armv7a-none-eabihf
  • thumbv7a-none-eabi
  • thumbv7a-none-eabihf
  • armv8r-none-eabihf
  • thumbv8r-none-eabihf

But I wouldn't block this PR on that - they can be added later.

and in particular for naked functions in that scenario
@folkertdevfolkertdev changed the title add tests for thumb calling arm codeadd tests for thumb interworkingMar 2, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I think this is ready then

@jieyouxujieyouxu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 5 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
Failed merges:
- #151864 (Implement AST -> HIR generics propagation in delegation)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 9 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 059ecc1...

Workflow: https://github.com/rust-lang/rust/actions/runs/22590534046

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153303.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 11 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 3600963...

Workflow: https://github.com/rust-lang/rust/actions/runs/22591476163

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153304.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors
rust-borsBot merged commit 6d16e3b into rust-lang:mainMar 2, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 2, 2026
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
rust-timer added a commit that referenced this pull request Mar 5, 2026
Rollup merge of #153396 - folkertdev:run-make-minicore, r=jieyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in #153153.
github-actionsBot pushed a commit to rust-lang/rust-analyzer that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/miri that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Mar 9, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
ghaaj pushed a commit to ghaaj/polygrammar that referenced this pull request Aug 7, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- rust-lang/rust#153153 (add tests for thumb interworking)
- rust-lang/rust#151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- rust-lang/rust#151962 (Fix next-solver ICE on PointeeSized goals)
- rust-lang/rust#153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- rust-lang/rust#153161 (Rejig `rustc_with_all_queries!`)
- rust-lang/rust#153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- rust-lang/rust#153273 (vec/mod.rs: add missing period in "ie." in docs)
- rust-lang/rust#153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- rust-lang/rust#153293 (library: std: process: skip tests on Hermit)
- rust-lang/rust#153301 (Do not ping kobzol on rustc-dev-guide changes)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-makeArea: port run-make Makefiles to rmake.rsS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk

7 participants

@folkertdev@rustbot@rust-log-analyzer@theemathas@thejpster@jieyouxu@JonathanBrouwer
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

add tests for thumb interworking - #153153

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm
Mar 2, 2026
Merged

add tests for thumb interworking#153153
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes#151946

thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.

cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise

I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.

@rustbot

Copy link
Copy Markdown
Collaborator

The run-make-support library was changed

cc @jieyouxu

@rustbotrustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 26, 2026
@rust-log-analyzer

This comment has been minimized.

@rustbotrustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 26, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

@theemathas why was this closed?

@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I'm assuming it was closed on accident then?

@folkertdevfolkertdev reopened this Feb 27, 2026
@rustbotrustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 27, 2026
@theemathas

Copy link
Copy Markdown
Contributor

I've never seen this PR before. Don't know what happened.

@thejpster

Copy link
Copy Markdown
Contributor

I don’t know the details of the test infra so I can’t comment there. The examples look good but perhaps:

  • it could be renamed ‘thumb-interworking’ because that’s the target flag
  • The a32 and t32 files can be merged into one, with entry calling six functions
  • The test could be extended to all targets with thumb-interworking enabled?

I also wondered if the hash in the thunk name was stable or if we needed to Wildcard it?

Comment threadtests/run-make/thumb-calling-arm/rmake.rs Outdated
@jieyouxu

Copy link
Copy Markdown
Member

@rustbot author

@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2026
@rustbot

Copy link
Copy Markdown
Collaborator

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@folkertdevfolkertdev left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Good points @thejpster, I've renamed and added tests using the arm targets.

@rustbot ready

View changes since this review

Comment threadtests/run-make/thumb-interworking/rmake.rs
@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 1, 2026
@thejpster

thejpster commented Mar 1, 2026

Copy link
Copy Markdown
Contributor

Looks good to me. You could also add:

  • armv6-none-eabi
  • armv6-none-eabihf
  • thumbv6-none-eabi
  • armv7r-none-eabi
  • armv7r-none-eabihf
  • thumbv7r-none-eabi
  • thumbv7r-none-eabihf
  • armv7a-none-eabi
  • armv7a-none-eabihf
  • thumbv7a-none-eabi
  • thumbv7a-none-eabihf
  • armv8r-none-eabihf
  • thumbv8r-none-eabihf

But I wouldn't block this PR on that - they can be added later.

and in particular for naked functions in that scenario
@folkertdevfolkertdev changed the title add tests for thumb calling arm codeadd tests for thumb interworkingMar 2, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I think this is ready then

@jieyouxujieyouxu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 5 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
Failed merges:
- #151864 (Implement AST -> HIR generics propagation in delegation)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 9 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 059ecc1...

Workflow: https://github.com/rust-lang/rust/actions/runs/22590534046

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153303.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 11 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 3600963...

Workflow: https://github.com/rust-lang/rust/actions/runs/22591476163

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153304.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors
rust-borsBot merged commit 6d16e3b into rust-lang:mainMar 2, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 2, 2026
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
rust-timer added a commit that referenced this pull request Mar 5, 2026
Rollup merge of #153396 - folkertdev:run-make-minicore, r=jieyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in #153153.
github-actionsBot pushed a commit to rust-lang/rust-analyzer that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/miri that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Mar 9, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
ghaaj pushed a commit to ghaaj/polygrammar that referenced this pull request Aug 7, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- rust-lang/rust#153153 (add tests for thumb interworking)
- rust-lang/rust#151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- rust-lang/rust#151962 (Fix next-solver ICE on PointeeSized goals)
- rust-lang/rust#153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- rust-lang/rust#153161 (Rejig `rustc_with_all_queries!`)
- rust-lang/rust#153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- rust-lang/rust#153273 (vec/mod.rs: add missing period in "ie." in docs)
- rust-lang/rust#153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- rust-lang/rust#153293 (library: std: process: skip tests on Hermit)
- rust-lang/rust#153301 (Do not ping kobzol on rustc-dev-guide changes)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-makeArea: port run-make Makefiles to rmake.rsS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk

7 participants

@folkertdev@rustbot@rust-log-analyzer@theemathas@thejpster@jieyouxu@JonathanBrouwer
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

add tests for thumb interworking - #153153

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm
Mar 2, 2026
Merged

add tests for thumb interworking#153153
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes#151946

thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.

cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise

I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.

@rustbot

Copy link
Copy Markdown
Collaborator

The run-make-support library was changed

cc @jieyouxu

@rustbotrustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 26, 2026
@rust-log-analyzer

This comment has been minimized.

@rustbotrustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 26, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

@theemathas why was this closed?

@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I'm assuming it was closed on accident then?

@folkertdevfolkertdev reopened this Feb 27, 2026
@rustbotrustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 27, 2026
@theemathas

Copy link
Copy Markdown
Contributor

I've never seen this PR before. Don't know what happened.

@thejpster

Copy link
Copy Markdown
Contributor

I don’t know the details of the test infra so I can’t comment there. The examples look good but perhaps:

  • it could be renamed ‘thumb-interworking’ because that’s the target flag
  • The a32 and t32 files can be merged into one, with entry calling six functions
  • The test could be extended to all targets with thumb-interworking enabled?

I also wondered if the hash in the thunk name was stable or if we needed to Wildcard it?

Comment threadtests/run-make/thumb-calling-arm/rmake.rs Outdated
@jieyouxu

Copy link
Copy Markdown
Member

@rustbot author

@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2026
@rustbot

Copy link
Copy Markdown
Collaborator

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@folkertdevfolkertdev left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Good points @thejpster, I've renamed and added tests using the arm targets.

@rustbot ready

View changes since this review

Comment threadtests/run-make/thumb-interworking/rmake.rs
@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 1, 2026
@thejpster

thejpster commented Mar 1, 2026

Copy link
Copy Markdown
Contributor

Looks good to me. You could also add:

  • armv6-none-eabi
  • armv6-none-eabihf
  • thumbv6-none-eabi
  • armv7r-none-eabi
  • armv7r-none-eabihf
  • thumbv7r-none-eabi
  • thumbv7r-none-eabihf
  • armv7a-none-eabi
  • armv7a-none-eabihf
  • thumbv7a-none-eabi
  • thumbv7a-none-eabihf
  • armv8r-none-eabihf
  • thumbv8r-none-eabihf

But I wouldn't block this PR on that - they can be added later.

and in particular for naked functions in that scenario
@folkertdevfolkertdev changed the title add tests for thumb calling arm codeadd tests for thumb interworkingMar 2, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I think this is ready then

@jieyouxujieyouxu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 5 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
Failed merges:
- #151864 (Implement AST -> HIR generics propagation in delegation)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 9 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 059ecc1...

Workflow: https://github.com/rust-lang/rust/actions/runs/22590534046

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153303.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 11 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 3600963...

Workflow: https://github.com/rust-lang/rust/actions/runs/22591476163

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153304.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors
rust-borsBot merged commit 6d16e3b into rust-lang:mainMar 2, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 2, 2026
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
rust-timer added a commit that referenced this pull request Mar 5, 2026
Rollup merge of #153396 - folkertdev:run-make-minicore, r=jieyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in #153153.
github-actionsBot pushed a commit to rust-lang/rust-analyzer that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/miri that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Mar 9, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
ghaaj pushed a commit to ghaaj/polygrammar that referenced this pull request Aug 7, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- rust-lang/rust#153153 (add tests for thumb interworking)
- rust-lang/rust#151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- rust-lang/rust#151962 (Fix next-solver ICE on PointeeSized goals)
- rust-lang/rust#153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- rust-lang/rust#153161 (Rejig `rustc_with_all_queries!`)
- rust-lang/rust#153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- rust-lang/rust#153273 (vec/mod.rs: add missing period in "ie." in docs)
- rust-lang/rust#153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- rust-lang/rust#153293 (library: std: process: skip tests on Hermit)
- rust-lang/rust#153301 (Do not ping kobzol on rustc-dev-guide changes)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-makeArea: port run-make Makefiles to rmake.rsS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk

7 participants

@folkertdev@rustbot@rust-log-analyzer@theemathas@thejpster@jieyouxu@JonathanBrouwer
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

add tests for thumb interworking - #153153

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm
Mar 2, 2026
Merged

add tests for thumb interworking#153153
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes#151946

thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.

cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise

I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.

@rustbot

Copy link
Copy Markdown
Collaborator

The run-make-support library was changed

cc @jieyouxu

@rustbotrustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 26, 2026
@rust-log-analyzer

This comment has been minimized.

@rustbotrustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 26, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

@theemathas why was this closed?

@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I'm assuming it was closed on accident then?

@folkertdevfolkertdev reopened this Feb 27, 2026
@rustbotrustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 27, 2026
@theemathas

Copy link
Copy Markdown
Contributor

I've never seen this PR before. Don't know what happened.

@thejpster

Copy link
Copy Markdown
Contributor

I don’t know the details of the test infra so I can’t comment there. The examples look good but perhaps:

  • it could be renamed ‘thumb-interworking’ because that’s the target flag
  • The a32 and t32 files can be merged into one, with entry calling six functions
  • The test could be extended to all targets with thumb-interworking enabled?

I also wondered if the hash in the thunk name was stable or if we needed to Wildcard it?

Comment threadtests/run-make/thumb-calling-arm/rmake.rs Outdated
@jieyouxu

Copy link
Copy Markdown
Member

@rustbot author

@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2026
@rustbot

Copy link
Copy Markdown
Collaborator

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@folkertdevfolkertdev left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Good points @thejpster, I've renamed and added tests using the arm targets.

@rustbot ready

View changes since this review

Comment threadtests/run-make/thumb-interworking/rmake.rs
@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 1, 2026
@thejpster

thejpster commented Mar 1, 2026

Copy link
Copy Markdown
Contributor

Looks good to me. You could also add:

  • armv6-none-eabi
  • armv6-none-eabihf
  • thumbv6-none-eabi
  • armv7r-none-eabi
  • armv7r-none-eabihf
  • thumbv7r-none-eabi
  • thumbv7r-none-eabihf
  • armv7a-none-eabi
  • armv7a-none-eabihf
  • thumbv7a-none-eabi
  • thumbv7a-none-eabihf
  • armv8r-none-eabihf
  • thumbv8r-none-eabihf

But I wouldn't block this PR on that - they can be added later.

and in particular for naked functions in that scenario
@folkertdevfolkertdev changed the title add tests for thumb calling arm codeadd tests for thumb interworkingMar 2, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I think this is ready then

@jieyouxujieyouxu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 5 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
Failed merges:
- #151864 (Implement AST -> HIR generics propagation in delegation)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 9 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 059ecc1...

Workflow: https://github.com/rust-lang/rust/actions/runs/22590534046

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153303.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 11 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 3600963...

Workflow: https://github.com/rust-lang/rust/actions/runs/22591476163

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153304.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors
rust-borsBot merged commit 6d16e3b into rust-lang:mainMar 2, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 2, 2026
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
rust-timer added a commit that referenced this pull request Mar 5, 2026
Rollup merge of #153396 - folkertdev:run-make-minicore, r=jieyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in #153153.
github-actionsBot pushed a commit to rust-lang/rust-analyzer that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/miri that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Mar 9, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
ghaaj pushed a commit to ghaaj/polygrammar that referenced this pull request Aug 7, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- rust-lang/rust#153153 (add tests for thumb interworking)
- rust-lang/rust#151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- rust-lang/rust#151962 (Fix next-solver ICE on PointeeSized goals)
- rust-lang/rust#153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- rust-lang/rust#153161 (Rejig `rustc_with_all_queries!`)
- rust-lang/rust#153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- rust-lang/rust#153273 (vec/mod.rs: add missing period in "ie." in docs)
- rust-lang/rust#153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- rust-lang/rust#153293 (library: std: process: skip tests on Hermit)
- rust-lang/rust#153301 (Do not ping kobzol on rustc-dev-guide changes)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-makeArea: port run-make Makefiles to rmake.rsS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk

7 participants

@folkertdev@rustbot@rust-log-analyzer@theemathas@thejpster@jieyouxu@JonathanBrouwer
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

add tests for thumb interworking - #153153

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm
Mar 2, 2026
Merged

add tests for thumb interworking#153153
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
folkertdev:thumb-and-arm

Conversation

@folkertdev

Copy link
Copy Markdown
Contributor

fixes#151946

thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.

cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise

I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.

@rustbot

Copy link
Copy Markdown
Collaborator

The run-make-support library was changed

cc @jieyouxu

@rustbotrustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Feb 26, 2026
@rust-log-analyzer

This comment has been minimized.

@rustbotrustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 26, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

@theemathas why was this closed?

@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I'm assuming it was closed on accident then?

@folkertdevfolkertdev reopened this Feb 27, 2026
@rustbotrustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Feb 27, 2026
@theemathas

Copy link
Copy Markdown
Contributor

I've never seen this PR before. Don't know what happened.

@thejpster

Copy link
Copy Markdown
Contributor

I don’t know the details of the test infra so I can’t comment there. The examples look good but perhaps:

  • it could be renamed ‘thumb-interworking’ because that’s the target flag
  • The a32 and t32 files can be merged into one, with entry calling six functions
  • The test could be extended to all targets with thumb-interworking enabled?

I also wondered if the hash in the thunk name was stable or if we needed to Wildcard it?

Comment threadtests/run-make/thumb-calling-arm/rmake.rs Outdated
@jieyouxu

Copy link
Copy Markdown
Member

@rustbot author

@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Feb 28, 2026
@rustbot

Copy link
Copy Markdown
Collaborator

Reminder, once the PR becomes ready for a review, use @rustbot ready.

@folkertdevfolkertdev left a comment

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Good points @thejpster, I've renamed and added tests using the arm targets.

@rustbot ready

View changes since this review

Comment threadtests/run-make/thumb-interworking/rmake.rs
@rustbotrustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Mar 1, 2026
@thejpster

thejpster commented Mar 1, 2026

Copy link
Copy Markdown
Contributor

Looks good to me. You could also add:

  • armv6-none-eabi
  • armv6-none-eabihf
  • thumbv6-none-eabi
  • armv7r-none-eabi
  • armv7r-none-eabihf
  • thumbv7r-none-eabi
  • thumbv7r-none-eabihf
  • armv7a-none-eabi
  • armv7a-none-eabihf
  • thumbv7a-none-eabi
  • thumbv7a-none-eabihf
  • armv8r-none-eabihf
  • thumbv8r-none-eabihf

But I wouldn't block this PR on that - they can be added later.

and in particular for naked functions in that scenario
@folkertdevfolkertdev changed the title add tests for thumb calling arm codeadd tests for thumb interworkingMar 2, 2026
@folkertdev

Copy link
Copy Markdown
ContributorAuthor

I think this is ready then

@jieyouxujieyouxu left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 5 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
Failed merges:
- #151864 (Implement AST -> HIR generics propagation in delegation)
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 9 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 059ecc1...

Workflow: https://github.com/rust-lang/rust/actions/runs/22590534046

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixesrust-lang#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153303.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 11 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #149328 (Add `String<A>` type with custom allocator parameter)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

⌛ Testing commit 2d8ceee with merge 3600963...

Workflow: https://github.com/rust-lang/rust/actions/runs/22591476163

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
add tests for thumb interworking
fixes#151946
thumb programs (using a 16-bit instruction encoding) can call arm (32-bit instruction encoding) code. Doing so requires switching from thumb mode to arm mode, executing, then switching back. Test that this happens correctly, in particular for naked functions.
cc @thejpster can you confirm the output looks good here and that we're testing all of the relevant things
r? jieyouxu because this is doing some interesting things testing-wise
I believe that we need run-make here because we need to look at the assembly after the linker has run. It will correct calls from thumb to arm: depending on the thumb version this either uses a special instruction or inserts a call to a thunk that handles switching between thumb and arm mode.
@JonathanBrouwer

Copy link
Copy Markdown
Member

@bors yield
Yielding to enclosing rollup

@rust-bors

rust-borsBot commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153304.

rust-borsBot pushed a commit that referenced this pull request Mar 2, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- #153153 (add tests for thumb interworking)
- #151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- #151962 (Fix next-solver ICE on PointeeSized goals)
- #153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- #153161 (Rejig `rustc_with_all_queries!`)
- #153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- #153273 (vec/mod.rs: add missing period in "ie." in docs)
- #153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- #153293 (library: std: process: skip tests on Hermit)
- #153301 (Do not ping kobzol on rustc-dev-guide changes)
@rust-bors
rust-borsBot merged commit 6d16e3b into rust-lang:mainMar 2, 2026
11 of 12 checks passed
@rustbotrustbot added this to the 1.96.0 milestone Mar 2, 2026
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Mar 4, 2026
…eyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang#153153.
rust-timer added a commit that referenced this pull request Mar 5, 2026
Rollup merge of #153396 - folkertdev:run-make-minicore, r=jieyouxu
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in #153153.
github-actionsBot pushed a commit to rust-lang/rust-analyzer that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/miri that referenced this pull request Mar 5, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
github-actionsBot pushed a commit to rust-lang/rustc-dev-guide that referenced this pull request Mar 9, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
ghaaj pushed a commit to ghaaj/polygrammar that referenced this pull request Aug 7, 2026
use `minicore` in some `run-make` tests
r? jieyouxu
This manually builds `minicore` in two more `rmake` tests that rolled their own before, and adds a helper for the path of the minicore source. I tried adding a true minicore helper in `run_make_support` but unfortunately the minicore build needs to inherit some (but probably not all) arguments of the final rustc invocation (notably `target` and `target_cpu`), so a one-size-fits-all helper doesn't really work as far as I can see.
For now with 3 uses this is probably fine, but there are probably other `run-make` tests that could use `minicore` but didn't document/simulate that.
follow-up to discussion in rust-lang/rust#153153.
flip1995 pushed a commit to flip1995/rust-clippy that referenced this pull request Aug 17, 2026
…uwer
Rollup of 10 pull requests
Successful merges:
- rust-lang/rust#153153 (add tests for thumb interworking)
- rust-lang/rust#151780 (Updated slice tests to pass for big endian hosts for `multiple-option-or-permutations.rs`)
- rust-lang/rust#151962 (Fix next-solver ICE on PointeeSized goals)
- rust-lang/rust#153015 (core: make atomic primitives type aliases of `Atomic<T>`)
- rust-lang/rust#153161 (Rejig `rustc_with_all_queries!`)
- rust-lang/rust#153191 ( don't emit `unused_results` lint for tuples of "trivial" types )
- rust-lang/rust#153273 (vec/mod.rs: add missing period in "ie." in docs)
- rust-lang/rust#153292 (tests: codegen-llvm: vec-calloc: do not require the uwtable attribute)
- rust-lang/rust#153293 (library: std: process: skip tests on Hermit)
- rust-lang/rust#153301 (Do not ping kobzol on rustc-dev-guide changes)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-run-makeArea: port run-make Makefiles to rmake.rsS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk

7 participants

@folkertdev@rustbot@rust-log-analyzer@theemathas@thejpster@jieyouxu@JonathanBrouwer