This website requires JavaScript.
Explore
Help
Sign In
replica
/
hanchenye-llvm-project
Watch
2
Star
0
Fork
You've already forked hanchenye-llvm-project
0
Code
Issues
Pull Requests
Projects
Releases
Wiki
Activity
fc3d80bda1
hanchenye-llvm-project
/
lld
/
test
/
Driver
/
trivial-driver.test
6 lines
96 B
Plaintext
Raw
Normal View
History
Unescape
Escape
This is my Driver refactoring patch. The major changes are: 1) LinkerOptions has been merged into TargetInfo 2) LinkerInvocation has been merged into Driver 3) Drivers no longer convert arguments into an intermediate (core) argument list, but instead create a TargetInfo object and call setter methods on it. This is only how in-process linking would work. That is, you can programmatically set up a TargetInfo object which controls the linking. 4) Lots of tweaks to test suite to work with driver changes 5) Add the DarwinDriver 6) I heavily doxygen commented TargetInfo.h Things to do after this patch is committed: a) Consider renaming TargetInfo, given its new roll. b) Consider pulling the list of input files out of TargetInfo. This will enable in-process clients to create one TargetInfo the re-use it with different input file lists. c) Work out a way for Drivers to format the warnings and error done in core linking. llvm-svn: 178776
2013-04-05 02:59:24 +08:00
RUN: lld -flavor gnu --help | FileCheck %s
[Driver] Add test. llvm-svn: 169721
2012-12-10 10:53:10 +08:00
This is my Driver refactoring patch. The major changes are: 1) LinkerOptions has been merged into TargetInfo 2) LinkerInvocation has been merged into Driver 3) Drivers no longer convert arguments into an intermediate (core) argument list, but instead create a TargetInfo object and call setter methods on it. This is only how in-process linking would work. That is, you can programmatically set up a TargetInfo object which controls the linking. 4) Lots of tweaks to test suite to work with driver changes 5) Add the DarwinDriver 6) I heavily doxygen commented TargetInfo.h Things to do after this patch is committed: a) Consider renaming TargetInfo, given its new roll. b) Consider pulling the list of input files out of TargetInfo. This will enable in-process clients to create one TargetInfo the re-use it with different input file lists. c) Work out a way for Drivers to format the warnings and error done in core linking. llvm-svn: 178776
2013-04-05 02:59:24 +08:00
CHECK: -L
CHECK: -emit-yaml
CHECK: --noinhibit-exec