<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>RISC-V &#8211; jcomes.org</title>
	<atom:link href="https://jcomes.org/category/risc-v/feed" rel="self" type="application/rss+xml" />
	<link>https://jcomes.org</link>
	<description></description>
	<lastBuildDate>Sat, 28 Mar 2026 18:07:56 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">204893580</site>	<item>
		<title>AFL++ Instrumentation in Practice: A Trace from Compilation to Fuzz II</title>
		<link>https://jcomes.org/afl-from-compilation-to-fuzz-ii</link>
		
		<dc:creator><![CDATA[Jcomes]]></dc:creator>
		<pubDate>Tue, 16 Sep 2025 06:55:00 +0000</pubDate>
				<category><![CDATA[ARM]]></category>
		<category><![CDATA[Binary explotation]]></category>
		<category><![CDATA[Fuzzing]]></category>
		<category><![CDATA[RISC-V]]></category>
		<category><![CDATA[Userland]]></category>
		<category><![CDATA[x86_64]]></category>
		<guid isPermaLink="false">https://jcomes.org/?p=1037</guid>

					<description><![CDATA[In the previous post, we stopped at the point where AFL++ had produced instrumented binaries with PCGUARD and LTO. In this installment, we pick up the story at runtime: tracing the execution of those binaries, observing how coverage signals are collected, and following how afl-fuzz consumes that feedback to discover new paths. This is where [&#8230;]]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1037</post-id>	</item>
		<item>
		<title>AFL++ Instrumentation in Practice: A Trace from Compilation to Fuzz I</title>
		<link>https://jcomes.org/afl-from-compilation-to-fuzz-i</link>
		
		<dc:creator><![CDATA[Jcomes]]></dc:creator>
		<pubDate>Tue, 09 Sep 2025 06:55:00 +0000</pubDate>
				<category><![CDATA[ARM]]></category>
		<category><![CDATA[Binary explotation]]></category>
		<category><![CDATA[Fuzzing]]></category>
		<category><![CDATA[RISC-V]]></category>
		<category><![CDATA[Userland]]></category>
		<category><![CDATA[x86_64]]></category>
		<guid isPermaLink="false">https://jcomes.org/?p=953</guid>

					<description><![CDATA[In the previous post, we laid out the theoretical map of AFL++’s instrumentation modes, from the classic edge coverage to modern LLVM-based techniques. With that foundation in place, it’s time to move from theory to practice. This article focuses on the compilation process with afl-cc: how LTO and PCGUARD instrumentation are inserted into the binary, [&#8230;]]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">953</post-id>	</item>
		<item>
		<title>An Introduction to AFL++ Instrumentation Modes</title>
		<link>https://jcomes.org/afl-instrumentation-modes</link>
		
		<dc:creator><![CDATA[Jcomes]]></dc:creator>
		<pubDate>Tue, 02 Sep 2025 06:55:00 +0000</pubDate>
				<category><![CDATA[ARM]]></category>
		<category><![CDATA[Binary explotation]]></category>
		<category><![CDATA[Fuzzing]]></category>
		<category><![CDATA[RISC-V]]></category>
		<category><![CDATA[Userland]]></category>
		<category><![CDATA[x86_64]]></category>
		<guid isPermaLink="false">https://jcomes.org/?p=893</guid>

					<description><![CDATA[AFL++ has earned its reputation as a top-tier fuzzer thanks to its clever use of code coverage to guide the search for bugs. This series takes a deep dive into that process. In this first post, we’ll explore the instrumentation modes AFL++ uses to generate coverage—from the classic AFL edge hash to modern LLVM-based approaches. [&#8230;]]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">893</post-id>	</item>
		<item>
		<title>ROPV &#8211; ROP gadget finder tool for RISC-V binaries</title>
		<link>https://jcomes.org/ropv</link>
		
		<dc:creator><![CDATA[Jcomes]]></dc:creator>
		<pubDate>Wed, 17 Aug 2022 17:35:48 +0000</pubDate>
				<category><![CDATA[Binary explotation]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[RISC-V]]></category>
		<category><![CDATA[Userland]]></category>
		<guid isPermaLink="false">https://jcomes.org/?p=122</guid>

					<description><![CDATA[As my first post, I would like to talk about my final degree project. The idea behind the project was to build a program like ropshell, that searches for ROP gadgets but only focused in binaries from the RISC-V architecture. In this post I&#8217;ll be explaining the motivation behind this work, some background around Return [&#8230;]]]></description>
		
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">122</post-id>	</item>
	</channel>
</rss>
