<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Wrong line numbers expanded while compiling shaders"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106590#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Wrong line numbers expanded while compiling shaders"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106590">bug 106590</a>
from <span class="vcard"><a class="email" href="mailto:kenneth@whitecape.org" title="Kenneth Graunke <kenneth@whitecape.org>"> <span class="fn">Kenneth Graunke</span></a>
</span></b>
<pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=106590#c5">comment #5</a>)
<span class="quote">> This seems like a duplicate of
>
> <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Failed to parse macro "#line""
href="show_bug.cgi?id=106807">https://bugs.freedesktop.org/show_bug.cgi?id=106807</a>
>
> My faint recollection is that the specification of the __LINE__ macro is
> inconsistent. If, as Ken says, this has been removed from the
> specification, why are we looking at patches to change the implementation?</span >
No, __LINE__ is perfectly well defined and not going away. #line directives to
alter the current line using expressions is going away. I'm pretty sure
Zhaowei Yuan's patch fixes a real bug we've had for a long time.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>