rui314/mold
1
1
Fork 0
mirror of https://github.com/rui314/mold.git synced 2024-09-21 09:57:18 +03:00
Code Issues Projects Releases Wiki Activity

Include a version number to the --version message

Browse Source
This commit is contained in:
Rui Ueyama 2021-05-18 21:42:37 +09:00
parent 0f6c9ca2b8
commit ebe37ef642
3 changed files with 15 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Makefile
View File

@ -5,6 +5,7 @@ MIMALLOC_LIB = mimalloc/out/release/libmimalloc.a
CPPFLAGS = -g -Imimalloc/include -pthread -std=c++20 \
-Wno-deprecated-volatile -Wno-switch \
-DMOLD_VERSION=\"0.1\" \
-DGIT_HASH=\"$(shell git rev-parse HEAD)\" \
$(EXTRA_CPPFLAGS)
LDFLAGS = $(EXTRA_LDFLAGS)

12
cmdline.cc
View File

@ -353,6 +353,12 @@ static i64 get_default_thread_count() {
return std::min(n, 32);
}
template <typename E>
static void print_version(Context<E> &ctx) {
SyncOut(ctx) << "mold " << MOLD_VERSION << " ("
<< GIT_HASH << "; compatible with GNU ld)";
}
template <typename E>
void parse_nonpositional_args(Context<E> &ctx,
std::vector<std::string_view> &remaining) {
@ -365,13 +371,13 @@ void parse_nonpositional_args(Context<E> &ctx,
std::string_view arg;
if (read_flag(args, "v") || read_flag(args, "version")) {
SyncOut(ctx) << "mold " GIT_HASH " (compatible with GNU ld)";
print_version(ctx);
exit(0);
}
if (read_flag(args, "V")) {
SyncOut(ctx) << "mold " GIT_HASH " (compatible with GNU ld)\n"
<< " Supported emulations:\n elf_x86_64\n elf_i386";
print_version(ctx);
SyncOut(ctx) << " Supported emulations:\n elf_x86_64\n elf_i386";
exit(0);
}

10
docs/mold.1
View File

@ -52,7 +52,7 @@ functions to run \fBmold\fR if \fB/usr/bin/ld\fR is attempted to be
run.
.PP
If you don't want to use the \fB\-run\fR option, and if you are using
\fBclang\fR, you can pass \fB\-fuse\-ld=/absolute/path/to/mold\fR to
\fBclang\fR, you can pass \fB\-fuse\-ld\fR=\fI/absolute/path/to/mold\fR to
\fBclang\fR to used \fBmold\fR. If you are using \fBgcc\fR, it looks
like there's unfortunately no easy way (other than \fB\-run\fR) to
force it to use \fBmold\fR, as \fBgcc\fR doesn't take an arbitrary
@ -84,17 +84,17 @@ files appear on command line. They process input files from the first
input files, they maintain sets of defined and undefined symbols.
When visiting an archive file (\fB.a\fR files), they pull out object
files to resolve as many undefined symbols as possible and go on to
the next input file. If an object file wasn't pulled out from an
archive file, it will never have a chance for a second look.
the next input file. Object files that weren't pulled out will never
have a chance for a second look.
.PP
Due to this semantics, you usually had to add archive files at the end
Due to this semantics, you usually have to add archive files at the end
of a command line, so that when a linker reaches archive files, it
knows what symbols are remain undefined. If you put archive files at
the beginning of a command line, a linker doesn't have any undefined
symbol, and thus no object files will be pulled out from archives.
.PP
You can change the processing order by \fB\-\-start\-group\fR and
\fB\-\-end\-group\fR options, though they degrade the performance.
\fB\-\-end\-group\fR options, though they make a linker slower.
.PP
\fBmold\fR as well as LLVM \fBlld\fR linker take a different
approach. They memorize what symbols can be resolved from archive