similar to: syslinux-5.xx+ modules' ELF files may be mistreated as system DSO

?Hi, I found a new issue in lld (https://llvm.org/bugs/show_bug.cgi?id=26222), but after review of outputs internals still have no idea why that can happen. Do you have any thoughts about possible reasons of that ? I am going to continue investigating that tomorrow. Best regards, George. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugzilla.mindrot.org/show_bug.cgi?id=1714 Summary: Avoid implicit DSO linking Product: Portable OpenSSH Version: 5.3p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org ReportedBy: jchadima

Hi, It looks like I have found a bug in LLD. Suppose DSO defines a global variable 'data' and initializes it by the address of function 'set_data' defined in the same DSO. If an executable file (linked by LLD) gets address of the '&set_data' function and compares it with a value stored in the 'data' variable it gets different result. If the executable is linked

I'm attempting to fetch a kernel over http using lpxelinux.0, as documented in http://www.syslinux.org/wiki/index.php/Syslinux_5_Changelog and it took me far too long to succeed... My first attempt was via pxelinux.0 as embedded in the Ubuntu 13.04 installer, this gave me the error that gPXE/iPXE extentions weren't available. So I inferred that this wasn't v5.10 or greater. Then I

This is a Fedora Core 13 environment and I just noticed this as I update the xen-unstable tree: make -C libxl install make[3]: Entering directory `/home/konrad/ssd/xtt/xen-unstable/tools/libxl'' rm -f _libxl_paths.h.tmp.tmp; echo "SBINDIR=\"/usr/sbin\"" >> _libxl_paths.h.tmp.tmp; echo "BINDIR=\"/usr/bin\"" >> _libxl_paths.h.tmp.tmp;

Yes, I had just reduced it too. I am pretty sure this was implemented at some point. Taking a look. Cheers, Rafael On 8 February 2016 at 17:52, Sean Silva <chisophugis at gmail.com> wrote: > Sounds like it is related to this: > > http://www.airs.com/blog/archives/42 > """ > > The fact that C permits taking the address of a function introduces an >

On 04/29/2013 09:12, Keith Walker wrote: > You only need to go to 64-bit DWARF when your debugging information becomes > too large to fit in 32-bit DWARF tables. I am not sure if this is true. Currently R_X86_64_32 EL relocations are issued for DWARF-32 debug info sections. This is because the size of address in DWARF-32 is only 32-bits, according to the above mentioned specification.

Some time ago i already tried to get running a Digital Oszilloscope DSO-2100 at the parallel port LPT1. But i give up to get it running. Now i have another problem (http://forum.winehq.org/viewtopic.php?p=38741#38741) and so i have tested this again. This time i added the keys to the registry for direct parport access: Code: REGEDIT4 [HKEY_LOCAL_MACHINE\Software\Wine\VDM]

The size of an address on the target machine in the 32-bit DWARF format is NOT restricted to 32-bits. The size of an address on the target machine is specified in the DWARF table headers. For example, in the DWARF-3 Specification, section 7.5.1, the unit_length field is used to specify whether the DWARF format is 32-bit or 64-bit (as well as defining the length of the table). However the

On Sep 23, 2013, at 4:52 PM, Michael Spencer <bigcheesegs at gmail.com> wrote: > The following code currently links incorrectly when linking against a dynamic libc on Ubuntu 12.10 unless -fpic is specified. > > #include <stdio.h> > > int main() { > fputs("hi\n", stdout); > } > > The reason is that stdout gets a R_X86_64_PC32 relocation, but is

On 9/23/2013 7:07 PM, Nick Kledzik wrote: > On Sep 23, 2013, at 4:52 PM, Michael Spencer <bigcheesegs at gmail.com> wrote: > >> The following code currently links incorrectly when linking against a dynamic libc on Ubuntu 12.10 unless -fpic is specified. >> >> #include <stdio.h> >> >> int main() { >> fputs("hi\n", stdout); >>

The following code currently links incorrectly when linking against a dynamic libc on Ubuntu 12.10 unless -fpic is specified. #include <stdio.h> int main() { fputs("hi\n", stdout); } The reason is that stdout gets a R_X86_64_PC32 relocation, but is of type Object. The ELF writer can't see this, and assumes all R_X86_64_PC32 relocations in dynamic outputs are to functions

Absolutely. The goal of the tool is to produce both textual and binary DSO stubs. This means you could take a DSO, produce a textual stub, modify it however you wish, and then produce a linkable binary stub from that modified .tbe. That, or you could bypass the textual portion altogether and just produce binary stubs from DSOs. While the textual format is useful, the goal is to make the tool

Right. Usually you wouldn't want to write a .tbe from scratch, but for the sake of linking against a DSO you might only have access to a .tbe stub that was produced from the DSO. This specific functionality becomes critical when DSOs only used for linking are replaced entirely by .tbe stubs because at a SDK level the complete DSO isn't needed. This is what Apple has done to significantly

Initial issue is related to R_MIPS_GPREL16/32 relocations. When we calculate such relocations we need to know _gp symbol's value. This value might come from different sources. Usually we setup it using constant offset from the .got section. Also it might be defined by a linker script. And in rare but possible case it comes from .reginfo / .MIPS.options sections. Got example, GNU bfd linker

<div dir='auto'>Maybe LLD is lagging behind, but is the TAPI stuff that's landed close enough to the original such that Apple cctools could be modified to use it?<div dir="auto"><br></div><div dir="auto">Cheers,</div><div dir="auto"><br></div><div

Hello all, LLVM-TAPI seeks to decouple the necessary link-time information for a dynamic shared object from the implementation of the runtime object. This process will be referred to as dynamic shared object (DSO) stubbing throughout this proposal. A number of projects have implemented their own versions of shared object stubbing for a variety of reasons related to improving the overall linking

On 9/23/2013 9:05 PM, Shankar Easwaran wrote: > On 9/23/2013 7:07 PM, Nick Kledzik wrote: >> On Sep 23, 2013, at 4:52 PM, Michael Spencer <bigcheesegs at gmail.com> >> wrote: >> >>> The following code currently links incorrectly when linking against >>> a dynamic libc on Ubuntu 12.10 unless -fpic is specified. >>> >>> #include

On Sep 23, 2013, at 7:05 PM, Shankar Easwaran wrote: > On 9/23/2013 7:07 PM, Nick Kledzik wrote: >> On Sep 23, 2013, at 4:52 PM, Michael Spencer <bigcheesegs at gmail.com> wrote: >> >>> The following code currently links incorrectly when linking against a dynamic libc on Ubuntu 12.10 unless -fpic is specified. >>> >>> #include <stdio.h>

Oof, I didn't think about Clang not being in the same place. Perhaps we could put this in clang-tools-extra to solve that? As for the unification of the code bases. I was assuming we didn't want to just throw a ton of code over the wall anyway so the merge was going to need to be reviewed chunk by chunk anyhow. Support for the two formats should be possible to add in parallel (although, I