Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: bauerman@br.ibm.com, luisgpm@linux.vnet.ibm.com, drow@false.org,
		gdb-patches@sourceware.org
Subject: Re: [RFC] Linux-specific ppc32 ABI
Date: Fri, 01 Feb 2008 22:39:00 -0000	[thread overview]
Message-ID: <20080201223839.GA27578@adacore.com> (raw)
In-Reply-To: <200801261535.m0QFZddH026156@brahms.sibelius.xs4all.nl>

Hi Mark,

> How about the attached diff?

Sounds like everyone is happy with the patch you suggested. Thiago
just mentioned one nit in your comments (repeated below). Can the patch
be checked in?  We'd like to have it for the release.

Thank you.

> Index: ppc-sysv-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/ppc-sysv-tdep.c,v
> retrieving revision 1.45
> diff -u -p -r1.45 ppc-sysv-tdep.c
> --- ppc-sysv-tdep.c	1 Jan 2008 22:53:12 -0000	1.45
> +++ ppc-sysv-tdep.c	26 Jan 2008 15:24:36 -0000
> @@ -129,17 +129,19 @@ ppc_sysv_abi_push_dummy_call (struct gdb
>  		}
>  	      else
>  		{
> -		  /* SysV ABI converts floats to doubles before
> -		     writing them to an 8 byte aligned stack location.  */
> -		  argoffset = align_up (argoffset, 8);
> +		  /* The SysV ABI tells us to convert floats to
> +		     doubles before writing them to an 8 byte aligned
> +		     stack location.  Unfortunately GCC does not do
> +		     that, and stores floats without into 4 bytes
                                             ^^^^^^^ should be removed
> +		     aligned locations without converting them to
> +		     doubles. */
> +
> +		  /* Align to 4 bytes or 8 bytes depending on the type of
> +		     the argument (float or double).  */
> +		  argoffset = align_up (argoffset, len);
>  		  if (write_pass)
> -		    {
> -		      char memval[8];
> -		      convert_typed_floating (val, type, memval,
> -					      builtin_type_ieee_double);
>  		      write_memory (sp + argoffset, val, len);
> -		    }
> -		  argoffset += 8;
> +		  argoffset += len;
>  		}
>  	    }
>  	  else if (TYPE_CODE (type) == TYPE_CODE_FLT

-- 
Joel


  parent reply	other threads:[~2008-02-01 22:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 19:00 Luis Machado
2008-01-10 19:13 ` Daniel Jacobowitz
2008-01-10 19:26   ` Thiago Jung Bauermann
2008-01-11  6:06 ` Joel Brobecker
2008-01-11 15:55   ` Luis Machado
2008-01-11 15:58     ` Daniel Jacobowitz
2008-01-11 21:26       ` Luis Machado
2008-01-25 16:13         ` Thiago Jung Bauermann
2008-01-25 16:51           ` Thiago Jung Bauermann
2008-01-26 18:18           ` Mark Kettenis
2008-01-26 19:08             ` Joseph S. Myers
2008-01-26 19:10               ` Mark Kettenis
2008-01-28 20:32             ` Thiago Jung Bauermann
2008-02-01 21:42             ` Thiago Jung Bauermann
2008-02-01 22:39             ` Joel Brobecker [this message]
2008-02-02  0:27               ` Mark Kettenis
2008-02-06  3:57                 ` Thiago Jung Bauermann

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=20080201223839.GA27578@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bauerman@br.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    --cc=mark.kettenis@xs4all.nl \
    /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