Let CI's sanitizer job use clang's default version#13219
Let CI's sanitizer job use clang's default version#13219shindere merged 1 commit intoocaml:trunkfrom
Conversation
MisterDA
left a comment
There was a problem hiding this comment.
The end of the script is commented out but could be updated too. I suggest to name the variable llvm_version.
5053922 to
81e91b0
Compare
|
Thanks a lot for the two suggestions, that I did take into account.
I didn't dare to modify the commented bit because it was referring to a
different llvm version, but it's probably better to do that and be
homogeneous.
I also had to slightly shorten the right bannter in the first invocation
of `echo` to keep the line length below 80 characters so I went ahead
and also shortened the other right bannbters form 10 `=` signs to 8, for
consistency between the different `echo` commands and also with the
length of the left banner.
|
This is to avoid having to maintain a hard-coded version
81e91b0 to
5d16740
Compare
|
Much neater, thanks! |
OlivierNicole
left a comment
There was a problem hiding this comment.
Looks correct to me too. I don’t know why version 14 (and even 9) are hardcoded, but if there’s no good reason, I’m all for moving to a more recent and regularly updated version.
|
Olivier Nicole (2024/06/05 05:58 -0700):
@OlivierNicole approved this pull request.
Thanks!
I don’t know why version 14 (and even 9) are hardcoded, but if there’s
no good reason, I’m all for moving to a more recent and regularly
updated version.
My understanding is that one had to know which version we were using so
that one could use the right `llvm-symbolizer`.
So the version had to be explixcit, and I think 14 and 9 were those
which were state of the art at the time.
As I understand it, `ASAN_SYMBOLIZER_PATH` and `TSAN_SYMBOLIZER_PATH`
MUST contain the path of the tool. Them being undefined just means
`don't use the tool at all` rather than `use the tool of the same LLVM
version`. Sadly.
|
|
#13290 will also modify the script. I think this PR should be merged before. I don't see anything holding it back. |
Do you have
I can rebase my PRs once this one is merged. |
Let CI's sanitizer job use clang's default version (cherry picked from commit f4b13c2)
Let CI's sanitizer job use clang's default version (cherry picked from commit f4b13c2)
Let CI's sanitizer job use clang's default version (cherry picked from commit f4b13c2)
Let CI's sanitizer job use clang's default version (cherry picked from commit f4b13c2)
This is to avoid having to maintain a hard-coded version number
@xavierleroy may like this. Also discussed recenty with both @MisterDA and @OlivierNicole.
It may be interesting to backport this to other release branches, which
would make it possible to uninstall the older clang versions from the
server. @Octachron may have an opinion on this.