Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Hidden-visibility aliases to default-visibility globals"
2013 Mar 21
0
[LLVMdev] Hidden-visibility aliases to default-visibility globals
On Wed, Mar 20, 2013 at 02:22:47PM -0700, Peter Collingbourne wrote:
> I am trying to compile a dynamic loader using LLVM. Part of the IR
> for this loader looks like this:
>
> @_rtld_local = hidden alias %struct.rtld_global* @_rtld_global
> @_rtld_global = unnamed_addr global %struct.rtld_global { ... }
Have you tried using protected visibility?
Joerg
2013 Apr 01
2
[LLVMdev] Hidden-visibility aliases to default-visibility globals
On Thu, Mar 21, 2013 at 02:12:27PM +0900, Joerg Sonnenberger wrote:
> On Wed, Mar 20, 2013 at 02:22:47PM -0700, Peter Collingbourne wrote:
> > I am trying to compile a dynamic loader using LLVM. Part of the IR
> > for this loader looks like this:
> >
> > @_rtld_local = hidden alias %struct.rtld_global* @_rtld_global
> > @_rtld_global = unnamed_addr global
2013 May 14
0
[LLVMdev] Hidden-visibility aliases to default-visibility globals
On Mon, Apr 01, 2013 at 03:49:14PM -0700, Peter Collingbourne wrote:
> On Thu, Mar 21, 2013 at 02:12:27PM +0900, Joerg Sonnenberger wrote:
> > On Wed, Mar 20, 2013 at 02:22:47PM -0700, Peter Collingbourne wrote:
> > > I am trying to compile a dynamic loader using LLVM. Part of the IR
> > > for this loader looks like this:
> > >
> > > @_rtld_local =
2016 Feb 21
2
RFC: Add guard intrinsics to LLVM
Hi Andy,
Thanks for replying, responses inline below:
On Fri, Feb 19, 2016 at 11:12 AM, Andrew Trick <atrick at apple.com> wrote:
> This clearly doesn't need operand bundles, but using an intrinsic
> would permit special code motion semantics. It could be hoisted and
> merged with other traps, but the condition could never be widened
> beyond the union of the original
2016 Feb 27
0
Possible soundness issue with available_externally (split from "RFC: Add guard intrinsics")
On Fri, Feb 26, 2016 at 7:08 PM Sanjoy Das <sanjoy at playingwithpointers.com>
wrote:
> On Thu, Feb 25, 2016 at 9:59 AM, Sanjoy Das
> <sanjoy at playingwithpointers.com> wrote:
> > Couple of other examples:
> >
> > void @foo(i32* %ptr) available_externally {
> > %discard = load i32, i32* %ptr
> > }
> > void bar() {
> > call
2018 Nov 07
2
Re: guestfs_launch() fails when C application is started as a systemd service
> That makes no sense because we are supposed to have just forked
successfully
I just realized libguestfs uses fork. Now we know why qemu-img worked - I
launched it with popen.
> So it must be something to do with collectd and how it runs programs.
> Is it using LD_PRELOAD trickery, or replacing libc, or using seccomp?
If I understand the question correctly - it's about how
1998 May 27
3
dependencies in .so files
Thomas Lumley writes:
>
>
> I've been trying to get Matt Calder's S compiler to work in R using R
> COMPILE and R SHLIB so it will be fairly platform-independent.
>
> I'm sure someone has claimed in the past that it is possible/easy to
> dyn.load() two dynamic libraries and have one call functions in the other.
> I can't get it to work (Red Hat
2013 Oct 10
1
[LLVMdev] How to handle aliases?
My recent change to use more aliases for destrucors in clang has
opened a can of worms.
The fundamental issue is that aliasing in object files have fairly
complex semantics. For example, on ELF if a symbol is defined in a
COMDAT in one object file, it must be defined in every object file
that has that COMDAT.
Given that weak symbols get implemented with COMDATs, the actual rule
at the llvm level
2012 Oct 22
5
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote:
> Nick,
> I have uploaded the full walk with 'set env DYLD_PRINT_INITIALIZERS'. It didn't seem very informative
> as the dyld error occurs right after...
>
> (gdb)
> llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8 "/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at
2016 Feb 27
2
Possible soundness issue with available_externally (split from "RFC: Add guard intrinsics")
On Thu, Feb 25, 2016 at 9:59 AM, Sanjoy Das
<sanjoy at playingwithpointers.com> wrote:
> Couple of other examples:
>
> void @foo(i32* %ptr) available_externally {
> %discard = load i32, i32* %ptr
> }
> void bar() {
> call @foo(i32* %x)
> }
>
> ==>
>
> void @foo(i32* %ptr) available_externally {
> }
> void bar() {
>
2007 Apr 09
1
RTLD_GLOBAL flag for dlopen
I am just experimenting with a plugin loader and I found
that there are problems with external symbols which are
loaded at runtime.
The solution is to add RTLD_GLOBAL to the dlopen mode,
but I am not sure if this would cause other problems.
Is this patch OK to go in?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtld_global.diff
Type: text/x-patch
Size:
2008 Jul 09
2
[LLVMdev] Add RTLD_GLOBAL to dlopen
Hi,
Today, I've made the transition from LLVM 2.1 to 2.3. I invoke opt
with two dynamic libraries to "-load", the first of which contains
transformation passes and support code whereas the second one provides
extra passes which make use of the first library's support code. In
other words, the symbols loaded in for the first library should be
available when the second
2015 Feb 17
2
[LLVMdev] [PATCH 2/2 v3] add visibility hidden to tls entry points
On Tue, Feb 17, 2015 at 12:38 PM, Marc Dietrich <marvin24 at gmx.de> wrote:
> Am Dienstag, 17. Februar 2015, 11:58:06 schrieb Sedat Dilek:
>> On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at gmx.de> wrote:
>> > Avoid redefined symbol errors in clang. Based on a suggestion from
>> > Rafael Ávila de Espíndola <rafael.espindola at gmail.com> in
2015 Feb 17
2
[LLVMdev] [PATCH 2/2 v3] add visibility hidden to tls entry points
On Tue, Feb 17, 2015 at 12:38 PM, Marc Dietrich <marvin24 at gmx.de> wrote:
> Am Dienstag, 17. Februar 2015, 11:58:06 schrieb Sedat Dilek:
>> On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at gmx.de> wrote:
>> > Avoid redefined symbol errors in clang. Based on a suggestion from
>> > Rafael Ávila de Espíndola <rafael.espindola at gmail.com> in
2015 Feb 17
3
[LLVMdev] [PATCH 2/2 v3] add visibility hidden to tls entry points
On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at gmx.de> wrote:
> Avoid redefined symbol errors in clang. Based on a suggestion from
> Rafael Ávila de Espíndola <rafael.espindola at gmail.com> in
> http://llvm.org/bugs/show_bug.cgi?id=19778.
>
> Signed-off-by: Marc Dietrich <marvin24 at gmx.de>
> ---
> v2: - no change
> v3: - include util
2015 Feb 17
3
[LLVMdev] [PATCH 2/2 v3] add visibility hidden to tls entry points
On Tue, Feb 17, 2015 at 12:47 PM, Marc Dietrich <marvin24 at gmx.de> wrote:
> Am Dienstag, 17. Februar 2015, 12:42:00 schrieb Sedat Dilek:
>> On Tue, Feb 17, 2015 at 12:38 PM, Marc Dietrich <marvin24 at gmx.de> wrote:
>> > Am Dienstag, 17. Februar 2015, 11:58:06 schrieb Sedat Dilek:
>> >> On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at
2012 Oct 23
1
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Mon, Oct 22, 2012 at 11:40:32AM -0700, Nick Kledzik wrote:
>
> On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote:
>
> > Nick,
> > I have uploaded the full walk with 'set env DYLD_PRINT_INITIALIZERS'. It didn't seem very informative
> > as the dyld error occurs right after...
> >
> > (gdb)
> >
2015 Feb 20
2
[LLVMdev] [PATCH 0/2 v3] add visibility hidden to tls entry points
On Tue, Feb 17, 2015 at 1:55 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
> On Tue, Feb 17, 2015 at 10:40 AM, Marc Dietrich <marvin24 at gmx.de> wrote:
>> Patch 1 adds a check for the compilers visibility macro to configure.ac.
>> Patch 2 avoids redefined symbol errors in clang of the tls entry points.
>> Based on a suggestion from Rafael Ávila de Espíndola
2016 Feb 27
1
Possible soundness issue with available_externally (split from "RFC: Add guard intrinsics")
On Fri, Feb 26, 2016 at 7:11 PM, Chandler Carruth <chandlerc at google.com> wrote:
> On Fri, Feb 26, 2016 at 7:08 PM Sanjoy Das <sanjoy at playingwithpointers.com>
> wrote:
>>
>> On Thu, Feb 25, 2016 at 9:59 AM, Sanjoy Das
>> <sanjoy at playingwithpointers.com> wrote:
>> > Couple of other examples:
>> >
>> > void @foo(i32*
2010 Jan 09
0
[LLVMdev] Inlining
Hi Alastair,
> Forgive my confusion, but I can't help notice that LangRef states:
>
> Globals with "linkonce" linkage are merged with other globals of the same name when linkage occurs. This is typically used to implement inline functions, templates, or other code which must be generated in each translation unit that uses it. Unreferenced linkonce globals are allowed to be