search for: x86_avx

> Maybe a target-specific attribute instead? It would still apply to all CCs, > but would never be dropped. That would work too, yes. I proposed metadata because it looks like it can be dropped, but that is not a big issue. I would be OK with an attribute too if that is more convenient or we want to make sure it is kept. Cheers, Rafael

...VM part) Add an x86-specific calling convention to the LLVM IR > which > > > > specifies that an external function will be compiled with AVX support and > > its > > > > function definition does not use any legacy SSE instructions, e.g., > > > > declare x86_avxcc i32 @foo() > > I would suggest using metadata instead. The reasons are: > > * It could be applied to functions with different calling conventions. > For example, on windows we would probably want to do this to thiscall > (methods) too. > * It the metadata is dropped, we would...