<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ASM insn. support by proc. through API in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/ASM-insn-support-by-proc-through-API/m-p/1641420#M8462</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;I'm working on a project involving a disassembler that runs on its own binary (the app binary) for proactive optimization and process impact analysis, which needs to support multiple architectures. Currently, fetching information from documentation is a lengthy and somewhat inefficient process.&lt;/P&gt;&lt;P&gt;It could be interesting to introduce a secure layer within the CPU's microcode that developers can access as an API. This would allow the CPU to directly inform the code about its capabilities. Such a feature would be incredibly useful for HPC applications, which need minimal latency and precise infrastructure capability assessments. For developers focused on ultra-low-level optimization, it would be invaluable.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This could significantly simplify the updating of profiling and disassembly applications and, in my case, eliminate the need to update this part of the application.&lt;/P&gt;&lt;P&gt;It would be even more valuable to use a straightforward data format with distinct segments for each section—such as prefixes, op_codes, etc.—allowing us to directly retrieve the hexadecimal values. Even better would be the inclusion of fields related to the number of CPU cycles per instruction.&lt;/P&gt;&lt;P&gt;To my knowledge, no other CPU manufacturer, provides this type of feature.&lt;/P&gt;&lt;P&gt;Thanks for considering this, and I appreciate any feedback,&lt;/P&gt;&lt;P&gt;Delta_0ne.&lt;/P&gt;</description>
    <pubDate>Tue, 05 Nov 2024 18:09:16 GMT</pubDate>
    <dc:creator>Delta_0ne</dc:creator>
    <dc:date>2024-11-05T18:09:16Z</dc:date>
    <item>
      <title>ASM insn. support by proc. through API</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/ASM-insn-support-by-proc-through-API/m-p/1641420#M8462</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;I'm working on a project involving a disassembler that runs on its own binary (the app binary) for proactive optimization and process impact analysis, which needs to support multiple architectures. Currently, fetching information from documentation is a lengthy and somewhat inefficient process.&lt;/P&gt;&lt;P&gt;It could be interesting to introduce a secure layer within the CPU's microcode that developers can access as an API. This would allow the CPU to directly inform the code about its capabilities. Such a feature would be incredibly useful for HPC applications, which need minimal latency and precise infrastructure capability assessments. For developers focused on ultra-low-level optimization, it would be invaluable.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This could significantly simplify the updating of profiling and disassembly applications and, in my case, eliminate the need to update this part of the application.&lt;/P&gt;&lt;P&gt;It would be even more valuable to use a straightforward data format with distinct segments for each section—such as prefixes, op_codes, etc.—allowing us to directly retrieve the hexadecimal values. Even better would be the inclusion of fields related to the number of CPU cycles per instruction.&lt;/P&gt;&lt;P&gt;To my knowledge, no other CPU manufacturer, provides this type of feature.&lt;/P&gt;&lt;P&gt;Thanks for considering this, and I appreciate any feedback,&lt;/P&gt;&lt;P&gt;Delta_0ne.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Nov 2024 18:09:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/ASM-insn-support-by-proc-through-API/m-p/1641420#M8462</guid>
      <dc:creator>Delta_0ne</dc:creator>
      <dc:date>2024-11-05T18:09:16Z</dc:date>
    </item>
  </channel>
</rss>

