This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: 970125-0.f
- To: Craig Burley <burley at gnu dot org>
- Subject: Re: 970125-0.f
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 02 Jun 1998 22:18:28 -0600
- cc: egcs-bugs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199806021439.KAA20678@melange.gnu.org>you write:
> >So what does it mean to have ADDR_EXPR (PLUS_EXPR ...))). Do you
> >put the result of the PLUS_EXPR into a stack slot, then take it's
> >address?
>
> I *think* that's what gcc has done for years.
I'll have to take your word for it. The tree structure and how it
works is an area I don't know as well as I'd like.
> >OK. So you want/need the pointer to foo shoved into a stack slot
> >and we pass the address of the stack slot? I can do that, though I
> >don't see how it's useful :-)
>
> Well, it's useful in that that's how it has worked for a very long
> time, and that's what various front ends expect.
I meant from a code generation standpoint. What do you expect to do with
a pointer to a stack slot that holds the address of the object?
Regardless, I've tweaked the compiler to shove the pointer into a
stack slot, then give you back the address of that stack slot. I don't
have any way to test whether or not the generated code is actually
correct though.
Jeff