search for: ttext

...nel.org/?p=libs/klibc/klibc.git;a=commit;h=72d6d78a8f0d24a64911c246487402c81b4beb9d Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 20 Jan 2019 19:41:47 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 20 Jan 2019 21:15:17 +0000 [klibc] Use -Ttext-segment to link shared library on all arches We previously changed mips and x86 to link the shared library with the -Ttext-segment option to avoid address collisions with extra sections automatically added by the linker (commits 048bfb0df170, 2a705525e081, 34163a2c7d1c). Adding a build ID to supp...

When using clang+llvm and lld, I get the following error: ld.lld: error: -Ttext-segment is not supported. Use --image-base if you intend to set the base address Let's test whether linker is lld and use --image-base instead of -Ttext-segment. See llvm's rationale for not supporting -Ttext-segment: https://github.com/llvm/llvm-project/commit/4dc2fb123dcfe9a97ad6f3a11350...

.../?p=libs/klibc/klibc.git;a=commit;h=2a705525e0816f9d708d7c41688f6bcb127374fe Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 5 Jan 2019 20:59:33 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 03:10:14 +0000 [klibc] x86_64: Use -Ttext-segment to avoid address collision Building klibc for x86_64 with binutils 2.31 adds an extra .note.gnu.property section to klibc.so, the address of which is not affected by the -Ttext option. Loading a klibc executable then fails with the following kernel log message: 9409 (sh.shared): Uhuuh, e...

...rg/?p=libs/klibc/klibc.git;a=commit;h=34163a2c7d1c3b841a35b242dbdbda25c4fb1ecb Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 6 Jan 2019 03:19:51 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 18 Jan 2019 03:10:14 +0000 [klibc] i386: Use -Ttext-segment to avoid address collision Building klibc for i386 with binutils 2.31 adds an extra .note.gnu.property section to klibc.so, the address of which is not affected by the -Ttext option. Loading a klibc executable then fails with the following kernel log message: 9409 (sh.shared): Uhuuh, elf...

Building klibc for x86_64 with binutils 2.31 adds an extra .note.gnu.property section to klibc.so, the address of which is not affected by the -Ttext option. Loading a klibc executable then fails with the following kernel log message: 9409 (sh.shared): Uhuuh, elf segment at 0000000000200000 requested but the memory is mapped already I don't exactly see why this is happening, but it is triggered by the new section and the collision can be...

...sr/klibc/arch/alpha/MCONFIG b/usr/klibc/arch/alpha/MCONFIG index ad11372f..072adb85 100644 --- a/usr/klibc/arch/alpha/MCONFIG +++ b/usr/klibc/arch/alpha/MCONFIG @@ -14,3 +14,7 @@ KLIBCBITSIZE = 64 # 7 GB - normal binaries start at 4.5 GB, and the stack is below # the binary. KLIBCSHAREDFLAGS = -Ttext-segment 0x1c0000000 + +# Kernel uses stack trampoline for signal return unless we set +# sa_restorer +KLIBCEXECSTACK := y diff --git a/usr/klibc/arch/arm/MCONFIG b/usr/klibc/arch/arm/MCONFIG index 8a7096b8..ae407cb9 100644 --- a/usr/klibc/arch/arm/MCONFIG +++ b/usr/klibc/arch/arm/MCONFIG @@ -33,3 +...

From: Stanislav Fomichev <sdf at google.com> Clang's lld prefers the use of "-image-base" instead of "-Ttext-segment". Signed-off-by: Stanislav Fomichev <sdf at google.com> Signed-off-by: Bill Wendling <morbo at google.com> --- Makefile | 3 +++ usr/klibc/arch/i386/MCONFIG | 2 +- usr/klibc/arch/mips64/MCONFIG | 2 +- usr/klibc/arch/ppc/MCONFIG | 2 +- usr/...

...endling <morbo at google.com> AuthorDate: Sun, 29 Mar 2020 04:38:31 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 20:45:34 +0100 [klibc] Kbuild: support clang's lld Clang's lld prefers the use of "-image-base" instead of "-Ttext-segment". Signed-off-by: Stanislav Fomichev <sdf at google.com> Signed-off-by: Bill Wendling <morbo at google.com> Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- Makefile | 3 +++ usr/klibc/arch/i386/MCONFIG | 2 +- usr/klibc/arch/mips64...

This reverts commit 9d8d648e604026b32cad00a84ed6c29cbd157641, which broke signal handing on some architectures. On m68k and parisc, signal return depends on a trampoline that the kernel writes on the stack. On alpha, s390, and sparc (32-bit), we can avoid this by providing our own function as sa_restorer, but we currently don't. Signed-off-by: Ben Hutchings <ben at decadent.org.uk>

...main interp.o tests/$*.o $(LD_SOLIB_FLAGS) $(SOLIB) $(LIBGCC) cp $@ $@.stripped $(STRIP) $@.stripped --- klibc/arch/alpha/MCONFIG +++ klibc/arch/alpha/MCONFIG 2003/11/27 15:04:12 @@ -14,4 +14,4 @@ # 7 GB - normal binaries start at 4.5 GB, and the stack is below # the binary. SHAREDFLAGS = -Ttext 0x1c0000200 - +LD_SOLIB_FLAGS = -R --- klibc/arch/arm/MCONFIG +++ klibc/arch/arm/MCONFIG 2003/11/27 15:04:16 @@ -24,3 +24,4 @@ # This address needs to be reachable using normal inter-module # calls, and work on the memory models for this architecture SHAREDFLAGS = -Ttext 0x01000200 +LD_SOLIB_FLA...

