Varargs not supported on Linux/x64

[kunalspathak]

There are lot of tests that are disabled stating that Unix/x64 do not support varargs. This is a tracking issue so we can have conversation here on why it is not supported and what is needed to support it.

runtime/src/tests/issues.targets

Lines 633 to 663 in aa4290f

	<ItemGroup Condition="'$(XunitTestBinBase)' != '' and '$(TargetArchitecture)' == 'x64' and '$(TargetsWindows)' != 'true' and '$(RuntimeFlavor)' == 'coreclr'">
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Methodical/refany/_il_dbgseq/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Methodical/refany/_il_relseq/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Methodical/refany/_relstress1/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Methodical/refany/_relstress3/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Methodical/refany/_speed_dbgstress1/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Methodical/refany/_speed_dbgstress3/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Methodical/refany/_speed_relstress1/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Methodical/refany/_speed_relstress3/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b41391/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>
	<ExcludeList Include="$(XunitTestBinBase)/JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b37646/*">
	<Issue>Varargs not supported on this platform</Issue>
	</ExcludeList>

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[jkotas]

Duplicate of #10478 ?

[kunalspathak]

Thanks @jkotas for pointing out. I will close this one.