Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/ppc] Use frame_align(); delete hack
Date: Tue, 24 Sep 2002 18:27:00 -0000	[thread overview]
Message-ID: <3D9110EA.5060102@redhat.com> (raw)
In-Reply-To: <1020924233033.ZM9198@localhost.localdomain>

> On Sep 24,  7:07pm, Andrew Cagney wrote:
> 
> 
>> In the process it delets that global variable 
>> struct return hack.  Struct returns involving dummy functions are 
>> instead handled by the dummy frame code.
> 
> 
> Where/how does this happen?

In hand_function_call(), near the end:

>     /* NOTE: cagney/2002-09-10: Only when the stack has been correctly
>        aligned (using frame_align()) do we can trust STRUCT_ADDR and
>        fetch the return value direct from the stack.  This lack of
>        trust comes about because legacy targets have a nasty habit of
>        silently, and local to PUSH_ARGUMENTS(), moving STRUCT_ADDR.
>        For such targets, just hope that value_being_returned() can
>        find the adjusted value.  */
>     if (struct_return && gdbarch_frame_align_p (current_gdbarch))
>       {
>         struct value *retval = value_at (value_type, struct_addr, NULL);
>         do_cleanups (retbuf_cleanup);
>         return retval;
>       }
>     else
>       {
> 	struct value *retval = value_being_returned (value_type, retbuf,
> 						     struct_return);
> 	do_cleanups (retbuf_cleanup);
> 	return retval;
>       }
>   }

Andrew




  reply	other threads:[~2002-09-25  1:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D90F04C.9040900@redhat.com>
2002-09-24 16:30 ` Kevin Buettner
2002-09-24 18:27   ` Andrew Cagney [this message]
2002-09-26 11:37 ` Kevin Buettner
2002-09-26 15:31   ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D9110EA.5060102@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox