5 Commits

Author	SHA1	Message	Date
Josh Stone	1b79bb937f	Add inline comments why we're forcing the target cpu	2024-05-01 16:54:20 -07:00
Josh Stone	706f06c39a	Use an explicit x86-64 cpu in tests that are sensitive to it ... There are a few tests that depend on some target features **not** being enabled by default, and usually they are correct with the default x86-64 target CPU. However, in downstream builds we have modified the default to fit our distros -- `x86-64-v2` in RHEL 9 and `x86-64-v3` in RHEL 10 -- and the latter especially trips tests that expect not to have AVX. These cases are few enough that we can just set them back explicitly.	2024-05-01 15:25:26 -07:00
许杰友 Jieyou Xu (Joe)	6e48b96692	[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives	2024-02-22 16:04:04 +00:00
Zalathar	58d62fc271	Don't accidentally detect the commit hash as an `fadd` instruction	2023-10-10 16:59:49 +11:00
Caleb Zulawski	cdb9de7e8b	Add codegen test ensuring always-inline closures don't bypass target features	2023-07-16 21:26:08 -04:00