...nd no other > recent changes related to Clang or lld. > > So please send over any other fixes you have. > Hi Ben, I'm sorry. I don't know what you want. The patches I see in top-of-tree klibc look to be the ones I listed above. Though I don't see the -ffreestanding and the -Ttext-segment changes commit 3dbbaade8f836f18e1f739a61cc359d799d1127f Author: Bill Wendling <morbo at google.com> Date: Mon Jun 4 16:55:01 2018 -0700 klibc: add -ffreestanding to required flags Newer clang versions need the '-ffreestanding' flag because new changes convert...

.../?p=libs/klibc/klibc.git;a=commit;h=048bfb0df170d4a43142adcee8a2dffdfc2c1e9f Author: James Cowgill <james.cowgill at mips.com> AuthorDate: Fri, 2 Mar 2018 08:33:01 -0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] mips: use -Ttext-segment when linking shared library Most architectures use the -Ttext option to move the klibc shared library out of the way of the normal load address. Unfortunately MIPS has some extra sections which are positioned before the .text section and are therefore not repositioned by the -Ttext option....

On Sat, 2020-07-25 at 15:16 -0700, Bill Wendling wrote: > On Sat, Jul 25, 2020 at 2:56 PM Ben Hutchings <ben at decadent.org.uk> wrote: > > On Sat, 2020-07-25 at 14:36 -0700, Bill Wendling wrote: > > [...] > > > I upstreamed a few patches to klibc to fix a few linker errors. Some > > > of these might help: > > > > I applied v3 of your patch

This series fixes link/load issues I found on i386 with Debian's toolchain (gcc 8 with PIE as default, binutils 2.31). Ben. Ben Hutchings (2): [klibc] i386: Use -Ttext-segment to avoid address collision [klibc] Disable PIE scripts/Kbuild.klibc | 3 ++- usr/klibc/arch/i386/MCONFIG | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/p...

This is a series of patches for clang compatibility: - Using flags needed flags and removing unsupported flags. - Adding support for clang's LLD linker. - Removing a variety of warnings. Bill Wendling (3): [klibc] Kbuild: use "libc.a" with clang [klibc] Kbuild: Add "-fcommon" for clang builds [klibc] Clean up clang warnings Michael Davidson (1): [klibc] Kbuild:

.../MCONFIG b/usr/klibc/arch/i386/MCONFIG index bfec004..0704669 100644 --- a/usr/klibc/arch/i386/MCONFIG +++ b/usr/klibc/arch/i386/MCONFIG @@ -31,6 +31,3 @@ KLIBCBITSIZE = 32 # calls, and work on the memory models for this architecture # 96 MB - normal binaries start at 128 MB KLIBCSHAREDFLAGS = -Ttext-segment 0x06000000 - -# Asm includes for i386 are in the merged x86 tree -KLIBCARCHINCFLAGS = -I$(KLIBCKERNELOBJ)/arch/x86/include diff --git a/usr/klibc/arch/ppc/MCONFIG b/usr/klibc/arch/ppc/MCONFIG index 6630df7..46c5923 100644 --- a/usr/klibc/arch/ppc/MCONFIG +++ b/usr/klibc/arch/ppc/MCONFIG @@...

...ternal email. Do not click links or open attachments unless you recognize the sender and know the content is safe. On Mon, Nov 16, 2020 at 9:05 AM Moshtaghi, Alireza <Alireza.Moshtaghi at netapp.com> wrote: > > My target requires that text section be at 0x0 so "-Ttext 0x0" is passed to the linker. > When I link with gold, it goes through; but lld fails. > Instead of always returning the same calculation, when I change the calculation to the following, it links: > return first->offset + (os->addr > first->addr ? >...

...d GNU ld's -z separate-code layout) You need to use --image-base=0 https://releases.llvm.org/10.0.0/tools/lld/docs/ReleaseNotes.html#breaking-changes On Mon, Nov 16, 2020 at 10:31 AM Moshtaghi, Alireza <Alireza.Moshtaghi at netapp.com> wrote: > > Actually it is the combination of -Ttext 0x0 and --no-rosegment that cause the problem. You can reproduce using any c file using following: > clang test.c -fuse-ld=lld -Wl,-Ttext,0x0 -Wl,--no-rosegment > > A > > On 11/16/20, 9:52 AM, "llvm-dev on behalf of Moshtaghi, Alireza via llvm-dev" <llvm-dev-bounces at...

- Renamed IMAGE_BASE to LD_IMAGE_BASE_OPT. - Moved "-fcommon" to KLIBCREQFLAGS in scripts/Kbuild.klibc. - Remove "dash" warning fixes which have been upstreamed. - Conditionalize the inclusion of compiler flags by using the proper compiler name or "cc-option". - Added "-Werror" to "cc-option" to catch flags that cause warnings. - Retain

...bit MIPS and in my quest to fix the bug I got a bit carried away and fixed a few other things as well. Here are various miscellaneous MIPS patches, although the first patch is the important one. Thanks, James *** BLURB HERE *** James Cowgill (5): mips64: compile with -mno-abicalls mips: use -Ttext-segment when linking shared library mips/mips64: simplify crt0 code mips: don't save floating point registers in setjmp / longjmp mips64: remove __unused from __jmp_buf usr/include/arch/mips/klibc/archsetjmp.h | 14 -- usr/include/arch/mips64/klibc/archsetjmp.h | 1 - usr/klibc/arc...