-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Link with ld instead of gcc #1300
Comments
Might want to ask rafael about this; the impression I got is that the amount of "how to invoke ld properly" brains embedded in gcc is so immense and platform-specific as to be prohibitive. Or at least very, very painful. (IOW: "quantify a bit, before starting work on this"; I'm happy to be wrong) |
Would LLD be helpful? http://lld.llvm.org/ |
@kud1ing It would probably be incredibly helpful, but last I checked it was still very immature. |
Ah: "lld is in its early stages of development." |
Does libclang expose a way to drive the linker? It seems like it would. |
I'm considering removing E-easy because figuring out all the details of each systems' linker isn't going to be that easy. |
Closing in favour of #9367. |
Rename the build/ directory to dist/
It seems silly to have this runtime dependency on gcc just for calling the linker. Calling ld will make #[link_args] and --link_args more accurate. Right now they would be better described as gcc_args.
The text was updated successfully, but these errors were encountered: