<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>After enabling FPU in Kconfig, the computation speed remains unchanged. Why?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/121625/after-enabling-fpu-in-kconfig-the-computation-speed-remains-unchanged-why</link><description>HI, 
 I’m using nRF Connect SDK (NCS) v2.8.0 with the blinky example.nrf54l15dk, In the project, I configured the following in Kconfig: 
 
 
 
 
 kconfig 
 
 
 
 CONFIG_FPU=y 
CONFIG_FPU_SHARING=y 
 
 In the main function, I performed floating-point calculations</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 20 May 2025 08:24:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/121625/after-enabling-fpu-in-kconfig-the-computation-speed-remains-unchanged-why" /><item><title>RE: After enabling FPU in Kconfig, the computation speed remains unchanged. Why?</title><link>https://devzone.nordicsemi.com/thread/536115?ContentTypeID=1</link><pubDate>Tue, 20 May 2025 08:24:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ecf26509-3857-4df6-a61c-85b91008c49e</guid><dc:creator>joey</dc:creator><description>&lt;p&gt;&lt;span&gt;I set the optimization level to &amp;#39;Optimize for Debugging.&amp;#39; Does this need to be changed to the default setting?&amp;quot;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: After enabling FPU in Kconfig, the computation speed remains unchanged. Why?</title><link>https://devzone.nordicsemi.com/thread/536104?ContentTypeID=1</link><pubDate>Tue, 20 May 2025 07:55:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8870788-6fb4-404e-9216-13d6da0e0970</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Check the resulting assembly code - the optimizer will completely eliminate the floating point calculation in the loop. It could actually remove for loop entirely.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>