<?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>Zen 5c Archives - BenchLife.info</title>
	<atom:link href="https://benchlife.info/tag/zen-5c/feed/" rel="self" type="application/rss+xml" />
	<link>https://benchlife.info/tag/zen-5c/</link>
	<description>專注科技產業的趨勢報導與分析</description>
	<lastBuildDate>Wed, 24 Jul 2024 13:04:14 +0000</lastBuildDate>
	<language>zh-TW</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://benchlife.info/wp-content/uploads/2019/04/Transparent@512pw.png</url>
	<title>Zen 5c Archives - BenchLife.info</title>
	<link>https://benchlife.info/tag/zen-5c/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>定位與需求面向不同，AMD Zen 5 與 Zen 5c 處理器架構設計取捨</title>
		<link>https://benchlife.info/deep-dive-amd-zen-5-and-zen-5c/</link>
		
		<dc:creator><![CDATA[Chris.L]]></dc:creator>
		<pubDate>Wed, 24 Jul 2024 13:00:36 +0000</pubDate>
				<category><![CDATA[硬體零組件]]></category>
		<category><![CDATA[處理器]]></category>
		<category><![CDATA[AMD]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[Granite Ridge]]></category>
		<category><![CDATA[Strix Point]]></category>
		<category><![CDATA[Zen 5]]></category>
		<category><![CDATA[Zen 5c]]></category>
		<guid isPermaLink="false">https://benchlife.info/?p=72281</guid>

					<description><![CDATA[<p>更進一步了解 Zen 5 與 Zen 5c 的差異，還有 Zen 5 的一些細節。 Ryzen AI [&#8230;]</p>
<p>這篇文章 <a href="https://benchlife.info/deep-dive-amd-zen-5-and-zen-5c/">定位與需求面向不同，AMD Zen 5 與 Zen 5c 處理器架構設計取捨</a> 最早出現於 <a href="https://benchlife.info">BenchLife.info</a>。</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
