similar to: [LLVMdev] More questions about non_lazy_ptr

So, I've got a case where I am attempting to pass the address of a static symbol from a module written in Tart (the language I am working on), to a module written in C (which is part of Tart's runtime library). This works fine on Linux, but fails on OS X because the address being passed is the "non_lazy_ptr" symbol, not the symbol itself. In my .bc file, I've got code that

Hi All, I'm working on various cleanups and simplifications to the asmprinters. One thing that is driving me nuts is that the asmprinters currently "reverse engineer" a lot of information when printing an operand that isel had when it created it. I'm specifically talking about all the suffixes generated by isel, like $non_lazy_ptr, @TLSGD, @NTPOFF, (%rip) etc. These

Please don't be alarmed by the failed compiles on llvm-ppc-darwin. They are likely not your fault. I'm trying to get a PPC build bot setup (arxan_bellini), and so far it's dying here: Linking CXX shared library ../../lib/libgtest.dylib Undefined symbols: "vtable for llvm::raw_ostream", referenced from: __ZTVN4llvm11raw_ostreamE$non_lazy_ptr in gtest.cc.o

Here's a more specific question about compiling native code: When I use llc to generate a .s file, and then I try to assemble it using 'as', I get tons of errors - it appears to be choking on lines like the following: movl L"_tart.core.Iterable<tart.core.String>:type"$non_lazy_ptr, %eax The error I get is:

On May 18, 2008, at 11:51 PM, Talin wrote: > Anton Korobeynikov wrote: >> Hello Talin, >> >>> Yes exactly. I'm on OS X (x86), and I'm not specifying a target - I >>> assumed that it would choose sensible defaults... >>> >> Could you please provide a .bc testcase? There can be multiple >> issues, >> but at the first glance it

Hello, Bill. > It's not exactly tweaking magic knobs. It's doing something that's > already done -- putting the information in the TAI object, and > allowing the specific back-end to set the appropriate strings. It seems to me, that simple strings / bools there are not enough :) "$non_lazy_ptr" emission is already in asm printers (in 2 places!). The

Hi, I tried to implement an 'llc'-like tool in my project to manage different passes and a target machine. I use given llvm project structure to avoid problems but I have a link problem and don't know how to solve it: The target machine uses 'FindUsedTypes' pass and when I try to use my target machine in the tool I got "Undefined symbols:

> And be warned that the PC doesn't point at the next instruction when you use it like this - I believe you don't need to modify it at all if you swap the pop and the .long. Bernie, is it related to ARM pipeline? I'm interesting in this, is there any other additional information? On Fri, Mar 8, 2013 at 4:59 AM, Tim Northover <t.p.northover at gmail.com>wrote: > Hi Ashi,

Hi Anton, >> It's not exactly tweaking magic knobs. It's doing something that's >> already done -- putting the information in the TAI object, and >> allowing the specific back-end to set the appropriate strings. > It seems to me, that simple strings / bools there are not enough :) > "$non_lazy_ptr" emission is already in asm printers (in 2 places!).

Dear Nico, I believe you need to add LLVMipa to the list of libraries to link into your tool. FindUsedTypes::ID is defined in lib/Analysis/IPA. I think it would be LLVMipa.a if you added it to LLVMLIBS and ipa if you added it to LINK_COMPONENTS. -- John T. Nico wrote: > Hi, > > I tried to implement an 'llc'-like tool in my project to manage > different passes and a

On Tue, 4 May 2004, Chris Lattner wrote: > On Tue, 4 May 2004, Chris Lattner wrote: > > I suspect that a large reason that LLVM does worst than a native C > > compiler with the CBE+GCC is that LLVM generates very low-level C code, > > and I'm not convinced that GCC is doing a very good job (ie, without > > syntactic loops). > > Yup, this is EXACTLY what is

I recently modified my compiler's build files to use clang if it detects its available, however I'm running into a number of problems with this. I'm having one set of problems on OS X, and a different set of problems under Ubuntu. In both cases I'm attempting to link my frontend - compiled with clang - against the LLVM libraries - compiled with gcc. (I thought about compiling LLVM

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1345046301 -3600 # Node ID 7cec0543f67cefe3755bbad0c2262fa2e820d746 # Parent 30bf79cc14d932fbe6ff572d0438e5a432f69b0a libxl: make domain resume API asynchronous Although the current implementation has no asynchromous parts I can envisage it needing to do bits of create/destroy like functionality which may need async

From 18344216b432648605726b137b348f28ef64a4ef Mon Sep 17 00:00:00 2001 From: Liu Jinsong <jinsong.liu@intel.com> Date: Fri, 23 Aug 2013 23:30:23 +0800 Subject: [PATCH V3] xl: HVM domain S3 bugfix Currently Xen hvm s3 has a bug coming from the difference between qemu-traditioanl and qemu-xen. For qemu-traditional, the way to resume from hvm s3 is via ''xl trigger'' command.

Sounds like that was fixed on trunk also, in 0e8608b (I get the same on Windows.) On Tue, Jul 7, 2020 at 8:10 AM Neil Nelson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Uploaded Ubuntu 20.04 > > sha256sum clang+llvm-10.0.1-rc3-x86_64-unknown-linux-gnu.tar.xz > 9a2b573b69a4c3d62d7a4accd9b164044cd5e8fbe68b056716c72cd0f81a134d > > FAIL: LLVM ::

>> 2. ABI docs for Darwin (x86, x86_64, ppc, ppc64) you might find >> somewhere @apple.com. There you can have all 3 types of PIC code: >> static (no pic at all), DynamicNoPIC and full PIC. > > Okay. We need documentation, what is the difference between > DynamicNoPIC and > full PIC ? The best way to figure this out is to run a small program through and look at

Hello all, I am a LLVM newer who want to add a new backend(EBC) into LLVM. After coping the related files from another target and modifying it, I meet a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols:

Anton, >> Can I ask what platform ABI's are documented other than Itanium ? > I'd bet all platform ABI are more or less documented. Right. Maybe we should collect references and do some LLVM PIC documentation and put it on LLVM website ? >> I need to get to understand PIC on x86, x86_64 and PowerPC for the COFF >> and MachO backends. > ABI is normally induced

Hi Ashi, > ld: illegal text-relocation to _data_table in table.o from foo in > use_table.o for architecture armv7 It looks like you're using iOS. I'm not familiar with the exact workings of that platform, but I think a similar message would occur in ELF-land. If iOS *is* comparable, your issue is that symbols in dynamically loaded objects can't (usually) be referenced directly

Any help with the below build failure would be greatly appreciated. If the information I am providing is deficient to diagnose the problem please tell me how to provide better information. Trying to build dovecot-antispam plugin 1.3 from; http://johannes.sipsolutions.net/download/dovecot-antispam/ Dovecot 1.2.11 installed and was configured with --enable-header- install. I also have dovecot