<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 6, 2012, at 8:45 AM, Craig Topper <<a href="mailto:craig.topper@gmail.com">craig.topper@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Tue, Mar 6, 2012 at 8:32 AM, Jakob Stoklund Olesen <span dir="ltr"><<a href="mailto:stoklund@2pi.dk">stoklund@2pi.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Mar 6, 2012, at 8:23 AM, Craig Topper wrote:<br>
<br>
> It might not work with 64k registers. I didn't make the change to use one long string literal. I just exploited the C++ restriction that a string literal cant contain more 64K characters. I'll add asserts since that restriction might only be a warning.<br>
<br>
</div>That's just a minimum limit, clang and gcc have much larger limits. I expect so does most other modern compilers.<br></blockquote></div></blockquote><br><blockquote type="cite">I know its the minimum limit, but clang in default build configuration and Werror will fail if the string literal is larger than 64K doesn't that sort make the code base after obey the minimum limit?<br></blockquote><div><br></div><div>Well, that means you have found a potential portability problem. You shouldn't make it worse by propagating the assumptions, try to fix it instead.</div><div><br></div><div>As I told you yesterday, people are writing targets with many registers. This patch would probably have broken those targets.</div><div><br></div><div>Please do not change the limits of the target descriptions without discussing it on the mailing list first.</div><div><br></div><div>/jakob</div><div><br></div></div></body></html>