search for: rauw'ed

...GTM. > > > Benefits: > > 1) Lets us reverse the DIGlobalVariable -> GlobalVariable edge, which > should hopefully clear the way for removing the llvm.dbg.cu named > metadata node. > > A little harder than it sounds (need to somehow support a GlobalVariable > that is RAUW'ed with a ConstantInt), but I think this is important to do. > How can a GlobalVariable be replaced with a ConstantInt? Wouldn't that just be an absolute address? Thanks, -- -- Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm...

...1) Lets us reverse the DIGlobalVariable -> GlobalVariable edge, which >>> should hopefully clear the way for removing the llvm.dbg.cu named >>> metadata node. >>> >>> A little harder than it sounds (need to somehow support a GlobalVariable >>> that is RAUW'ed with a ConstantInt), but I think this is important to do. >>> >> >> How can a GlobalVariable be replaced with a ConstantInt? Wouldn't that >> just be an absolute address? >> > > If the global variable has a known constant value & the address is...

...mith <dexonsmith at apple.com> wrote: >> In response to my recent commits (e.g., [1]) that changed API from >> `MDNode` to `Value`, Eric had a really interesting idea [2] -- split >> metadata entirely from the `Value` hierarchy, and drop general support >> for metadata RAUW. > > Wow, this never occurred to me, but in hindsight seems like obviously the right direction. Yup, good on Eric here. >> Here is what we'd lose: >> >> 1. No more arbitrary RAUW of metadata. >> >> While we'd keep support for RAUW of temporary MDNo...

...-> GlobalVariable edge, >>>>> which should hopefully clear the way for removing the llvm.dbg.cu >>>>> named metadata node. >>>>> >>>>> A little harder than it sounds (need to somehow support a >>>>> GlobalVariable that is RAUW'ed with a ConstantInt), but I think this is >>>>> important to do. >>>>> >>>> >>>> How can a GlobalVariable be replaced with a ConstantInt? Wouldn't that >>>> just be an absolute address? >>>> >>> >&gt...

...gt;>>> which should hopefully clear the way for removing the llvm.dbg.cu >>>>>>> named metadata node. >>>>>>> >>>>>>> A little harder than it sounds (need to somehow support a >>>>>>> GlobalVariable that is RAUW'ed with a ConstantInt), but I think this is >>>>>>> important to do. >>>>>>> >>>>>> >>>>>> How can a GlobalVariable be replaced with a ConstantInt? Wouldn't >>>>>> that just be an absolute addres...

Hi all, Recently I have implemented a transformation pass based on LLVM3.5 and its function is to duplicate the function's argument list in a bytecode file and replace all use of original function with modified function. In LLVM3.5, the pass can work properly. However, when I tried to transplant the pass to LLVM3.9, the error "Argument value does not match function argument type!"

...efully clear the way for removing the llvm.dbg.cu >>>>>>>>> named metadata node. >>>>>>>>> >>>>>>>>> A little harder than it sounds (need to somehow support a >>>>>>>>> GlobalVariable that is RAUW'ed with a ConstantInt), but I think this is >>>>>>>>> important to do. >>>>>>>>> >>>>>>>> >>>>>>>> How can a GlobalVariable be replaced with a ConstantInt? Wouldn't >>>>>>...

Hello, I'm currently developing a tool based on LLVM to understand how the LLVM IR changes after optimization passes are run. Today it's a tedious but automatic process at a function level in my language, where I first dump the IR before running any passes, and then do it for the 10 or so passes I care about one-at-a-time to understand which pass affected the change. There are two

...9;t understand why that would be useful outside of speeding up teardown. Since it was actively harmful in some cases, I removed the behaviour, and tried to optimize teardown in other ways. But I can see how it would make sense here. Maybe, when an MDNode operand that is a ConstantAsMetadata gets RAUW'ed to "null" and/or deleted, we should drop uniquing from the MDNode. This is a more targeted version of the historical behaviour. It would prevent the SharedMDs entry from being reused in this case. > > Thanks, > > — > Mehdi > > >> >>> cat...

...way for removing the llvm.dbg.cu >>>>>>>>>> named metadata node. >>>>>>>>>> >>>>>>>>>> A little harder than it sounds (need to somehow support a >>>>>>>>>> GlobalVariable that is RAUW'ed with a ConstantInt), but I think this is >>>>>>>>>> important to do. >>>>>>>>>> >>>>>>>>> >>>>>>>>> How can a GlobalVariable be replaced with a ConstantInt? Wouldn't >>...

...g the >>>>>>>>>>> llvm.dbg.cu named metadata node. >>>>>>>>>>> >>>>>>>>>>> A little harder than it sounds (need to somehow support a >>>>>>>>>>> GlobalVariable that is RAUW'ed with a ConstantInt), but I think this is >>>>>>>>>>> important to do. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> How can a GlobalVariable be replaced with a ConstantInt? Would...

On Jan 27, 2012, at 3:40 PM, Devang Patel <dpatel at apple.com> wrote: > [ removing cfe-dev from the cc list ] > > On Jan 27, 2012, at 1:31 PM, Dan Gohman wrote: > >> On Jan 27, 2012, at 11:20 AM, Devang Patel wrote: >> >>> >>> On Jan 26, 2012, at 2:10 PM, Dan Gohman wrote: >>> >>>> On Jan 26, 2012, at 12:54 PM, Devang

Hi all, I'd like to add support for metadata attachments for global variables in the same way as we did for functions. Syntax would be pretty simple: @foo = global i32 0, !foo !0, !bar !1 (the extra commas are required to disambiguate from a named metadata on the next line) Benefits: 1) Lets us reverse the DIGlobalVariable -> GlobalVariable edge, which should hopefully clear the way for

...std::pair<>`, with `.first` being a tag for the type of attachment (really this is a low-mem map from tag to pointer). - The pointer type needs to have `MetadataTracking` support so that LLParser, BitcodeReader, and DIBuilder can assign a temporary attachment that later gets RAUW'ed. However, if I'm going to roll a custom type anyway, I might as well go full hog: - Make the "large" vector `std::pair<unsigned, TrackingMDNodeRef>`. - Reserve the "small" vector for the `!dbg` tag. - Add custom hooks for `MetadataTracking` for the &quot...

...nality below to see whether I'm trying to break your compiler permanently. In response to my recent commits (e.g., [1]) that changed API from `MDNode` to `Value`, Eric had a really interesting idea [2] -- split metadata entirely from the `Value` hierarchy, and drop general support for metadata RAUW. After hacking together some example code, this seems overwhelmingly to me like the right direction. See the attached metadata-v2.patch for my sketch of what the current metadata primitives might look like in the new hierarchy (includes LLVMContextImpl uniquing support). The initial motivation w...

With 3.9, llvm-link tells me 'invalid subroutine type ref' when linking the two code pieces below, and I don't quite understand why. It looks like it merges the debug information with the custom metadata. I've filed a ticket already [1] but as I'm not sure if this is indeed a bug or if I'm misunderstanding something, I thought I'd ask here. Any ideas? Thanks, Robin

> On 2015 Apr 14, at 21:46, David Blaikie <dblaikie at gmail.com> wrote: > > On Tue, Apr 14, 2015 at 9:33 PM, Duncan P. N. Exon Smith > <dexonsmith at apple.com> wrote: >> >> `Function` definitions should support `MDNode` attachments, with a >> similar syntax to instructions: >> >> define void @foo() nounwind !attach !0 { >>