Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com,
	thorpej@wasabisystems.com
Subject: Re: userdef.exp regression for ppc?
Date: Mon, 03 Jun 2002 11:30:00 -0000	[thread overview]
Message-ID: <3CFBB24A.30F5AE81@redhat.com> (raw)
In-Reply-To: <200206011546.g51FkMj30586@duracef.shout.net>

Michael Elizabeth Chastain wrote:
> 
> This looks like a bug in calling functions that return a structure
> by value.  All the functions that return structures FAIL:

That could be checked by looking at the results of structs.exp, 
callfuncs.exp, and to some extent call-ar-st and call-rt-st.

> 
>   print one + two
>   $1 = {x = 2147479536, y = 1099239424}
>   (gdb) FAIL: gdb.c++/userdef.exp: print one + two
> 
> The functions that return a scalar PASS:
> 
>   print one && two
>   $6 = 1
>   (gdb) PASS: gdb.c++/userdef.exp: print one && two
> 
> Look at the results in gdb.base/call-rt-st.exp and gdb.base/structs.exp.
> I bet there is a lot of juicy log info there.
> 
> Michael C


  parent reply	other threads:[~2002-06-03 18:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01  8:46 Michael Elizabeth Chastain
2002-06-01 10:21 ` [rfa:ppc] Fix PPC/NBSD struct return; Was: " Andrew Cagney
2002-06-01 15:03   ` Jason R Thorpe
2002-06-02 11:15   ` Jason R Thorpe
2002-06-02 11:51   ` Jason R Thorpe
2002-06-02 12:24     ` Zack Weinberg
2002-06-02 13:29   ` Jason R Thorpe
2002-06-03  6:13     ` Andrew Cagney
2002-06-03 11:30 ` Michael Snyder [this message]
     [not found] <200206010517.g515Ho227072@duracef.shout.net>
2002-06-01  7:03 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2002-05-31 22:17 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=3CFBB24A.30F5AE81@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    --cc=thorpej@wasabisystems.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