Uploaded image for project: 'Embedded Software & Tools'
  1. Embedded Software & Tools
  2. EXT_EP-10657

C28 --isr_save_vcu_regs=on does not always save/restore VCU registers

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • Code Generation Tools
    • CODEGEN-9422
    • Hide
      C2000_21.6.0.LTS
      C2000_20.2.0.LTS
      Show
      C2000_21.6.0.LTS C2000_20.2.0.LTS
    • Hide
      C2000_21.12.0.STS*
      C2000_21.6.1.LTS*
      C2000_20.2.6.LTS*
      Show
      C2000_21.12.0.STS* C2000_21.6.1.LTS* C2000_20.2.6.LTS*
    • default
    • Hide
      If an interrupt routine does not save/restore VCU registers with option --isr_save_vcu_regs=on, then work arounds to force the VCU register save/restores include: add a function call to the interrupt, or add additional code that requires using save-on-call registers.
      Show
      If an interrupt routine does not save/restore VCU registers with option --isr_save_vcu_regs=on, then work arounds to force the VCU register save/restores include: add a function call to the interrupt, or add additional code that requires using save-on-call registers.

      For interrupt routines, C28 option --isr_save_vcu_regs=on/off only saves/restores VCU registers if any save-on-call register is also save/restored.  

      With --isr_save_vcu_regs=on, VCU registers are save/restored if:

      • the interrupt routine makes any function calls since all save-on-call registers are saved/restored
      • the interrupt routine generates any save-on-call save/restores  

      If an interrupt routine does not make any function calls, and does not use any save-on-call registers, then option --isr_save_vcu_regs=on will not work to generate VCU register save/restores.

       

            syncuser TI User
            syncuser TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: