Skip to content

Mark functions as "readnone" or "readonly" #848

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.

Sign up for GitHub

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

Jump to bottom
Closed
pcwalton opened this issue Aug 19, 2011 · 1 comment
Closed

Mark functions as "readnone" or "readonly" #848

pcwalton opened this issue Aug 19, 2011 · 1 comment
Labels
A-codegen Area: Code generation E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Milestone
old 1.0 milestone

Comments

@pcwalton
Copy link
Contributor

LLVM can reason about purity and do nice things like CSE… if we give it the information.
@z0w0
Copy link
Contributor

z0w0 commented Feb 16, 2013

This is segfaulting when it tries to compile at stage2. Any idea what I'm doing wrong here @pcwalton?

keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
@bors
Auto merge of rust-lang#849 - cramertj:separate-fuchsia, r=alexcrichton
a72a79b 
Separate and Update Fuchsia

The first commit pulls Fuchsia out into its own directory, while the second commit updates the "open" flags as in rust-lang#848.

cc @smklein, @alexcrichton
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 26, 2020
@bjorn3
Implement #[track_caller]
38797f8 
Fixes rust-lang#848
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-codegen Area: Code generation E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
old 1.0 milestone
Development

No branches or pull requests
2 participants
@pcwalton @z0w0