https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116395
Andrew Pinski changed:
What|Removed |Added
Resolution|FIXED |INVALID
--- Comment #6 from Andrew Pins
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116395
Stas Sergeev changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #5 from Stas Sergeev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116395
--- Comment #4 from Andrew Pinski ---
(In reply to Stas Sergeev from comment #3)
> (In reply to Andrew Pinski from comment #1)
> > va_list can't be used that way.
> > in x86 (32bit) va_list is a pointer while in x86_64, it is an array.
>
> http
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116395
--- Comment #3 from Stas Sergeev ---
(In reply to Andrew Pinski from comment #1)
> va_list can't be used that way.
> in x86 (32bit) va_list is a pointer while in x86_64, it is an array.
https://stackoverflow.com/questions/77647307/expression-in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116395
--- Comment #2 from Andrew Pinski ---
va_list can only be assigned to via another va_list, initialized using va_start
or va_copy.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116395
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
