On 03/22/2017 09:54 AM, Bob von Knobloch wrote:
> Inspecting the assembly, I found that the interrupt was suspect.
> The 'old' code pushed the registers that it needed, the 'new' TI 
> compiler pushes (and, of course, later pulls) all of the registers from 
> r4 - r15 inclusive.

I complained about the failure to follow the EABI (which registers a
called function is required to preserve) to the TI forums some time ago.
(April 2015)

Apparently it still isn't fixed.

Calling another function from the ISR was what triggers this bad
behaviour. Especially if the called function is in another file.

David W. Schultz
"Life without stock is barely worth living..." - Anthony Bourdain

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Mspgcc-users mailing list

Reply via email to