Automated handling of busted assembly tests

[workingjubilee]

There are assembly tests we know in advance are busted.

They

• specify a --target in the compiletest headers
• do not have only-{arch} in the compiletest headers
• are neither #![no_core] or #![no_std], and do not -Zbuild-std
• are testing assembly generation of the compiler, and especially including asm!

We could lint these automatically and probably should.

[Ezrashaw]

are neither #![no_core] or #![no_std], and do not -Zbuild-std are testing assembly generation of the compiler, and especially including asm!

Could you elaborate? I think that the test in my recent PR checks both of these boxes but is still useful.

As an aside, do you think this should be implemented in tidy or compiletest itself?

[workingjubilee]

That entire list is a single logical constraint.

[workingjubilee]

No idea on where this code could/should live, that feels like a vibes decision.

[thomcc]

compiletest is used out of tree (sort of) so probably tidy is more appropriate for this kind of thing.