[Bug]: svdconv generates wrong __VTOR_PRESENT when optional vtorPresent is absent from *.svd

[joshuanekl-skyworks]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

According to the Open-CMSIS-SVD spec for the vtorPresent field "If not specified, then VTOR is assumed to be present."
If a *.svd file with <cpu><name>CM33</name> ... is lacking a <vtorPresent> field, the following output is generated.
#define __VTOR_PRESENT 0 /*!< Set to 1 if CPU supports Vector Table Offset Register

Expected Behavior

If vtorPresent is absent from *.svd, I would expect the following
#define __VTOR_PRESENT 1 /*!< Set to 1 if CPU supports Vector Table Offset Register

Steps To Reproduce

No response

Affected tools

• cbuild
• cbuild-gen
• cpackget
• csolution
• packchk
• svdconv

Affected operating systems

• Windows amd64
• Windows arm64
• Linux amd64
• Linux arm64
• MacOS amd64
• MacOS arm64

Environment

No response