Skip to content

Get rid of main.ll #992

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 Sep 28, 2011 · 1 comment
Closed

Get rid of main.ll #992

brson opened this issue Sep 28, 2011 · 1 comment
Labels
C-cleanup Category: PRs that clean code up or issues documenting cleanup. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@brson
Copy link
Contributor

brson commented Sep 28, 2011

This can easily be generated by rustc

@marijnh
Copy link
Contributor

marijnh commented Oct 14, 2011

I'd actually like to do the same with the intrinsics. Just have them be special cases in the compiler rather than yet another file that has to be worked around when changing things.

marijnh added a commit that referenced this issue Oct 20, 2011
This isn't needed now that our functions are cdecl (and was apparently
only still working by accident).

Issue #992
marijnh added a commit that referenced this issue Oct 20, 2011
I'll remove the actual file after I register a snapshot.

Issue #992
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
coastalwhite pushed a commit to coastalwhite/rust that referenced this issue Aug 5, 2023
celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
All changes were fairly straight forward, and they were due to the
following rustc changes:
  - A few member variable -> function refactoring.
  - Change to ty::AdtDef internal representation.
  - The function span_error now returns a value.
  - Added a new field to the return value of ptr_metadata_ty.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-cleanup Category: PRs that clean code up or issues documenting cleanup. 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