-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Undefined reference to `__morestack' when compiling with -O #13625
Comments
sebcrozet
added a commit
to sebcrozet/kiss3d
that referenced
this issue
Apr 19, 2014
Version of rustc: rustc 0.11-pre (2c22ae4 2014-04-19 04:26:28 -0700) The last two examples fail to link because of rust-lang/rust#13625.
Can you paste the output of |
Output of
Output of
|
bors
added a commit
that referenced
this issue
Apr 19, 2014
In upgrading LLVM, only rust functions had the "split-stack" attribute added. This commit changes the addition of LLVM's "split-stack" attribute to *always* occur and then we remove it sometimes if the "no_split_stack" rust attribute is present. Closes #13625
Manishearth
pushed a commit
to Manishearth/rust
that referenced
this issue
Nov 23, 2022
internal: Update proc-macro-srv tests Should have been included in rust-lang#13548, but I didn't notice as those tests aren't run in our CI. cc rust-lang#104454
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Nov 28, 2024
It's becoming more and more common to see people including markdown files in their code using `doc = include_str!("...")`, which is great. However, often there is no condition on this include, which is not great because it slows down compilation and might trigger recompilation if these files are updated. This lint aims at fixing this situation. changelog: Add new lint `doc_include_without_cfg`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since I updated the compiler to:
the following code:
fails to compile with optimizations on:
Compiling without
-O
does work fine.The text was updated successfully, but these errors were encountered: