Skip to content

native_lib_path attribute #2218

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

Closed
brson opened this issue Apr 16, 2012 · 2 comments
Closed

native_lib_path attribute #2218

brson opened this issue Apr 16, 2012 · 2 comments
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) A-linkage Area: linking into static, shared libraries and binaries C-enhancement Category: An issue proposing an enhancement or a PR with one. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Apr 16, 2012

Add a crate attribute, #[native_lib_path = ""] to act as an official, possibly smarter, version of #[link_args = "-L something"]

@brson
Copy link
Contributor Author

brson commented Apr 16, 2012

Actually, since I'm planning (#2197) on making -L apply to both crates and native libs, maybe for now we should just add #[addl_lib_path] to add both to the crate and native paths.

@Aatch
Copy link
Contributor

Aatch commented May 6, 2013

I'm pretty sure this isn't valid any more.

Re-open if you disagree.

@Aatch Aatch closed this as completed May 6, 2013
bors added a commit to rust-lang-ci/rust that referenced this issue Sep 22, 2022
…fJung

Optimize `SbTag::eq`

The code before generated really bad code with a branch.
This nudges LLVM towards being smarter and simply comparing
the integers.

See rust-lang/miri#2214 (comment)
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) A-linkage Area: linking into static, shared libraries and binaries C-enhancement Category: An issue proposing an enhancement or a PR with one. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

2 participants