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

Invoke gcc with -nodefaultlibs #12205

Merged
merged 1 commit into from
Feb 14, 2014
Merged

Conversation

alexcrichton
Copy link
Member

This will hopefully bring us closer to #11937. We're still using gcc's idea of
"startup files", but this should prevent us from leaking in dependencies that we
don't quite want (libgcc for example once compiler-rt is what we use).

@alexcrichton
Copy link
Member Author

Reopening now that #12027 has landed to see if having compiler-rt locally helps at all.

This will hopefully bring us closer to rust-lang#11937. We're still using gcc's idea of
"startup files", but this should prevent us from leaking in dependencies that we
don't quite want (libgcc for example once compiler-rt is what we use).
bors added a commit that referenced this pull request Feb 14, 2014
This will hopefully bring us closer to #11937. We're still using gcc's idea of
"startup files", but this should prevent us from leaking in dependencies that we
don't quite want (libgcc for example once compiler-rt is what we use).
@bors bors closed this Feb 14, 2014
@bors bors merged commit 28fa81a into rust-lang:master Feb 14, 2014
@alexcrichton alexcrichton deleted the nodefaultlibs branch February 14, 2014 21:58
flip1995 pushed a commit to flip1995/rust that referenced this pull request Feb 8, 2024
[`never_loop`]: recognize desugared `try` blocks

Fixes rust-lang#12205

The old code assumed that only blocks with an explicit label can be jumped to (using `break`). This is mostly correct except for `try` desugaring, where the `?` operator is rewritten to a `break` to that block, even without a label on the block. `Block::targeted_by_break` is a little more accurate than just checking if a block has a label in that regard, so we should just use that instead

changelog: [`never_loop`]: avoid linting when `?` is used inside of a try block
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