Implement Attribute Target MultiVersioning
GCC's attribute 'target', in addition to being an optimization hint,
also allows function multiversioning. We currently have the former
implemented, this is the latter's implementation.
This works by enabling functions with the same name/signature to coexist,
so that they can all be emitted. Multiversion state is stored in the
FunctionDecl itself, and SemaDecl manages the definitions.
Note that it ends up having to permit redefinition of functions so
that they can all be emitted. Additionally, all versions of the function
must be emitted, so this also manages that.
Note that this includes some additional rules that GCC does not, since
defining something as a MultiVersion function after a usage has been made illegal.
The only 'history rewriting' that happens is if a function is emitted before
it has been converted to a multiversion'ed function, at which point its name
needs to be changed.
Function templates and virtual functions are NOT yet supported (not supported
in GCC either).
Additionally, constructors/destructors are disallowed, but the former is
planned.
llvm-svn: 322028
2018-01-09 05:34:17 +08:00
|
|
|
// RUN: %clang_cc1 -triple x86_64-linux-gnu -fsyntax-only -verify %s
|
|
|
|
|
|
|
|
void __attribute__((target("sse4.2"))) no_default(void);
|
|
|
|
void __attribute__((target("arch=sandybridge"))) no_default(void);
|
|
|
|
|
|
|
|
void use1(void){
|
|
|
|
// expected-error@+1 {{no matching function for call to 'no_default'}}
|
|
|
|
no_default();
|
|
|
|
}
|
|
|
|
|
|
|
|
void __attribute__((target("sse4.2"))) has_def(void);
|
|
|
|
void __attribute__((target("default"))) has_def(void);
|
|
|
|
|
|
|
|
void use2(void){
|
|
|
|
// expected-error@+2 {{reference to overloaded function could not be resolved; did you mean to call it?}}
|
|
|
|
// expected-note@-4 {{possible target for call}}
|
|
|
|
+has_def;
|
|
|
|
}
|
|
|
|
|
|
|
|
int __attribute__((target("sse4.2"))) no_proto();
|
|
|
|
// expected-error@-1 {{multiversioned function must have a prototype}}
|
|
|
|
// expected-note@+1 {{function multiversioning caused by this declaration}}
|
|
|
|
int __attribute__((target("arch=sandybridge"))) no_proto();
|
|
|
|
|
|
|
|
// The following should all be legal, since they are just redeclarations.
|
|
|
|
int __attribute__((target("sse4.2"))) redecl1(void);
|
|
|
|
int __attribute__((target("sse4.2"))) redecl1(void) { return 1; }
|
|
|
|
int __attribute__((target("arch=sandybridge"))) redecl1(void) { return 2; }
|
|
|
|
|
|
|
|
int __attribute__((target("sse4.2"))) redecl2(void) { return 1; }
|
|
|
|
int __attribute__((target("sse4.2"))) redecl2(void);
|
|
|
|
int __attribute__((target("arch=sandybridge"))) redecl2(void) { return 2; }
|
|
|
|
|
|
|
|
int __attribute__((target("sse4.2"))) redecl3(void) { return 0; }
|
|
|
|
int __attribute__((target("arch=ivybridge"))) redecl3(void) { return 1; }
|
|
|
|
int __attribute__((target("arch=sandybridge"))) redecl3(void);
|
|
|
|
int __attribute__((target("arch=sandybridge"))) redecl3(void) { return 2; }
|
|
|
|
|
|
|
|
int __attribute__((target("sse4.2"))) redecl4(void) { return 1; }
|
|
|
|
int __attribute__((target("arch=sandybridge"))) redecl4(void) { return 2; }
|
|
|
|
int __attribute__((target("arch=sandybridge"))) redecl4(void);
|
|
|
|
|
|
|
|
int __attribute__((target("sse4.2"))) redef(void) { return 1; }
|
|
|
|
int __attribute__((target("arch=ivybridge"))) redef(void) { return 1; }
|
|
|
|
int __attribute__((target("arch=sandybridge"))) redef(void) { return 2; }
|
|
|
|
// expected-error@+2 {{redefinition of 'redef'}}
|
|
|
|
// expected-note@-2 {{previous definition is here}}
|
|
|
|
int __attribute__((target("arch=sandybridge"))) redef(void) { return 2; }
|
|
|
|
|
|
|
|
int __attribute__((target("default"))) redef2(void) { return 1;}
|
|
|
|
// expected-error@+2 {{redefinition of 'redef2'}}
|
|
|
|
// expected-note@-2 {{previous definition is here}}
|
|
|
|
int __attribute__((target("default"))) redef2(void) { return 1;}
|
|
|
|
|
|
|
|
int __attribute__((target("sse4.2"))) mv_after_use(void) { return 1; }
|
|
|
|
int use3(void) {
|
|
|
|
return mv_after_use();
|
|
|
|
}
|
|
|
|
|
|
|
|
// expected-error@+1 {{function declaration cannot become a multiversioned function after first usage}}
|
|
|
|
int __attribute__((target("arch=sandybridge"))) mv_after_use(void) { return 2; }
|
|
|
|
|
|
|
|
int __attribute__((target("sse4.2,arch=sandybridge"))) mangle(void) { return 1; }
|
|
|
|
//expected-error@+2 {{multiversioned function redeclarations require identical target attributes}}
|
|
|
|
//expected-note@-2 {{previous declaration is here}}
|
|
|
|
int __attribute__((target("arch=sandybridge,sse4.2"))) mangle(void) { return 2; }
|
|
|
|
|
2018-11-29 04:58:43 +08:00
|
|
|
// allow this, since we want to treat the 1st one as fwd-decl of the sandybridge version.
|
Implement Attribute Target MultiVersioning
GCC's attribute 'target', in addition to being an optimization hint,
also allows function multiversioning. We currently have the former
implemented, this is the latter's implementation.
This works by enabling functions with the same name/signature to coexist,
so that they can all be emitted. Multiversion state is stored in the
FunctionDecl itself, and SemaDecl manages the definitions.
Note that it ends up having to permit redefinition of functions so
that they can all be emitted. Additionally, all versions of the function
must be emitted, so this also manages that.
Note that this includes some additional rules that GCC does not, since
defining something as a MultiVersion function after a usage has been made illegal.
The only 'history rewriting' that happens is if a function is emitted before
it has been converted to a multiversion'ed function, at which point its name
needs to be changed.
Function templates and virtual functions are NOT yet supported (not supported
in GCC either).
Additionally, constructors/destructors are disallowed, but the former is
planned.
llvm-svn: 322028
2018-01-09 05:34:17 +08:00
|
|
|
int prev_no_target(void);
|
|
|
|
int __attribute__((target("arch=sandybridge"))) prev_no_target(void) { return 2; }
|
|
|
|
int __attribute__((target("arch=ivybridge"))) prev_no_target(void) { return 2; }
|
|
|
|
|
|
|
|
int __attribute__((target("arch=sandybridge"))) prev_no_target2(void);
|
|
|
|
int prev_no_target2(void);
|
|
|
|
// expected-error@-1 {{function declaration is missing 'target' attribute in a multiversioned function}}
|
|
|
|
// expected-note@+1 {{function multiversioning caused by this declaration}}
|
|
|
|
int __attribute__((target("arch=ivybridge"))) prev_no_target2(void);
|
|
|
|
|
|
|
|
void __attribute__((target("sse4.2"))) addtl_attrs(void);
|
2020-08-04 01:54:50 +08:00
|
|
|
//expected-error@+2 {{attribute 'target' multiversioning cannot be combined with attribute 'no_caller_saved_registers'}}
|
2020-03-10 01:15:45 +08:00
|
|
|
void __attribute__((no_caller_saved_registers,target("arch=sandybridge")))
|
|
|
|
addtl_attrs(void);
|
Implement Attribute Target MultiVersioning
GCC's attribute 'target', in addition to being an optimization hint,
also allows function multiversioning. We currently have the former
implemented, this is the latter's implementation.
This works by enabling functions with the same name/signature to coexist,
so that they can all be emitted. Multiversion state is stored in the
FunctionDecl itself, and SemaDecl manages the definitions.
Note that it ends up having to permit redefinition of functions so
that they can all be emitted. Additionally, all versions of the function
must be emitted, so this also manages that.
Note that this includes some additional rules that GCC does not, since
defining something as a MultiVersion function after a usage has been made illegal.
The only 'history rewriting' that happens is if a function is emitted before
it has been converted to a multiversion'ed function, at which point its name
needs to be changed.
Function templates and virtual functions are NOT yet supported (not supported
in GCC either).
Additionally, constructors/destructors are disallowed, but the former is
planned.
llvm-svn: 322028
2018-01-09 05:34:17 +08:00
|
|
|
|
2020-08-04 01:54:50 +08:00
|
|
|
//expected-error@+1 {{attribute 'target' multiversioning cannot be combined with attribute 'no_caller_saved_registers'}}
|
2020-03-10 01:15:45 +08:00
|
|
|
void __attribute__((target("default"), no_caller_saved_registers)) addtl_attrs2(void);
|
Implement Attribute Target MultiVersioning
GCC's attribute 'target', in addition to being an optimization hint,
also allows function multiversioning. We currently have the former
implemented, this is the latter's implementation.
This works by enabling functions with the same name/signature to coexist,
so that they can all be emitted. Multiversion state is stored in the
FunctionDecl itself, and SemaDecl manages the definitions.
Note that it ends up having to permit redefinition of functions so
that they can all be emitted. Additionally, all versions of the function
must be emitted, so this also manages that.
Note that this includes some additional rules that GCC does not, since
defining something as a MultiVersion function after a usage has been made illegal.
The only 'history rewriting' that happens is if a function is emitted before
it has been converted to a multiversion'ed function, at which point its name
needs to be changed.
Function templates and virtual functions are NOT yet supported (not supported
in GCC either).
Additionally, constructors/destructors are disallowed, but the former is
planned.
llvm-svn: 322028
2018-01-09 05:34:17 +08:00
|
|
|
|
2020-08-04 01:54:50 +08:00
|
|
|
//expected-error@+2 {{attribute 'target' multiversioning cannot be combined with attribute 'no_caller_saved_registers'}}
|
Implement Attribute Target MultiVersioning
GCC's attribute 'target', in addition to being an optimization hint,
also allows function multiversioning. We currently have the former
implemented, this is the latter's implementation.
This works by enabling functions with the same name/signature to coexist,
so that they can all be emitted. Multiversion state is stored in the
FunctionDecl itself, and SemaDecl manages the definitions.
Note that it ends up having to permit redefinition of functions so
that they can all be emitted. Additionally, all versions of the function
must be emitted, so this also manages that.
Note that this includes some additional rules that GCC does not, since
defining something as a MultiVersion function after a usage has been made illegal.
The only 'history rewriting' that happens is if a function is emitted before
it has been converted to a multiversion'ed function, at which point its name
needs to be changed.
Function templates and virtual functions are NOT yet supported (not supported
in GCC either).
Additionally, constructors/destructors are disallowed, but the former is
planned.
llvm-svn: 322028
2018-01-09 05:34:17 +08:00
|
|
|
//expected-note@+2 {{function multiversioning caused by this declaration}}
|
2020-03-10 01:15:45 +08:00
|
|
|
void __attribute__((no_caller_saved_registers,target("sse4.2"))) addtl_attrs3(void);
|
Implement Attribute Target MultiVersioning
GCC's attribute 'target', in addition to being an optimization hint,
also allows function multiversioning. We currently have the former
implemented, this is the latter's implementation.
This works by enabling functions with the same name/signature to coexist,
so that they can all be emitted. Multiversion state is stored in the
FunctionDecl itself, and SemaDecl manages the definitions.
Note that it ends up having to permit redefinition of functions so
that they can all be emitted. Additionally, all versions of the function
must be emitted, so this also manages that.
Note that this includes some additional rules that GCC does not, since
defining something as a MultiVersion function after a usage has been made illegal.
The only 'history rewriting' that happens is if a function is emitted before
it has been converted to a multiversion'ed function, at which point its name
needs to be changed.
Function templates and virtual functions are NOT yet supported (not supported
in GCC either).
Additionally, constructors/destructors are disallowed, but the former is
planned.
llvm-svn: 322028
2018-01-09 05:34:17 +08:00
|
|
|
void __attribute__((target("arch=sandybridge"))) addtl_attrs3(void);
|
|
|
|
|
|
|
|
void __attribute__((target("sse4.2"))) addtl_attrs4(void);
|
|
|
|
void __attribute__((target("arch=sandybridge"))) addtl_attrs4(void);
|
|
|
|
//expected-error@+1 {{attribute 'target' multiversioning cannot be combined}}
|
2020-03-10 01:15:45 +08:00
|
|
|
void __attribute__((no_caller_saved_registers,target("arch=ivybridge"))) addtl_attrs4(void);
|
Implement Attribute Target MultiVersioning
GCC's attribute 'target', in addition to being an optimization hint,
also allows function multiversioning. We currently have the former
implemented, this is the latter's implementation.
This works by enabling functions with the same name/signature to coexist,
so that they can all be emitted. Multiversion state is stored in the
FunctionDecl itself, and SemaDecl manages the definitions.
Note that it ends up having to permit redefinition of functions so
that they can all be emitted. Additionally, all versions of the function
must be emitted, so this also manages that.
Note that this includes some additional rules that GCC does not, since
defining something as a MultiVersion function after a usage has been made illegal.
The only 'history rewriting' that happens is if a function is emitted before
it has been converted to a multiversion'ed function, at which point its name
needs to be changed.
Function templates and virtual functions are NOT yet supported (not supported
in GCC either).
Additionally, constructors/destructors are disallowed, but the former is
planned.
llvm-svn: 322028
2018-01-09 05:34:17 +08:00
|
|
|
|
|
|
|
int __attribute__((target("sse4.2"))) diff_cc(void);
|
2018-06-26 04:06:13 +08:00
|
|
|
// expected-error@+1 {{multiversioned function declaration has a different calling convention}}
|
Implement Attribute Target MultiVersioning
GCC's attribute 'target', in addition to being an optimization hint,
also allows function multiversioning. We currently have the former
implemented, this is the latter's implementation.
This works by enabling functions with the same name/signature to coexist,
so that they can all be emitted. Multiversion state is stored in the
FunctionDecl itself, and SemaDecl manages the definitions.
Note that it ends up having to permit redefinition of functions so
that they can all be emitted. Additionally, all versions of the function
must be emitted, so this also manages that.
Note that this includes some additional rules that GCC does not, since
defining something as a MultiVersion function after a usage has been made illegal.
The only 'history rewriting' that happens is if a function is emitted before
it has been converted to a multiversion'ed function, at which point its name
needs to be changed.
Function templates and virtual functions are NOT yet supported (not supported
in GCC either).
Additionally, constructors/destructors are disallowed, but the former is
planned.
llvm-svn: 322028
2018-01-09 05:34:17 +08:00
|
|
|
__vectorcall int __attribute__((target("arch=sandybridge"))) diff_cc(void);
|
|
|
|
|
|
|
|
int __attribute__((target("sse4.2"))) diff_ret(void);
|
|
|
|
// expected-error@+1 {{multiversioned function declaration has a different return type}}
|
|
|
|
short __attribute__((target("arch=sandybridge"))) diff_ret(void);
|
2020-08-04 21:28:29 +08:00
|
|
|
|
|
|
|
void __attribute__((target("sse4.2"), nothrow, used, nonnull(1))) addtl_attrs5(int*);
|
|
|
|
void __attribute__((target("arch=sandybridge"))) addtl_attrs5(int*);
|
|
|
|
|
|
|
|
void __attribute__((target("sse4.2"))) addtl_attrs6(int*);
|
|
|
|
void __attribute__((target("arch=sandybridge"), nothrow, used, nonnull)) addtl_attrs6(int*);
|
|
|
|
|