<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: shed some bytes</title>
	<atom:link href="http://blackpawn.com/blog/?feed=rss2&#038;p=6" rel="self" type="application/rss+xml" />
	<link>http://blackpawn.com/blog/?p=6</link>
	<description></description>
	<lastBuildDate>Tue, 03 Aug 2010 17:50:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Lost in the Triangles &#187; Blog Archive &#187; 64k coding continued</title>
		<link>http://blackpawn.com/blog/?p=6&#038;cpage=1#comment-2924</link>
		<dc:creator>Lost in the Triangles &#187; Blog Archive &#187; 64k coding continued</dc:creator>
		<pubDate>Sat, 24 Mar 2007 17:44:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackpawn.com/test.php/?p=6#comment-2924</guid>
		<description>[...] Compiling HLSL in two steps (HLSL-&gt;asm and asm-&gt;bytecode) instead of direct (HLSL-&gt;bytecode) gets rid of the constant table, some copyright strings and hence is good. (thanks blackpawn!) [...]</description>
		<content:encoded><![CDATA[<p>[...] Compiling HLSL in two steps (HLSL-&gt;asm and asm-&gt;bytecode) instead of direct (HLSL-&gt;bytecode) gets rid of the constant table, some copyright strings and hence is good. (thanks blackpawn!) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NeARAZ</title>
		<link>http://blackpawn.com/blog/?p=6&#038;cpage=1#comment-15</link>
		<dc:creator>NeARAZ</dc:creator>
		<pubDate>Tue, 13 Dec 2005 08:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackpawn.com/test.php/?p=6#comment-15</guid>
		<description>&lt;p&gt;
Yeah, I&#039;m already using that (that&#039;s why I have no use of the constant table). Actually, a macro processing is more convenient: have a header file &#039;constants.h&#039; with something like:&lt;/p&gt;&lt;p&gt;

#define SHC_WORLDMAT 0&lt;br /&gt;#define SHC_VIEWPROJMAT 4&lt;br /&gt;// etc.&lt;br /&gt;#define REG(x) register(c##x)

&lt;/p&gt;&lt;p&gt;Then use this header file in both HLSL (float4x4 world : REG(0)) and C++ (just use the constants)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>
Yeah, I&#8217;m already using that (that&#8217;s why I have no use of the constant table). Actually, a macro processing is more convenient: have a header file &#8216;constants.h&#8217; with something like:</p>
<p>#define SHC_WORLDMAT 0<br />#define SHC_VIEWPROJMAT 4<br />// etc.<br />#define REG(x) register(c##x)</p>
<p>Then use this header file in both HLSL (float4x4 world : REG(0)) and C++ (just use the constants)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blackpawn</title>
		<link>http://blackpawn.com/blog/?p=6&#038;cpage=1#comment-14</link>
		<dc:creator>blackpawn</dc:creator>
		<pubDate>Tue, 13 Dec 2005 08:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackpawn.com/test.php/?p=6#comment-14</guid>
		<description>
glad to help. one other useful bit is that if you don&#039;t already know, you can force HLSL to map a constant to a particular register using for example:

float4x4 world : register(c0);</description>
		<content:encoded><![CDATA[<p>glad to help. one other useful bit is that if you don&#8217;t already know, you can force HLSL to map a constant to a particular register using for example:</p>
<p>float4x4 world : register(c0);</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NeARAZ</title>
		<link>http://blackpawn.com/blog/?p=6&#038;cpage=1#comment-13</link>
		<dc:creator>NeARAZ</dc:creator>
		<pubDate>Tue, 13 Dec 2005 08:38:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.blackpawn.com/test.php/?p=6#comment-13</guid>
		<description>
Thanks for the tip! Exactly this issue is what I was worried about at the moment. The version string is probably okay (exe compressor should take care of it); but the constant tables were useless in my case.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip! Exactly this issue is what I was worried about at the moment. The version string is probably okay (exe compressor should take care of it); but the constant tables were useless in my case.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
