Age | Commit message (Collapse) | Author |
|
|
|
|
|
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.
|
|
ok hackroom@
|
|
Only having ELF is perfectly fine for us.
ok kettenis@
|
|
don't enforce it yet, but we want to go down that road. Additionally
the Pine64 seems to boot up with strict alignment on by default, so
this also implicitly fixes efiboot on that hardware.
ok kettenis@ phessler@ visa@
|
|
code generation. Use dyn_case_or_null instead of a static cast to
solve the crashes in the previous code.
ok stefan@ kettenis@
|
|
on any other platform and it causes a segfault in combination with our
IR Stack Guard.
"looks reasonable" kettenis@
"looks good to me" stefan@
|
|
|
|
|
|
to our linker. Additionally, we need to make sure the library path is
prefixed with the cross directory, which is sysroot.
ok kettenis@
|
|
(little-endian) target.
ok phessler@
|
|
cluebat & ok kettenis@
|
|
ok patrick@
|
|
ok stefan@, jsg@, patrick@
|
|
ok patrick@
|
|
ok pascal@
Original commit message:
[SSP] Do not set __guard_local to hidden for OpenBSD SSP
guard_local is defined as long on OpenBSD. If the source file contains
a definition of guard_local, it mismatches with the int8 pointer type
used in LLVM. In that case, Module::getOrInsertGlobal() returns a
cast operation instead of a GlobalVariable. Trying to set the
visibility on the cast operation leads to random segfaults (seen when
compiling the OpenBSD kernel, which also runs with stack
protection).
In the kernel, the hidden attribute does not matter. For userspace code,
guard_local is defined as hidden in the startup code. If a program
re-defines guard_local, the definition from the startup code will
either win or the linker complains about multiple definitions
(depending on whether the re-defined __guard_local is placed in the
common segment or not).
It also matches what gcc on OpenBSD does.
|
|
looks good to stefan@
|
|
does not tell our linker to produce that header for statically linked
binaries. Just create that header for all binaries and we are fine.
ok guenther@
|
|
use the old libstdc++ by specifying -stdlib=libstdc++.
with hints from/looks good to patrick@, ok kettenis@
|
|
ok kettenis@
|
|
ok hackroom@
|