Skip to content

Rustc pull #2200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jan 8, 2025
Merged

Rustc pull #2200

merged 6 commits into from
Jan 8, 2025

Conversation

Kobzol
Copy link
Contributor

@Kobzol Kobzol commented Jan 8, 2025

This pull is a bit special. I do it even though it's essentially empty, since we incorrectly used rebases on this repo instead of merges, which desynced the git history. So with this PR, I want to fix it ASAP. I had to manually rebase the rust-version file because there was a merge conflict.

Now the repo is configured such that only merges are possible, so this should not happen again in the future.

I tested that this worked on my fork, and I was able to do follow-up pulls and pushes, and the commit SHAs matched the filtered commits from Josh.

Kobzol and others added 6 commits January 5, 2025 18:12
rustc-dev-guide subtree update

This PR performs the first update of rustc-dev-guide code from its repository.

r? `@BoxyUwU`
add m68k-unknown-none-elf target

r? `@workingjubilee`

The existing `m68k-unknown-linux-gnu` target builds `std` by default, requires atomics, and has a base cpu with an fpu. A smaller/more embedded target is desirable both to have a baseline target for the ISA, as well to make debugging easier for working on the llvm backend. Currently this target is using the `M68010` as the minimum CPU due, but as missing features are merged into the `M68k` llvm backend I am hoping to lower this further.

I have been able to build very small crates using a toolchain built against this target (together with a later version of `object`) using the configuration described in the target platform-support documentation, although getting anything of substantial complexity to build quickly hits errors in the llvm backend
…=the8472

Merge the intrinsic and user tests for `select_unpredictable`

[1] mentions that having a single test with `-Zmerge-functions=disabled` is preferable to having two separate tests.  Apply that to the new `select_unpredictable` test here.

[1]: rust-lang/rust#133964 (comment)
@Kobzol Kobzol merged commit 7d59cb3 into rust-lang:master Jan 8, 2025
1 check passed
@Kobzol Kobzol deleted the rustc-pull branch January 8, 2025 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants