search for: asmverbose

...e: > Attached is a patch to print asm comments for spill information. > We've discussed the mechanisms before but I wanted to run the > patch by everyone before I start to commit pieces. The Offset->FrameIndex mapping seems rather heavy-weight, as any expense is incurred even when AsmVerbose is off. Would it be possible to use MachineMemOperands instead? In theory, they should already be preserving the needed information. If they're not sufficient, could they be improved? There is work going on to improve the register allocator's ability to use rematerlialization. In a wor...

...atch to print asm comments for spill information. > > We've discussed the mechanisms before but I wanted to run the > > patch by everyone before I start to commit pieces. > > The Offset->FrameIndex mapping seems rather heavy-weight, as > any expense is incurred even when AsmVerbose is off. Would it > be possible to use MachineMemOperands instead? In theory, > they should already be preserving the needed information. If > they're not sufficient, could they be improved? Yeah, I'm not totally happy with that mapping either. With MachineMemOperands, would t...

Attached is a patch to print asm comments for spill information. We've discussed the mechanisms before but I wanted to run the patch by everyone before I start to commit pieces. -Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: spillcomments.patch Type: text/x-diff Size: 58930 bytes Desc: not available URL:

On Monday 14 September 2009 12:32, David Greene wrote: > > The Offset->FrameIndex mapping seems rather heavy-weight, as > > any expense is incurred even when AsmVerbose is off. Would it > > be possible to use MachineMemOperands instead? In theory, > > they should already be preserving the needed information. If > > they're not sufficient, could they be improved? > > Yeah, I'm not totally happy with that mapping either. With >...

When using LLVM as a JIT compiler, you can use module.dump() to show the generated intermediate code, which is good. Is there similarly a programmatic way to show the generated x64 machine code in assembly format? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160406/c7d22dab/attachment.html>

On Sep 14, 2009, at 10:34 AM, David Greene wrote: > On Monday 14 September 2009 12:32, David Greene wrote: > > >>> The Offset->FrameIndex mapping seems rather heavy-weight, as >>> >>> any expense is incurred even when AsmVerbose is off. Would it >>> >>> be possible to use MachineMemOperands instead? In theory, >>> >>> they should already be preserving the needed information. If >>> >>> they're not sufficient, could they be improved? >>> >> >>...

...We've discussed the mechanisms before but I wanted to run the >>> >>> patch by everyone before I start to commit pieces. >>> >> >> >> The Offset->FrameIndex mapping seems rather heavy-weight, as >> >> any expense is incurred even when AsmVerbose is off. Would it >> >> be possible to use MachineMemOperands instead? In theory, >> >> they should already be preserving the needed information. If >> >> they're not sufficient, could they be improved? >> > > Yeah, I'm not totally happy wit...

...ntatively, SourceInterlave that would be responsible of printing the lines related to the instructions. SourceInterleave would take care of loading the files and making sure the source code lines are emitted as comments. This handler would be enabled through MCOptions (similar to what happens with AsmVerbose). The current option is tentatively called AsmSource. Currently AsmPrinterHandler mechanism looks slightly geared towards debug information but it also used for EH. So I think using it for printing interleaved source is a good fit. - Discussion In case this proposal is positively received I woul...

...fo"}, {"_ZL14ShowMCEncoding", "ShowMCEncoding"}, {"_ZL10ShowMCInst", "ShowMCInst"}, {"_ZL15EnableMCLogging", "EnableMCLogging"}, {"_ZL17VerifyMachineCode", "VerifyMachineCode"}, {"_ZL10AsmVerbose", "AsmVerbose"}, {"_ZL20EnableFastISelOption", "EnableFastISelOption"}, {"_ZL17EnableSplitGEPGVN", "EnableSplitGEPGVN"}, {"_ZL9EnableLDV", "EnableLDV"}, {"_ZL12DisableReMat", "DisableReMat&...