https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90482
Ian Lance Taylor changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90482
--- Comment #5 from Eric Botcazou ---
> What is different about 32-bit SPARC is not that it treats pointers and
> integers differently, but that
>
> struct { void *p; }
>
> and
>
> void *p;
>
> are passed as arguments in two different ways.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90482
--- Comment #4 from Ian Lance Taylor ---
What is different about 32-bit SPARC is not that it treats pointers and
integers differently, but that
struct { void *p; }
and
void *p;
are passed as arguments in two different ways. The former is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90482
--- Comment #3 from Eric Botcazou ---
It's not obvious to me why this would have anything to do with the calling
convention on SPARC 32-bit, which is very reasonable. For example, it's not
like M68k where pointers and integers are passed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90482
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90482
--- Comment #1 from ian at gcc dot gnu.org ---
Author: ian
Date: Fri May 17 05:49:22 2019
New Revision: 271310
URL: https://gcc.gnu.org/viewcvs?rev=271310=gcc=rev
Log:
PR go/90482
compiler: make value method of direct interface type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90482
Rainer Orth changed:
What|Removed |Added
Target Milestone|--- |10.0
