Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.


This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

format of *.Uv2 entries?

Does anyone know if the format/meaning of all the entries in the *.Uv2 file is available? Some are pretty obvious (RunUsr 1), but others are not (T51FL=33392). I assume they all correspond to entries in the "Options for Target" dialog box, but don't know which are which.

Thanks,
Ed

Parents
  • I actually don't want to change them, but I *do* want to be able to know what differences mean.

    When checking a software change, I use Beyond Compare 2 to diff all the source code files. While doing this, I found that there were several differences in the *.Uv2 file as compared to the baseline. (I found differences in the *.opt file too, but since those are mostly local environment-type settings, I don't really care about those.)

    So I want to know how the two software sets may be different in compiler options and whatever else the *.Uv2 file might indicate.

Reply
  • I actually don't want to change them, but I *do* want to be able to know what differences mean.

    When checking a software change, I use Beyond Compare 2 to diff all the source code files. While doing this, I found that there were several differences in the *.Uv2 file as compared to the baseline. (I found differences in the *.opt file too, but since those are mostly local environment-type settings, I don't really care about those.)

    So I want to know how the two software sets may be different in compiler options and whatever else the *.Uv2 file might indicate.

Children
No data