radv/ac: drop setting xnack

Since radv uses compute rings and we can't know when we are setting
up the shaders what ring they are to be used on, we should just use
the default xnack setting. This may be suboptimal in some places,
but if we hit a problem, we likely should try and address this
between llvm and mesa.

Reviewed-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Signed-off-by: Dave Airlie <airlied@redhat.com>

diff --git a/src/amd/common/ac_llvm_util.c b/src/amd/common/ac_llvm_util.c
index d14057fa7680441e68a8f03f1d49db8a6c9fd83f..ea752e031ef11f98400cfbcc9f26996574956097 100644 (file)
--- a/src/amd/common/ac_llvm_util.c
+++ b/src/amd/common/ac_llvm_util.c
@@ -126,8 +126,7 @@ LLVMTargetMachineRef ac_create_target_machine(enum radeon_family family, enum ac
        LLVMTargetRef target = ac_get_llvm_target(triple);
 
        snprintf(features, sizeof(features),
-                "+DumpCode,+vgpr-spilling,-fp32-denormals%s%s",
-                family >= CHIP_VEGA10 ? ",+xnack" : ",-xnack",
+                "+DumpCode,+vgpr-spilling,-fp32-denormals%s",
                 tm_options & AC_TM_SISCHED ? ",+si-scheduler" : "");
        
        LLVMTargetMachineRef tm = LLVMCreateTargetMachine(