Skip the ThinLTO cache tests on NetBSD. They require 'touch' being
able to alter atime of files, while NetBSD inhibits atime updates
when filesystem is mounted noatime.
Details
Diff Detail
Event Timeline
test/ThinLTO/X86/cache.ll | ||
---|---|---|
2 | Please include an inline comment why unsupported. |
What would happen if the thin LTO cache is used on such a system? Do we need to put something in the thin LTO code to emit some sort of error, if this is attempted?
I don't really know; I suppose the same thing as if it were used on any regular system with noatime. However, I believe NetBSD is only special here as we can't set up the test environment with past dates.
Is this only optimization (i.e. not about generating correct result)? If so we will ignore it and align the NetBSD kernel behavior to Linux/FreeBSD.
LGTM. Thinking about it a bit more, and I don't think using the cache will cause any actual problems if everything has the same access time, beyond potentially doing unnecessary work.
test/ThinLTO/X86/cache.ll | ||
---|---|---|
1–2 | Please move this comment down to the first set of RUN commands, since that's what it's describing. The UNSUPPORTED directive and associated comment are best kept at the top of the file before anything else. |
Please include an inline comment why unsupported.