search for: x86_avxcc

...r pressure and hurts performance for AVX-to-AVX calls. My proposal: 1) (LLVM 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() 2) (Clang part) Add a function attribute to the clang front-end which specifies this calling convention, e.g., extern int foo() __attribute__((avx)); Function definitions in a translation unit compiled with -mavx architecture will implicitly have this attribute. Benefits: No vzeroupp...

...> > My proposal: > > 1) (LLVM 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 just produced slower but still cor...

...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 j...