| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
to optimize the cache and UVM faulting behavior
ok kettenis@
|
| |
|
|
|
|
|
| |
Tested in snaps and package builds
Tested on amd64 by naddy@
Tested on arm64 by patrick@
Tested on octeon by visa@
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Prepared with help from jsg@ and mortimer@
Tested on amd64 by bcallah@, krw@, naddy@
Tested on arm64 by patrick@
Tested on macppc by kettenis@
Tested on octeon by visa@
Tested on sparc64 by claudio@
|
| | |
|
| |
|
|
|
|
| |
Affects i386 and amd64 only.
ok deraadt@ kettenis@
|
| |
|
|
| |
specified; suggested by and ok kettenis@
|
| |
|
|
|
|
|
|
|
|
| |
Note that this will still produce binaries that have the read-only segment
placed before the executable segment. This means that on machines without
the NX bit, the read-only segment is now executable. However on machines
with an NX bit, the ordering used by lld means the program headers are no
longer executable since they are now part of the read-only segment.
ok deraadt@, naddy@
|
| | |
|
| |
|
|
|
| |
With fixes from mortimer@ (thanks!)
Tested by many, especially naddy@ (thanks!)
|
| | |
|
| |
|
|
|
|
| |
is referenced from code being linked.
ok deraadt@, naddy@, guenther@
|
| |
|
|
| |
From upstream r335090. ok guenther@
|
| |
|
|
|
|
|
| |
GNU linkers by convention supports both `--foo bar` and `--foo=bar` styles
for all long options that take arguments.
From upstream r326506. ok patrick@ kettenis@
|
| |
|
|
|
|
|
|
|
|
| |
the section to be at least as large as the entry size of the section.
This causes a later check that validates the alignment to fail if the
entry size isn't a power of two. This happens when building some of the
java support code in ports gcc. Fix this by sticking to the original
alignment if the entry size isn't a power of two.
ok guenther@, naddy@
|
| |
|
|
|
|
|
|
|
|
| |
makes no sense. Yes it breaks function address equality and therefore
the expectations of the standard C language. However declaring symbols
with protected visibility isn't standard C in the first place.
Fixes linking non-PIC/PIE code with lld on amd64.
ok millert@
|
| |
|
|
| |
tested by naddy@
|
| |
|
|
|
|
| |
section when linking, as we do when using ld from binutils.
ok mortimer@ deraadt@
|
| |
|
|
|
|
|
| |
linker script makes ld.lld(1) crash. This has been fixed in a different
(proper?) way upstream but backporting their fix is a bit too invasive.
ok patrick@
|
| |
|
|
|
|
| |
was used to compile and object
ok kettenis@
|
| | |
|
| | |
|
| |
|
|
| |
"where is the kaboom?" deraadt@
|
| |
|
|
|
|
| |
the generation of gap.o.
ok patrick@
|
| |
|
|
|
|
|
|
| |
more closer to GNU linkers. This should help with autoconf/libtool
compatibility in ports.
Requested by Brad
"no objection" kettenis@
|
| | |
|
| | |
|
| |
|
|
| |
ok kettenis@ deraadt@
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Requested by deraadt@
|
| |
|
|
|
|
|
|
| |
libtool generated configure scripts expect. Otherwise they might assume
shared libraries aren't supported.
From lld svn revisions 298568 and 298571.
Discussed with kettenis@
|
| |
|
|
|
|
|
|
|
| |
problems with configure scripts generated with libtool.m4 that would
otherwise have to be regenerated with a patched libtool.
Among other things this fixes the build of Mesa on arm64 with lld.
From lld svn revision 298532. ok kettenis@
|
| |
|
|
|
|
|
|
|
|
| |
versioned and end up as local symbols despite being explicitly listed as
global in the version script. This breaks out brk()/sbrk() implementation.
The diff is only a partial solution and unlikely to be accepted as-is
upstream. We'll keep it as a local diff until a better solution is found.
ok guenther@
|
| |
|
|
| |
ok patrick@
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
zero-sized .eh_frame section, which confuses the strip from our
frankenbinutils.
With this diff lld seems to be usable as the arm64 system linker.
ok patrick@, jsg@
|
| |
|
|
|
|
|
| |
seems to cause bad behaviour. Instead call toStringRef() and use its
return value.
ok tom@
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Don't try to upstream this; we are considering moving to a more standard
way that uses symbolic links to point the linker at the right version of
shared libraries.
|
| | |
|
| |
|
|
| |
development effort on OpenBSD/arm64.
|
| |
|