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.

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

decide whether function addresses are significant #8957

Closed
thestinger opened this issue Sep 3, 2013 · 2 comments
Closed

decide whether function addresses are significant #8957

thestinger opened this issue Sep 3, 2013 · 2 comments
Labels
I-slow Issue: Problems and improvements with respect to performance of generated code.
Milestone
1.0

Comments

@thestinger
Copy link
Contributor

If they are significant, we can't be merging functions completely with type_use, it would have to leave behind stubs. If they aren't significant, we should be marking all of them as unnamed_addr so that mergefunc will be allowed to merge them without leaving stubs.
@thestinger
Copy link
Contributor Author

Nominating for the backwards compatible milestone (well defined would work too).

@thestinger thestinger mentioned this issue Sep 4, 2013
Closed
@catamorphism
Copy link
Contributor

Accepted backwards-compatible

@thestinger thestinger mentioned this issue Sep 16, 2013
Closed
@brson brson closed this as completed in 2992720 Nov 1, 2013
Jarcho pushed a commit to Jarcho/rust that referenced this issue Aug 29, 2022
@bors
Auto merge of rust-lang#8957 - Jarcho:more_pass_merges, r=flip1995
477c16d 
More lint pass merges

changelog: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
I-slow Issue: Problems and improvements with respect to performance of generated code.
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
2 participants
@catamorphism @thestinger