Hi Mark,
> Le 23 oct. 2023 à 16:07, Hatle, Mark a écrit :
>
> Not sure if this will work, but there is a strverscmp function in libiberty
> that I think will work.
>
> So the microblaze version compare could be done as:
>
> #define MICROBLAZE_VERSION_COMPARE(VA,VB) strvercmp(VA, VB)
>
> (I'
> Le 23 oct. 2023 à 18:40, Michael Eager a écrit :
>
> On 10/22/23 22:48, Neal Frager wrote:
>> There is a microblaze cpu version 10.0 included in versal. If the
>> minor version is only a single digit, then the version comparison
>> will fail as version 10.0 will appear as 100 compared to ve
>>> There is a microblaze cpu version 10.0 included in versal. If the
>>> minor version is only a single digit, then the version comparison
>>> will fail as version 10.0 will appear as 100 compared to version
>>> 6.00 or 8.30 which will calculate to values 600 and 830.
>>> The issue can be seen w
There is a microblaze cpu version 10.0 included in versal. If the
minor version is only a single digit, then the version comparison
will fail as version 10.0 will appear as 100 compared to version
6.00 or 8.30 which will calculate to values 600 and 830.
The issue can be s
Hi Michael,
> The MICROBLAZE_VERSION_COMPARE was incorrectly using strcasecmp
> instead of strverscmp to check the mcpu version against feature
> options. By simply changing the define to use strverscmp, the new
> version 10.0 is treated correctly as a higher version than previous
> versions.
> Hi Michael,
>
>> The MICROBLAZE_VERSION_COMPARE was incorrectly using strcasecmp
>> instead of strverscmp to check the mcpu version against feature
>> options. By simply changing the define to use strverscmp, the new
>> version 10.0 is treated correctly as a higher version than previous
>>
