During ISel lowering, there are some stubs I realize that I need to emit during AsmPrinter. The question is: where to store that information? As a hack it could be stored in Subtarget. If there is a reasonable place to put it, it could be store in Module. Any ideas? It's just a list of functions that I need to generate stubs for. I know the possible elements of the list. It's a hardcoded list. Any ideas? TIA. Reed
On 01/21/2014 05:05 PM, reed kotler wrote:> During ISel lowering, there are some stubs I realize that I need to emit > during AsmPrinter. > > The question is: where to store that information? > > As a hack it could be stored in Subtarget. > > If there is a reasonable place to put it, it could be store in Module. > > Any ideas? > > It's just a list of functions that I need to generate stubs for. > I know the possible elements of the list. It's a hardcoded list. > > Any ideas? > > TIA. > > ReedI suppose that I could use module metadata for this.
On Jan 22, 2014, at 8:22 AM, Reed Kotler <rkotler at mips.com> wrote:> On 01/21/2014 05:05 PM, reed kotler wrote: >> During ISel lowering, there are some stubs I realize that I need to emit >> during AsmPrinter. >> >> The question is: where to store that information? >> >> As a hack it could be stored in Subtarget. >> >> If there is a reasonable place to put it, it could be store in Module. >> >> Any ideas? >> >> It's just a list of functions that I need to generate stubs for. >> I know the possible elements of the list. It's a hardcoded list. >> >> Any ideas?I don’t really know what you’re doing, but there’s already a MipsMachineFunctionInfo... -Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140122/61a759f1/attachment.html>