similar to: [LLVMdev] Disjoint types after reading several modules

On Jan 31, 2012, at 6:16 AM, Clemens Hammacher wrote: > This is because each module contains its own type table with all the types used in that module. When reading in the corresponding bitcode, the BitcodeReader explicitly calls StructType::create, without looking up in the context whether an equivalent type (even with the same name) already exists. > So I think that llvm is behaving

Hi Chris, thanks for your answer! On 2/2/12 1:15 AM, Chris Lattner wrote: > The linker has to solve the exact same problem (read multiple .bc files and unify types across them). This is the impetus behind TypeMapTy in lib/Linker/LinkModules.cpp. You'll probably need to do something like that. I already looked into that. The linker is using the GlobalValues of both modules to identify

Hi Clemens, On 02/02/12 13:30, Clemens Hammacher wrote: > Hi Chris, > thanks for your answer! > > On 2/2/12 1:15 AM, Chris Lattner wrote: >> The linker has to solve the exact same problem (read multiple .bc files and >> unify types across them). This is the impetus behind TypeMapTy in >> lib/Linker/LinkModules.cpp. You'll probably need to do something like that.

On 2/2/12 1:51 PM, Duncan Sands wrote: > On 02/02/12 13:30, Clemens Hammacher wrote: >> On 2/2/12 1:15 AM, Chris Lattner wrote: >>> I have to ask: why are you writing these modules out as separate bc files? >> >> I knew that someone would ask that ;) >> We need to have separate modules during runtime. One of them contains the code >> that is actually JIT

On 2/2/12 2:32 PM, Duncan Sands wrote: > On 02/02/12 14:25, Clemens Hammacher wrote: >> On 2/2/12 1:51 PM, Duncan Sands wrote: > ... >>> what do you mean by "copied over to the main module"? If you want to add >>> additional IR to the main module then you should link it in using the >>> linker. >> >> I think that the linker would indeed

Hi Clemens, On 02/02/12 14:25, Clemens Hammacher wrote: > On 2/2/12 1:51 PM, Duncan Sands wrote: ... >> what do you mean by "copied over to the main module"? If you want to add >> additional IR to the main module then you should link it in using the linker. > > I think that the linker would indeed be able to remap the types correctly, but > the main obstacle here

Hi all, We've run into a tricky situation in our work on the Crack compiler and I'm hoping that someone on this list can help us find the best solution. We're currently trying to implement "module caching" for Crack, similar to the feature in Python where module bitcode is persisted at compile time. When we import a module, before compiling the module we check for a

Hi Michael, since noone of the experts answered, let me share our experiences. We recently had exactly the same problem, I posted on this list on January 31st. I didn't follow Duncans advice to "just use the linker", since for several reasons we wanted to have unique struct types even in the separate modules. > 1) duplicate the LinkModule internal code and copy the module we

On 2/27/12 8:27 PM, Michael Muller wrote: >>> 3) destructively convert all of the types in the imported module to our >>> existing types. >> >> That's what we actually implemented, following the idea I described in >> the mentioned post. We don't identify identical struct types by their >> name, since even in the new type system, names don't

Hi Clemens - thanks for your response. Clemens Hammacher wrote: > Hi Michael, > > since noone of the experts answered, let me share our experiences. We > recently had exactly the same problem, I posted on this list on January > 31st. > I didn't follow Duncans advice to "just use the linker", since for > several reasons we wanted to have unique struct types

Hi everyone, I want to use an LLVM new feature (llvm::orc::remote::RPCBase) to implement a simple RPC framework between two LLVM modules. It seems by this new class we can do serialization/deserialization on LLVM IR type system directly. But I haven't found any helpful stuff on google showing me how to use these RPC APIs. Can anyone give me some hints or example programs showing me how to use

On 3/6/12 5:28 PM, Joerg Sonnenberger wrote: > Advantage of using the latest address: one saved jmp per call. Per newly JITted call ;) > Advantage of using the initial address: easier G/C of intermediate > versions, less things to keep track of. I still think both versions require larger changes. When using the latest address, you have to keep track of all JITted functions per

Hello, Disclaimer: I have no plan to break 3.x bitcode compatibility in any way. I’m experimenting with ideas to improve the current bitcode serialization and deserialization in general. I’m interested in improving the speed and the flexibility of the reader/writer, as well as making the code easier to deal with. My current griefs against our bitcode format are mainly the lack of built-in

Hi all, I've a question about something that's bothering me for quite some time now: why is a llvm::Function seen as a llvm::Value (in a sense that llvm::Function is a subclass of llvm::Value), but llvm::Type is not? Should they not - technically seen - be equal? And to ask a concrete question: is there any way to store a reference to a llvm::Type within the LLVM metadata? As far as I

Looks like globalize (1.2) is not compatible with rails 2.2.2. I am getting: '' => Booting Mongrel (use ''script/server webrick'' to force WEBrick) => Rails 2.2.2 application starting on http://0.0.0.0:3003 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3003 ** Starting Rails with development environment...

On Tue, Oct 13, 2015 at 4:23 PM Hal Finkel <hfinkel at anl.gov> wrote: > > From: "Tanya Lattner via llvm-dev" <llvm-dev at lists.llvm.org> > > > Some back story here. I have gotten many requests through email and > > at the developer meetings about having a Code of Conduct and > > specifically having one for LLVM Developer Meetings. It has been

Hi, I made the switch from KDE4->XFCE, and because gdm takes more time than xfce to start I would like to replace it with lightdm. I installed lightdm, set it as default display manager and configured the gtk greeter. However, when I start I only get a black screen (x running) and nothing else happens. When I start it as root with the --test-mode argument, I get the following message: lightdm

Hi Marcus, > And to ask a concrete question: is there any way to store a reference to a llvm::Type within the LLVM metadata? Not directly, but you can store a null value (Constant::getNullValue()) of the respective type. Cheers, Clemens -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6392 bytes Desc:

Specifically what I am asking is, if I have a computer named ralph$ who is uidNumber 678 in ou=Computers and I have a user who is uidNumber 678 in ou=People, will this cause problems? Must the different sets of uidNumbers be disjoint acrossed different ou's?

Hello, Is there any way I can use the gregexpr functions (or a different function) in a manner that will also return overlapping (i.e. non disjoint) regular expressions? For instance, when running gregexpr("AAA","AAAAAA"), I get two matches, one at position 1 and one at position 4. I'd like to receive 4 matches at positions 1, 2, 3 and 4. Thanks, Schraga