https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272652
--- Comment #7 from Mark Millard <[email protected]> --- (In reply to Vedran Miletic from comment #6) Two ways, depending on the results: A) one or both of llvm17 or llvm18 is fixed: then there might be a backport to llvm16 (and llvm17?) that was reasonable. B) Still broke in both llvm17 and llvm18: The problem is far more general that llvm16 based contexts and may well still be an issue when no supproted release uses prior to llvm17. I'll also note the the Version being "CURRENT" and the clang16 reference are inconsistent at this point. CURRENT does not use clang16 any more and may progress to llvm18 in the not distant future. If this is to only be about llvm16 (clang16), then the Version should be indicating 14.0-RELEASE, not CURRENT. (Unfortunately one can not indicate a range/list of Versions directly.) stable/14 is using llvm17 at this point, as I remember. So more than CURRENT is using llvm17. If the problem still exists in clang18, for example, it likely would be appropriate for the summary to indicate "clang16..clang18" or some such. (That would also be a good clue that interpreting Version is going to be problematical.) -- You are receiving this mail because: You are the assignee for the bug.
