Skip to content
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

Update LLVM to fix crash on Emscripten targets #67976

Closed
wants to merge 1 commit into from

Conversation

tlively
Copy link
Contributor

@tlively tlively commented Jan 7, 2020

Pulls in a bug fix from upstream to resolve #66308. Also adds a small
Rust regression test.

r? @alexcrichton

Pulls in a bug fix from upstream to resolve rust-lang#66308. Also adds a small
Rust regression test.

r? @alexcrichton
@rust-highfive
Copy link
Collaborator

⚠️ Warning ⚠️

  • These commits modify submodules.

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jan 7, 2020
@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Contributor

bors commented Jan 7, 2020

📌 Commit 914befe has been approved by alexcrichton

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 7, 2020
@cuviper
Copy link
Member

cuviper commented Jan 8, 2020

FWIW, #68030 is rebasing to a new branch for LLVM 9.0.1, but I did include your backport.

@Centril
Copy link
Contributor

Centril commented Jan 8, 2020

@bors rollup=never

@bors
Copy link
Contributor

bors commented Jan 18, 2020

⌛ Testing commit 914befe with merge 40e44026d396ad251e58e51891e1bb51137db51b...

@rust-highfive
Copy link
Collaborator

Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @TimNN. (Feature Requests)

@bors
Copy link
Contributor

bors commented Jan 18, 2020

💔 Test failed - checks-azure

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jan 18, 2020
@bors
Copy link
Contributor

bors commented Jan 19, 2020

☔ The latest upstream changes (presumably #68030) made this pull request unmergeable. Please resolve the merge conflicts.

@nikic
Copy link
Contributor

nikic commented Jan 19, 2020

The patch has been picked up as part of #68030, so this can be reduced to just the test case.

@tlively
Copy link
Contributor Author

tlively commented Jan 21, 2020

Given that there are already regression tests for this bug in LLVM, I don't feel the Rust test is too important to have. I'll just close this PR.

@tlively tlively closed this Jan 21, 2020
@tlively tlively deleted the emcc-codegen-sigsegv-66308 branch January 21, 2020 19:09
@tlively tlively restored the emcc-codegen-sigsegv-66308 branch January 24, 2020 19:09
@tlively
Copy link
Contributor Author

tlively commented Jan 24, 2020

@alexcrichton I've pushed the new fix to the same branch, so we can either reopen this PR (and go straight to the head of the bors queue) or I can make a new PR. Which would you prefer?

@alexcrichton
Copy link
Member

I'm fine with either! The reopen button is grayed out for me though, so maybe a new PR for technical issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SIGSEGV compiling num-integer for asmjs-unknown-emscripten
7 participants