search for: metatadata

...ames via llvm-dev wrote: > I've scanned over your proposal, but am not quite sure I understand your > objective. Is your intent to be able to step through IR source in a > debugger and inspect intermediate state? If so, you may consider > whether "simply" inserting debug metatadata into your IR which describes > the IR source, and then compiling it gives you your desired result. A pass that does precisely this has been contributed by someone from Intel at some point but got removed later on for reasons I don't recall. It might be worth to scan the archives. Tobias

I've scanned over your proposal, but am not quite sure I understand your objective. Is your intent to be able to step through IR source in a debugger and inspect intermediate state? If so, you may consider whether "simply" inserting debug metatadata into your IR which describes the IR source, and then compiling it gives you your desired result. For the record, the current interpreter is poorly maintained, known to be somewhat buggy, and I don't believe anyone is actively working on it. Philip On 03/22/2016 06:00 PM, Janek van Oirschot...

...not quite sure I understand your >> objective. Is your intent to be able to step through IR source in a >> debugger and inspect intermediate state? Yes, that is what I had in mind with this proposal. >>If so, you may consider >> whether "simply" inserting debug metatadata into your IR which describes >> the IR source, and then compiling it gives you your desired result. > > > A pass that does precisely this has been contributed by someone from Intel > at some point but got removed later on for reasons I don't recall. > It might be worth to s...

...our >>> objective. Is your intent to be able to step through IR source in a >>> debugger and inspect intermediate state? > > Yes, that is what I had in mind with this proposal. > >>> If so, you may consider >>> whether "simply" inserting debug metatadata into your IR which describes >>> the IR source, and then compiling it gives you your desired result. >> >> >> A pass that does precisely this has been contributed by someone from Intel >> at some point but got removed later on for reasons I don't recall. >&gt...

Hello, I have created a first draft GSoC project proposal for a IR level interpreter debugger. I have omitted some contact information as it is currently a public document (can be given upon request). Feedback and comments are appreciated. Proposal: https://docs.google.com/document/d/1Rhq0hsc6unMrd1IfxBYd_jdINt_eCAs0dq-dhjtRePo/edit?usp=sharing Kind regards, Janek van Oirschot

...just have the LLVM libraries do it automatically for the "built-in" stuff? Having a separate namespace of enums is going to get confusing. Practically every day I curse the fact that "int" is different than "MyInt" in C++. :-/ - Defaulting alignment to 1 when metatadata is not present is going to be a huge performance hit on many architectures. I hope we can find a better solution. I'm not sure what it is yet because we have to maintain safety. I just fear a Pass inadvertantly dropping metadata and really screwing things up. This looks very promisi...

...g. > Practically > every day I curse the fact that "int" is different than "MyInt" in C > ++. :-/ "builtin" metadata would also be registered, the only magic would be that the encoding would be smaller in the IR. > - Defaulting alignment to 1 when metatadata is not present is going > to be a > huge performance hit on many architectures. I hope we can find a > better > solution. I'm not sure what it is yet because we have to maintain > safety. > I just fear a Pass inadvertantly dropping metadata and really > screwin...

...ve. Is your intent to be able to step through IR source in a >>>> debugger and inspect intermediate state? >> >> Yes, that is what I had in mind with this proposal. >> >>>> If so, you may consider >>>> whether "simply" inserting debug metatadata into your IR which >>>> describes >>>> the IR source, and then compiling it gives you your desired result. >>> >>> >>> A pass that does precisely this has been contributed by someone from >>> Intel >>> at some point but got remo...

On 16 January 2017 at 15:31, Sean Silva <chisophugis at gmail.com> wrote: > Do we have any open projects on LLD? > > I know we usually try to avoid any big "projects" and mainly add/fix things > in response to user needs, but just wondering if somebody has any ideas. > > Some really generic/simple stuff I can think of: > 1. trying out LLD on a large program

I've got a suggestion for a refinement: Right now, we have classes like DILocation that wrap an MDNode* to provide more convenient access to it. It would be more convenient for users if instead of MDNode *DbgInfo = Inst->getMD(MDKind::DbgTag); Inst2->setMD(MDKind::DbgTag, DbgInfo); they could write: DILocation DbgInfo = Inst->getMD<DILocation>();

Devang's work on debug info prompted this, thoughts welcome: http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt -Chris