__crc32 give different results between Hightech Tricore GCC 4.6.3.0 and Hightech Tricore GCC 4.6.6.1

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Hedi
Level 1
Level 1
First reply posted First question asked Welcome!

On a project i'm working on, i have to change the compiler from 4.6.6.1 to 4.6.3.0.

I discovered that both compilers call the CRC32 instruction, but i get different result for the same data.

 

Any ideas are welcome, where should i look ? has anyone encountered this kind of behavior before ?

 

Thanks in advance.

0 Likes
1 Solution
agostonrobert
Level 1
Level 1
First solution authored First reply posted Welcome!

Hi, the instruction crc32 before 4.6.4.0 has been implemented according the specification V1.0 D9 2010-11,
but in a later version of the manual V1.0 D12 the specification has changed.
There is an assembler option --warn-crc that will point you to the relevant assembler source lines that you may want to review.

View solution in original post

0 Likes
2 Replies
µC_Wrangler
Employee
Employee
50 solutions authored 100 sign-ins 25 likes received

The truth is almost always in the source code - can you share a snippet?

How do you know the data is the same?  Are you comparing hex files?

0 Likes
agostonrobert
Level 1
Level 1
First solution authored First reply posted Welcome!

Hi, the instruction crc32 before 4.6.4.0 has been implemented according the specification V1.0 D9 2010-11,
but in a later version of the manual V1.0 D12 the specification has changed.
There is an assembler option --warn-crc that will point you to the relevant assembler source lines that you may want to review.

0 Likes