fix fastcall mangling for rust_psm_on_stack #54
Conversation
jeremyd2019
changed the title
All but the label were `@16`, but the label itself was `@20`. This was causing an error trying to build a mingw-w64 (windows-gnu) rust using clang/lld.
|
Huh, I'm pretty sure we run tests for i686-pc-windows-gnu in CI. I wonder if its because the Windows' implementation actually uses the Fibers implementation and the toolchain used in the CI optimizes out the reference to the symbol, but not whatever toolchain you're using in msys2? |
|
Published as 0.1.14 |
Forgive my rust ignorance, but how do I use this when building rustc? There's a Cargo.lock file that references: I guess I can update the version to "0.1.14" but where do I find the checksum? This seems to be a file intended to be updated by cargo, but having not successfully built rust yet... |
|
cargo update -p pam?
…On Mon, 19 Jul 2021, 01:12 jeremyd2019, ***@***.***> wrote:
Published as 0.1.14
Forgive my rust ignorance, but how do I use this when building rustc?
There's a Cargo.lock file that references:
[[package]]
name = "psm"
version = "0.1.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "96e0536f6528466dbbbbe6b986c34175a8d0ff25b794c4bacda22e068cd2f2c5"
dependencies = [
"cc",
]
I guess I can update the version to "0.1.14" but where do I find the
checksum? This seems to be a file intended to be updated by cargo, but
having not successfully built rust yet...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#54 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFFZURM7VRYJSF53DVPCXLTYNGTZANCNFSM47Z3SOAA>
.
|
|
psm*
🪛 📱 ⌨️
…On Mon, 19 Jul 2021, 03:03 Simonas Kazlauskas, ***@***.***> wrote:
cargo update -p pam?
On Mon, 19 Jul 2021, 01:12 jeremyd2019, ***@***.***> wrote:
> Published as 0.1.14
>
> Forgive my rust ignorance, but how do I use this when building rustc?
> There's a Cargo.lock file that references:
>
> [[package]]
> name = "psm"
> version = "0.1.11"
> source = "registry+https://github.com/rust-lang/crates.io-index"
> checksum = "96e0536f6528466dbbbbe6b986c34175a8d0ff25b794c4bacda22e068cd2f2c5"
> dependencies = [
> "cc",
> ]
>
> I guess I can update the version to "0.1.14" but where do I find the
> checksum? This seems to be a file intended to be updated by cargo, but
> having not successfully built rust yet...
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#54 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAFFZURM7VRYJSF53DVPCXLTYNGTZANCNFSM47Z3SOAA>
> .
>
|
|
Well, that updated it to 0.1.13 but I'm trying to get 0.1.14 |
|
@nagisa it's not actually published. When I go to https://crates.io/crates/psm/versions version |
|
Ran Really sorry about that. |
|
No problem, it's easy to use git version in Cargo. |
|
Thanks, that got the Cargo.lock file to update through the command you gave. |
…Simulacrum Update stacker and psm crates Primarily to include rust-lang/stacker#54
…Simulacrum Update stacker and psm crates Primarily to include rust-lang/stacker#54
…mulacrum,nagisa Update stacker and psm crates Primarily to include rust-lang/stacker#54
All but the label were
@16, but the label itself was@20. This was causing an error trying to build a mingw-w64 (windows-gnu) rust using clang/lld.