Add clang-tidy checker to look for imprecise sub-object bounds.

[qwattash]

The clang-tidy checker should not do anything particularly complicated, it assumes that the structure is allocated at a properly aligned base and uses the offset of the fields to see whether the resulting capability would be exactly representable. The diagnostic is a bit verbose because I'm using it to get information out to plot, it would be nice to have some more structured output but I'm not sure whether there is a preferred way of doing that.

This also bumps the cheri-compressed-cap subtree.

[jrtc27]

Updating the subtree needs to be done specially as otherwise GitHub will rebase and screw up the hashes

[qwattash]

Updating the subtree needs to be done specially as otherwise GitHub will rebase and screw up the hashes

Uhm I thought I did it through git subtree but I may have done a quick hack just to check if it worked. Will edit it to make it the right way.

[arichardson]

Updating the subtree needs to be done specially as otherwise GitHub will rebase and screw up the hashes

Uhm I thought I did it through git subtree but I may have done a quick hack just to check if it worked. Will edit it to make it the right way.

The problem is that when you click rebase and merge the hashes change so it's no longer correct unless you push directly.

[qwattash]

Updating the subtree needs to be done specially as otherwise GitHub will rebase and screw up the hashes

Uhm I thought I did it through git subtree but I may have done a quick hack just to check if it worked. Will edit it to make it the right way.

The problem is that when you click rebase and merge the hashes change so it's no longer correct unless you push directly.

As an aside I thought git subtree was used but it appears that the git subrepo tool instead was used. I'm not familiar with it but attempting to use git subrepo pull <path> -b master fails with "Fatal: needed a single revision" and overwrites my last commit message with some text.

EDIT:
I think somehow the git subrepo information have gotten desynchronized with the cheri-compressed-cap repo

[arichardson]

Updating the subtree needs to be done specially as otherwise GitHub will rebase and screw up the hashes

Uhm I thought I did it through git subtree but I may have done a quick hack just to check if it worked. Will edit it to make it the right way.

The problem is that when you click rebase and merge the hashes change so it's no longer correct unless you push directly.

As an aside I thought git subtree was used but it appears that the git subrepo tool instead was used. I'm not familiar with it but attempting to use git subrepo pull <path> -b master fails with "Fatal: needed a single revision" and overwrites my last commit message with some text.

EDIT: I think somehow the git subrepo information have gotten desynchronized with the cheri-compressed-cap repo

I can take care of updating the compressed cap repo but I'd like to merge CTSRD-CHERI/cheri-compressed-cap#18 first since that includes an API change.

[qwattash]

Updating the subtree needs to be done specially as otherwise GitHub will rebase and screw up the hashes

Uhm I thought I did it through git subtree but I may have done a quick hack just to check if it worked. Will edit it to make it the right way.

The problem is that when you click rebase and merge the hashes change so it's no longer correct unless you push directly.

As an aside I thought git subtree was used but it appears that the git subrepo tool instead was used. I'm not familiar with it but attempting to use git subrepo pull <path> -b master fails with "Fatal: needed a single revision" and overwrites my last commit message with some text.
EDIT: I think somehow the git subrepo information have gotten desynchronized with the cheri-compressed-cap repo

I can take care of updating the compressed cap repo but I'd like to merge CTSRD-CHERI/cheri-compressed-cap#18 first since that includes an API change.

No worries, this is not urgent anyway. This just seems some tooling issue on my side. Let me know when it is safe to do, if you want me to do the cheri-compressed-cap bump :)