Use ".ll" as default suffix of LLVM assembly file
This commit is a follow up of Issue #1147. Althought there are some inconsistency about this naming convention in LLVM. For example, `clang' write LLVM assembly to a file with ".s" suffix, while both `llvm-dis' and `opt' write to files with ".ll" suffices. We think ".ll" makes more sense. Also rustc manual page is updated.
This commit is contained in:
parent
8857657640
commit
253242390c
@ -25,7 +25,8 @@ output filename for \fBfoo.rs\fR is otherwise \fBfoo\fR plus any
|
||||
platform-specific extension (when compiling a binary), a
|
||||
platform-specific name, e.g. \fBlibfoo.so\fR (when compiling a
|
||||
library), \fBfoo.o\fR (when using \fB-c\fR), \fBfoo.s\fR (when using
|
||||
\fB-S\fR) or \fBfoo.bc\fR (when using \fB--emit-llvm\fR), and
|
||||
\fB-S\fR) or \fBfoo.bc\fR (when using \fB--emit-llvm\fR), and \fBfoo.ll\fR
|
||||
(when using both \fB-S\fR and \fB--emit-llvm\fR).
|
||||
.TP
|
||||
\fB--lib\fR:
|
||||
Compile and link a library crate into a shared object.
|
||||
@ -82,7 +83,9 @@ Compile to assembly, but do not assemble or link.
|
||||
Compile and assemble, but do not link.
|
||||
.TP
|
||||
\fB--emit-llvm\fR:
|
||||
Generate llvm bitcode.
|
||||
Generate output files in LLVM format. When used with \fB-S\fR this generate LLVM
|
||||
intermediate language assembly files, otherwise this generates LLVM bitcode
|
||||
format object files.
|
||||
.TP
|
||||
\fB--save-temps\fR:
|
||||
For foo.rs, save generated bitcode before optimization to
|
||||
|
@ -477,7 +477,7 @@ fn build_output_filenames(ifile: str, ofile: option::t<str>,
|
||||
link::output_type_none. { "none" }
|
||||
link::output_type_bitcode. { "bc" }
|
||||
link::output_type_assembly. { "s" }
|
||||
link::output_type_llvm_assembly. { "s" }
|
||||
link::output_type_llvm_assembly. { "ll" }
|
||||
// Object and exe output both use the '.o' extension here
|
||||
link::output_type_object. | link::output_type_exe. {
|
||||
"o"
|
||||
|
Loading…
Reference in New Issue
Block a user