search for: bevinh

...ed in by sensible defaults: the function "number", the basic block number, predecessors and successors of a basic block, maybe allowing to leave out the llvm IR (though that probably is not allowed by CodeGen at the moment). - Matthias > On Apr 28, 2015, at 2:08 PM, Bevin Hansson <bevinh at sics.se> wrote: > > On 2015-04-28 20:18, Alex L wrote: >> 2015-04-28 10:15 GMT-07:00 Hal Finkel <hfinkel at anl.gov>: >> Hi Alex, >> I think this looks promising. What are the 1 an 4 above? How are you >> proposing to serialize operand flags (dead, etc.)?...

On 2015-04-28 19:14, Quentin Colombet wrote: > Personally I would rather not have to write YAML inputs but instead > resort on the what the machine dumps look like. That being said, I can > live with YAML :). > YAML is what is suggested in the FIXME for the textual Machine IR, so that might be the motivation behind Alex's choice. I sort of agree that it could be better to go

Hi, I'm Alex, and last summer I was working on the code coverage support for pgo for LLVM and clang at Apple. I'm currently interning at Apple again, and I'm planning to work on a project that was suggested to me by Bob Wilson. I plan on developing a text-based, human readable format that allows LLVM to serialize the machine level IR (The data structures like MachineFunction, etc.

2015-04-28 10:15 GMT-07:00 Hal Finkel <hfinkel at anl.gov>: > > ------------------------------ > > *From: *"Alex L" <arphaman at gmail.com> > *To: *"LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > *Sent: *Tuesday, April 28, 2015 11:56:42 AM > *Subject: *[LLVMdev] RFC: Machine Level IR text-based serialization format > >