https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765
--- Comment #6 from nightstrike ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2025-April/680856.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765
Peter Damianov changed:
What|Removed |Added
CC||peter0x44 at disroot dot org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765
--- Comment #4 from nightstrike ---
Ah, I think I understand better. It's not the AMD64 ABI saying to pass the
register count in EAX, it's the SysV or whatever ABI saying to do it, and the
Windows ABI says to do something else. So really instead
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765
--- Comment #3 from nightstrike ---
Is this a case of "skip windows", or a case of "skip targets with/without
feature X"?
Also, I'm a little surprised, as based on the name of the test, I would think
it was testing a feature of the cpu type, no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765
--- Comment #2 from Andrew Pinski ---
Yes the testcase should be skipped for the windows x86_64 which never sets eax
for varargs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119765
--- Comment #1 from Andrew Pinski ---
I suspect it is disable the test for windows abi. It is testing varargs setting
of eax for the number of use registers passed.
