<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jun 26, 2013, at 3:51 PM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; 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; float: none; display: inline !important;">Can you suggest an alternative solution? Can you describe why you don't think metadata is the right container? This alone isn't really helpful at moving us toward something that there has been widespread agreement LLVM needs.</span></blockquote></div><br><div>Hi Chandler, </div><div><br></div><div>Sure, we can talk about serializing MF. But the discussion should focus on serializing MF, and not multi-line metadata support, which is only one of the possible solutions. I understand the problem that Dan mentioned (that MF references IR), and I am sure that there are other problems that he did not mention. I would be happy to hear more about other solutions that you considered and other problems that you ran into. Have you considered using a new format that embeds LLVM-IR ? </div><div><br></div><div>Thanks,</div><div>Nadav </div></body></html>