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

Output TIME_PASSES info in a format that doesn't confuse emacs #844

Closed
marijnh opened this issue Aug 19, 2011 · 2 comments
Closed

Output TIME_PASSES info in a format that doesn't confuse emacs #844

marijnh opened this issue Aug 19, 2011 · 2 comments
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@marijnh
Copy link
Contributor

marijnh commented Aug 19, 2011

Currently, it tries to interpret the timing messages as errors and gets upset. I'd like to turn on TIME_PASSES as a kind of progress bar, but that does not currently work as it makes navigating the errors very painful.
@brson
Copy link
Contributor

brson commented Mar 6, 2012

I don't see emacs being confused by the TIME_PASSES output. Is this fixed?

@marijnh
Copy link
Contributor Author

marijnh commented Mar 6, 2012

Yes, it's fixed.

@marijnh marijnh closed this as completed Mar 6, 2012
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
@bors
Auto merge of rust-lang#844 - dereckson:unix-agnosticity, r=malbarbo
55c03cd 
Use more convenient and UNIX-agnostic shebang

Pure sh scripts should use /bin/sh as it's available on every platform.

When using bash-specific features, use env to find it, as bash can
be installed in different places according the OS.
@venkag venkag mentioned this issue Feb 13, 2019
Closed
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 26, 2020
@bjorn3
Re-use cranelift_codegen::ir::Function for every function
1bb848d 
Fixes rust-lang#844
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marijnh @brson