Uh oh!
There was an error while loading. Please reload this page.
fix fastcall mangling for rust_psm_on_stack - #54
Merged
Conversation
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.
nagisa
commented
Jul 5, 2021
Member
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? |
nagisa
commented
Jul 5, 2021
Member
Published as 0.1.14 |
jeremyd2019
commented
Jul 18, 2021
ContributorAuthor
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... |
nagisa
commented
Jul 19, 2021
via email
Member
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>
.
|
nagisa
commented
Jul 19, 2021
via email
Member
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>
> .
>
|
jeremyd2019
commented
Jul 19, 2021
ContributorAuthor
Well, that updated it to 0.1.13 but I'm trying to get 0.1.14 |
mati865
commented
Jul 23, 2021
Member
@nagisa it's not actually published. When I go to https://crates.io/crates/psm/versions version |
Member
Ran Really sorry about that. |
mati865
commented
Jul 23, 2021
Member
No problem, it's easy to use git version in Cargo. |
jeremyd2019
commented
Jul 23, 2021
ContributorAuthor
Thanks, that got the Cargo.lock file to update through the command you gave. |
JohnTitor added a commit
to JohnTitor/rust
that referenced
this pull request
Aug 3, 2021
…Simulacrum Update stacker and psm crates Primarily to include rust-lang/stacker#54
camsteffen added a commit
to camsteffen/rust
that referenced
this pull request
Aug 19, 2021
…Simulacrum Update stacker and psm crates Primarily to include rust-lang/stacker#54
bors added a commit
to rust-lang-ci/rust
that referenced
this pull request
Aug 30, 2021
…mulacrum,nagisa Update stacker and psm crates Primarily to include rust-lang/stacker#54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.