public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Maciej W. Rozycki <macro@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb: mips: Fix the handling of complex type of function return value
Date: Wed,  6 Apr 2022 22:46:00 +0000 (GMT)	[thread overview]
Message-ID: <20220406224600.5C3023858C50@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=089169c0037bc2ae153580de56df6acceab738fc

commit 089169c0037bc2ae153580de56df6acceab738fc
Author: Youling Tang <tangyouling@loongson.cn>
Date:   Wed Apr 6 23:38:21 2022 +0100

    gdb: mips: Fix the handling of complex type of function return value
    
    $ objdump -d outputs/gdb.base/varargs/varargs
    00000001200012e8 <find_max_float_real>:
    ...
       1200013b8:   c7c10000        lwc1    $f1,0(s8)
       1200013bc:   c7c00004        lwc1    $f0,4(s8)
       1200013c0:   46000886        mov.s   $f2,$f1
       1200013c4:   46000046        mov.s   $f1,$f0
       1200013c8:   46001006        mov.s   $f0,$f2
       1200013cc:   46000886        mov.s   $f2,$f1
       1200013d0:   03c0e825        move    sp,s8
       1200013d4:   dfbe0038        ld      s8,56(sp)
       1200013d8:   67bd0080        daddiu  sp,sp,128
       1200013dc:   03e00008        jr      ra
       1200013e0:   00000000        nop
    
    From the above disassembly, we can see that when the return value of the
    function is a complex type and len <= 2 * MIPS64_REGSIZE, the return value
    will be passed through $f0 and $f2, so fix the corresponding processing
    in mips_n32n64_return_value().
    
    $ make check RUNTESTFLAGS='GDB=../gdb gdb.base/varargs.exp --outdir=test'
    
    Before applying the patch:
     FAIL: gdb.base/varargs.exp: print find_max_float_real(4, fc1, fc2, fc3, fc4)
     FAIL: gdb.base/varargs.exp: print find_max_double_real(4, dc1, dc2, dc3, dc4)
    
     # of expected passes            9
     # of unexpected failures        2
    
    After applying the patch:
     # of expected passes            11
    
    This also fixes:
     FAIL: gdb.base/callfuncs.exp: call inferior func with struct - returns float _Complex
    
    Signed-off-by: Youling Tang <tangyouling@loongson.cn>
    Co-Authored-By: Maciej W. Rozycki <macro@orcam.me.uk>

Diff:
---
 gdb/mips-tdep.c | 34 ++++++++++++++++++++++++----------
 1 file changed, 24 insertions(+), 10 deletions(-)

diff --git a/gdb/mips-tdep.c b/gdb/mips-tdep.c
index 93945891407..4bdbf0fcdb7 100644
--- a/gdb/mips-tdep.c
+++ b/gdb/mips-tdep.c
@@ -5217,30 +5217,44 @@ mips_n32n64_return_value (struct gdbarch *gdbarch, struct value *function,
      that all composite results be handled by conversion to implicit first
      parameters.  The MIPS/SGI Fortran implementation has always made a
      specific exception to return COMPLEX results in the floating point
-     registers.]  */
+     registers.]
+
+     From MIPSpro Assembly Language Programmer's Guide, Document Number:
+     007-2418-004
+
+              Software
+     Register Name(from
+     Name     fgregdef.h) Use and Linkage
+     -----------------------------------------------------------------
+     $f0, $f2 fv0, fv1    Hold results of floating-point type function
+                          ($f0) and complex type function ($f0 has the
+                          real part, $f2 has the imaginary part.)  */
 
   if (TYPE_LENGTH (type) > 2 * MIPS64_REGSIZE)
     return RETURN_VALUE_STRUCT_CONVENTION;
-  else if (type->code () == TYPE_CODE_FLT
-	   && TYPE_LENGTH (type) == 16
+  else if ((type->code () == TYPE_CODE_COMPLEX
+	    || (type->code () == TYPE_CODE_FLT && TYPE_LENGTH (type) == 16))
 	   && tdep->mips_fpu_type != MIPS_FPU_NONE)
     {
-      /* A 128-bit floating-point value fills both $f0 and $f2.  The
-	 two registers are used in the same as memory order, so the
-	 eight bytes with the lower memory address are in $f0.  */
+      /* A complex value of up to 128 bits in width as well as a 128-bit
+	 floating-point value goes in both $f0 and $f2.  A single complex
+	 value is held in the lower halves only of the respective registers.
+	 The two registers are used in the same as memory order, so the
+	 bytes with the lower memory address are in $f0.  */
       if (mips_debug)
 	gdb_printf (gdb_stderr, "Return float in $f0 and $f2\n");
       mips_xfer_register (gdbarch, regcache,
 			  (gdbarch_num_regs (gdbarch)
 			   + mips_regnum (gdbarch)->fp0),
-			  8, gdbarch_byte_order (gdbarch),
+			  TYPE_LENGTH (type) / 2, gdbarch_byte_order (gdbarch),
 			  readbuf, writebuf, 0);
       mips_xfer_register (gdbarch, regcache,
 			  (gdbarch_num_regs (gdbarch)
 			   + mips_regnum (gdbarch)->fp0 + 2),
-			  8, gdbarch_byte_order (gdbarch),
-			  readbuf ? readbuf + 8 : readbuf,
-			  writebuf ? writebuf + 8 : writebuf, 0);
+			  TYPE_LENGTH (type) / 2, gdbarch_byte_order (gdbarch),
+			  readbuf ? readbuf + TYPE_LENGTH (type) / 2 : readbuf,
+			  (writebuf
+			   ? writebuf + TYPE_LENGTH (type) / 2 : writebuf), 0);
       return RETURN_VALUE_REGISTER_CONVENTION;
     }
   else if (type->code () == TYPE_CODE_FLT


                 reply	other threads:[~2022-04-06 22:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220406224600.5C3023858C50@sourceware.org \
    --to=macro@sourceware.org \
    --cc=gdb-cvs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).