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
On 10/24/23 00:01, Frager, Neal 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 version
6.00 or 8.30 which will calculate to values 600 and 830.
The
>>> 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
On 10/23/23 11:37, Frager, Neal wrote:
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
> 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
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 version
6.00 or 8.30 which will calculate to values 600 and 830.
The
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'
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've not tried this, just remembered doing something similar in the past.)
--Mar
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 when using the '-mcpu=
