<?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: Gem: A Generic Function Binding Interface</title>
	<atom:link href="http://scottbilas.com/publications/gem-fubi/feed/" rel="self" type="application/rss+xml" />
	<link>http://scottbilas.com</link>
	<description>Take what you want, and leave the rest (just like your salad bar).</description>
	<lastBuildDate>Mon, 06 Feb 2012 03:15:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott</title>
		<link>http://scottbilas.com/publications/gem-fubi/#comment-424</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Mon, 08 Mar 2010 04:33:53 +0000</pubDate>
		<guid isPermaLink="false">http://scottbilas.wordpress.com/gem-a-generic-function-binding-interface/#comment-424</guid>
		<description>GCC has an inline assembler language that you can use. IBM has a page I found on it that can get you started.

http://www.ibm.com/developerworks/linux/library/l-ia.html

Of course, it requires learning assembly language to get anywhere. But you can cheat a little by looking at the output of unoptimized assembly code in a debugger. In fact, that&#039;s how I figured out how all the different calling conventions of the VC++ compiler worked in memory. Make a function of a particular type, call it from another, then step through the debugger in disassembly view, and you&#039;ll be able to work out how it operates, and what the different assembly opcodes are.</description>
		<content:encoded><![CDATA[<p>GCC has an inline assembler language that you can use. IBM has a page I found on it that can get you started.</p>
<p><a href="http://www.ibm.com/developerworks/linux/library/l-ia.html" rel="nofollow">http://www.ibm.com/developerworks/linux/library/l-ia.html</a></p>
<p>Of course, it requires learning assembly language to get anywhere. But you can cheat a little by looking at the output of unoptimized assembly code in a debugger. In fact, that&#8217;s how I figured out how all the different calling conventions of the VC++ compiler worked in memory. Make a function of a particular type, call it from another, then step through the debugger in disassembly view, and you&#8217;ll be able to work out how it operates, and what the different assembly opcodes are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boro</title>
		<link>http://scottbilas.com/publications/gem-fubi/#comment-423</link>
		<dc:creator>Boro</dc:creator>
		<pubDate>Sat, 06 Mar 2010 19:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://scottbilas.wordpress.com/gem-a-generic-function-binding-interface/#comment-423</guid>
		<description>Do I need an assembler like TASM in order to make it work or is there a way to make sure the GCC compiler (used by code::Blocks) uses the assembly code. I&#039;m unfamiliar with assembly.</description>
		<content:encoded><![CDATA[<p>Do I need an assembler like TASM in order to make it work or is there a way to make sure the GCC compiler (used by code::Blocks) uses the assembly code. I&#8217;m unfamiliar with assembly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

