Hi all,
We are working on tools that use the new bug identification hash, added in r251011, for bug suppression. The current hash is labelled in the plist file as “issue_hash_content_of_line_in_context”. There seems to be no way to predict the names of hashes in future versions.
Our products that use the bug identification are on a different release schedule to our clang compiler. These tools will not be able to take advantage of new hashes, unless they have a way to understand the future hash names. Is there a way we can make the tools forwards compatible?
Regards,
Sean Eveson
SN Systems - Sony Computer Entertainment Group
Hi all,
We are working on tools that use the new bug identification hash, added in r251011, for bug suppression. The current hash is labelled in the plist file as “issue_hash_content_of_line_in_context”. There seems to be no way to predict the names of hashes in future versions.
Our products that use the bug identification are on a different release schedule to our clang compiler. These tools will not be able to take advantage of new hashes, unless they have a way to understand the future hash names. Is there a way we can make the tools forwards compatible?
A discussion about this was started in http://reviews.llvm.org/D10305. Feel free to contribute! Also see http://clang-developers.42468.n3.nabble.com/analyzer-Changing-issue-hash-in-plists-td4047823.html.
Cheers,
Anna.