search for: dynlink

...__dynstr_start; - . = ALIGN(4); - - __gnu_hash_vma = .; - __gnu_hash_lma = __gnu_hash_vma + __text_lma - __text_vma; - .gnu.hash : AT(__gnu_hash_lma) { + .gnu.hash : AT(ADDR(.gnu.hash) + __vma_to_lma) { __gnu_hash_start = .; *(.gnu.hash) __gnu_hash_end = .; } - . = ALIGN(4); - - __dynlink_vma = .; - __dynlink_lma = __dynlink_vma + __text_lma - __text_vma; - .dynlink : AT(__dynlink_lma) { + .dynlink : AT(ADDR(.dynlink) + __vma_to_lma) { __dynlink_start = .; *(.dynlink) __dynlink_end = .; } - . = ALIGN(4); - - __got_vma = .; - __got_lma = __got_vma + __text_lma - __text_v...

From: Sylvain Gault <sylvain.gault at gmail.com> TL;DR: The section aligment in linker scripts messed-up the memory mapping needed for the compression / decompression to work. The bug with gcc 5 is not trivial, I'll do my best to explain it here. Basically, there are two memory mappings of the code. One in "virtual memory", and one in "load memory". The one in

...http://llvm-reviews.chandlerc.com/D1927 In order to allow code generation from OCaml, I need to build a stub library per configured target. I'm not sure how to integrate it with LLVM's build system; my current solution seems very ad-hoc. I will update the patch to use Dynlink interface (this is the textbook use case for Dynlink), but conceptually this doesn't change the problem of interfacing with build system. -- WBR, Peter Zotov.

...ynstr_end - __dynstr_start); - - . = ALIGN(4); - - HIDDEN(__gnu_hash_vma = .); - HIDDEN(__gnu_hash_lma = __gnu_hash_vma + __text_lma - __text_vma); - .gnu.hash : AT(__gnu_hash_lma) { - HIDDEN(__gnu_hash_start = .); - *(.gnu.hash) - HIDDEN(__gnu_hash_end = .); - } - - - . = ALIGN(4); - - HIDDEN(__dynlink_vma = .); - HIDDEN(__dynlink_lma = __dynlink_vma + __text_lma - __text_vma); - .dynlink : AT(__dynlink_lma) { - HIDDEN(__dynlink_start = .); - *(.dynlink) - HIDDEN(__dynlink_end = .); - } - - . = ALIGN(4); - - HIDDEN(__got_vma = .); - HIDDEN(__got_lma = __got_vma + __text_lma - __text_vma); - .g...

From: Sylvain Gault <sylvain.gault at gmail.com> These patches basically remove unused linker scripts and port a change that was made to an unused script. Those are to be applied on top of the gcc 5 bug fixes as they would conflict otherwise. Sylvain Gault (4): diag/mbr: fix dependency to linker script Remove unused linker scripts core: Make symbols defined in linker script HIDDEN

...9;t think more than one DT_INIT / DT_FINI entry should be >> allowed as the latter entry will overwrite the earlier ones. > > Thanks Joerg, The snip of code that appears to run the init/fini was easily > browseable with musl. > > http://git.musl-libc.org/cgit/musl/tree/src/ldso/dynlink.c (function: > do_init_fini). > > That said, all of the code is essentially under NO_LEGACY_INITFINI, is the > linker responsible to convert DT_INIT to DT_INITARRAY's ? > > If so, I think more than one init/fini option should be converted to > DT_INIT_ARRAY (or) DT_FINI_ARR...

...but would like to. We have a call center that is currently dormant but are considering opening it back up (approx 200 seats). Also looking for ways to cluster or make it highly available. I looked around, not a whole lot of info on this. Thanks in advance. http://www.designatedsystems.com/dynlink.jsp?link_id=63

...uld be a nice optimization to share the .dynamic section of an application where possible. In particular we would like to have this option for Fuchsia. Other dynamic linkers, like musl, already have some support for this on non-MIPS targets as seen here: http://git.musl-libc.org/cgit/musl/tree/ldso/dynlink.c#n1629. In particular the DT_DEBUG_INDIRECT entry is recognized. This change would refactor code that already exists for MIPS specific .dynamic sections and make them available to other targets. Mostly this would just require renaming some things and moving a few lines around. The biggest part of...

...low code generation from OCaml, I need to build >>> a stub library per configured target. I'm not sure how to >>> integrate it with LLVM's build system; my current solution seems >>> very ad-hoc. >>> >>> I will update the patch to use Dynlink interface (this is the >>> textbook use case for Dynlink), but conceptually this doesn't >>> change the problem of interfacing with build system. >>> >>> -- >>> WBR, Peter Zotov. >>> _______________________________________________ &g...

On Mon, Dec 08, 2014 at 10:21:49AM -0600, Shankar Easwaran wrote: > The DT_INIT/DT_FINI correspond to one initializer function,where as > DT_INIT_ARRAY/DT_FINI_ARRAY is used when there is more than one > initalizer function/finalizer function respectively. This is not true. The difference is that the DT_INIT / DT_FINI function is responsible for calling into the .init / .fini block and

...>> the .dynamic section of an application where possible. In particular we >> would like to have this option for Fuchsia. Other dynamic linkers, like >> musl, already have some support for this on non-MIPS targets as seen here: >> http://git.musl-libc.org/cgit/musl/tree/ldso/dynlink.c#n1629. In >> particular the DT_DEBUG_INDIRECT entry is recognized. >> >> This change would refactor code that already exists for MIPS specific >> .dynamic sections and make them available to other targets. Mostly this >> would just require renaming some things and mo...

...ction of an application where possible. In particular we >>>> would like to have this option for Fuchsia. Other dynamic linkers, like >>>> musl, already have some support for this on non-MIPS targets as seen here: >>>> http://git.musl-libc.org/cgit/musl/tree/ldso/dynlink.c#n1629. In >>>> particular the DT_DEBUG_INDIRECT entry is recognized. >>>> >>>> This change would refactor code that already exists for MIPS specific >>>> .dynamic sections and make them available to other targets. Mostly this >>>> would...

...musl source too, at commit 7d756e1c04de ("dns: prefer monotonic clock for timeouts", 2023-02-12). The execvp() implementation: https://git.musl-libc.org/cgit/musl/tree/src/process/execvp.c does not handle ENOEXEC; what's more, the entire tree only sets errno=ENOEXEC in "ldso/dynlink.c". Laszlo

...ignore; if not (Llvm_bitwriter.write_bitcode_file m filename) then exit 1; dispose_module m let () = match Sys.argv with | [|_; filename|] -> main filename | _ as a -> Printf.eprintf "Usage: %s <file>\n" a.(0) Compile with: $ ocamlc -dtypes -pp camlp4oof -I +camlp4 dynlink.cma camlp4lib.cma -cc g++ -I /usr/local/lib/ocaml/ llvm.cma llvm_bitwriter.cma minml.ml -o minml Run on the following fib.ml file: let rec fib n = if n <= 2 then 1 else fib(n-1) + fib(n-2) do fib 40 with: $ ./minml run.bc $ llc -f run.bc -o run.s && $ gcc run.s -o run...

Here's my translation of the Fibonacci example into OCaml: open Printf open Llvm let build_fib m = let fibf = define_function "fib" (function_type i32_type [| i32_type |]) m in let bb = builder_at_end (entry_block fibf) in let one = const_int i32_type 1 and two = const_int i32_type 2 in let argx = param fibf 0 in set_value_name "AnArg" argx; let

...where possible. In particular we >>>>>> would like to have this option for Fuchsia. Other dynamic linkers, like >>>>>> musl, already have some support for this on non-MIPS targets as seen here: >>>>>> http://git.musl-libc.org/cgit/musl/tree/ldso/dynlink.c#n1629. In >>>>>> particular the DT_DEBUG_INDIRECT entry is recognized. >>>>>> >>>>>> This change would refactor code that already exists for MIPS specific >>>>>> .dynamic sections and make them available to other targets. Mos...

On Tue, Mar 21, 2023 at 03:56:22PM +0100, Laszlo Ersek wrote: > > $ podman build -f ci/containers/alpine-edge.Dockerfile -t libnbd-alpine-edge > > $ podman run -it --rm --userns=keep-id -v .:/repo:z -w /repo libnbd-alpine-edge bash > > $ ./configure > > $ make check > > $ grep tmpd= lib/test-suite.log > > + tmpd=/tmp/tmp.EMgKeF > > $ /tmp/tmp.EMgKeF/bin/f