<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Joerg,<div><br></div><div>This feels like a natural place for an MCTargetAsmParser hook to do the target-specific bits. What do you think? I’d really like to be moving towards less target-specific stuff in the generic code.</div><div><br></div><div>-Jim</div><div><br></div><div><br><div><div>On Jul 13, 2013, at 11:10 AM, Joerg Sonnenberger <<a href="mailto:joerg@britannica.bec.de">joerg@britannica.bec.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hi all,<br>PowerPC assembler supports expressions like "1234@l". This doesn't with<br>MC right now, because the constant expression never reaches the target<br>layer. I wonder if it is really that useful to refactor this ATM,<br>especially since it likely makes sense to share the variant codes at<br>some point as many RISC platforms have similar needs in this area.<br><br>Joerg<br><span><ppc-parser.diff></span>_______________________________________________<br>llvm-commits mailing list<br><a href="mailto:llvm-commits@cs.uiuc.edu">llvm-commits@cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits</a></div></blockquote></div><br></div></body></html>