ve2vel.py unrecognized character occurs too often.

[kruus]

• ^ xor operator happens in code
• various other characters ['@`] etc. can appear in doxygen/markdown comments

I just change the line 38 'other' character class be the else: action and never raise the unknown character exception.

It is very useful that the script changes ve things inside strings, so it gives a decent starting point even for converting JIT code generators to the vel intrinsics :)

[kruus]

Also ve2vel(intrin) should convert LVS intrinsics

    intrin = re.sub(r'lvs_svs_u64', 'lvsl_svs', intrin)                                                                                                                                                                                                                                                                                                                  
    intrin = re.sub(r'lvs_svs_f64', 'lvsd_svs', intrin)                                                                                                                                                                                                                                                                                                                  
    intrin = re.sub(r'lvs_svs_f32', 'lvss_svs', intrin)

and there is no VL arg , None that gets added for this translation, so hasVL should really
include 'lvs' (there was never an _ve_svl_TYPE, so no corresponding change there).

Also, I translate old _ve_lvl(...) into /* _ve_lvl(...) */ comments by a slight tweak parse_lvl(self,comment=True). This helps double-checking VL assumptions esp. if working with the default None substitution for VL. I often have two or more active VL values, so I'd retain a little excess code history and delete the comments by hand after code testing.

Also, old condition codes VECC_Ixx (and AF and AT) should be added to complete vfmk support.

Hmmm. maybe easier for me to submit a pull request soon.

[k-ishizaka]

Great. I already converted all my ve intrinsics. Please submit a pull request.