Displaying 3 results from an estimated 3 matches for "current_column".
2007 Aug 15
0
[LLVMdev] Extending AsmPrinter
On Tue, 14 Aug 2007, David Greene wrote:
>> Yes, this is one advantage, another is that we wouldn't have to fix the
>> same bug in multiple places :)
>
> Right. I've figured out where I need to make the changes in AsmWriterEmitter
> given the current design.
Ok, cool.
> I'm trying out a few interesting things here based on custom streambufs.
> It requires
2007 Aug 15
1
[LLVMdev] Extending AsmPrinter
...ic column (by padding with spaces if necessary). This makes
it easy to line up comments, for example.
This would be quite a bit uglier with C stdio. For example:
// Custom streambuf (pseudo-llvm APIs)
instr->print(O);
O << comment("Place after instruction");
// C stdio
int current_column = instr->print(outfile);
printComment(current_column, "Place after instruction");
This means that every ::print/::dump/etc API that's used to print asm has to
track columns by parsing output strings and looking for newlines and tabs.
With a custom streambuf it's automatic....
2007 Aug 15
3
[LLVMdev] Extending AsmPrinter
On Monday 13 August 2007 15:50, Chris Lattner wrote:
> > I also have a few questions on the general design of AsmPrinter. Why is
> > runOnMachineFunction implemented for each target AsmPrinter? I would
>
> Historical reasons that aren't very good. Over the years, I've taken
> several stabs at merging the asmprinters from various targets together.
> They used to