Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Joseph S. Myers <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA Darwin]: Add push_dummy_call for i386
Date: Mon, 06 Jul 2009 07:00:00 -0000	[thread overview]
Message-ID: <66568D6F-02DA-426F-8FA5-538F20931289@adacore.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0907031653300.823@digraph.polyomino.org.uk>


On Jul 3, 2009, at 6:55 PM, Joseph S. Myers wrote:

> On Fri, 3 Jul 2009, Tristan Gingold wrote:
>
>> Hi,
>>
>> Darwin i386 ABI is slightly different from the SVR4 one.  In  
>> particular
>> stack alignment is 16.  As a consquence, i386 Darwin can't use the  
>> standard
>> i386-tdeo.c push_dummy_call and this patch provides a Darwin  
>> version of this
>> call.
>
> Are there tests in the testsuite (of GDB knowing how SSE vector  
> arguments
> and function returns are handled) that this fixes?  (There are such  
> tests
> for AltiVec and e500 vectors, for example.)

This example fixes many tests in callfuncs.exp.  If gdb calls malloc()  
(eg to allocate a string) with
a wrong stack alignment, the inferior will crash (as it looks like  
malloc or one of its callees uses sse).

That's said, I haven't seen tests for SSE vector arguments/return.

Tristan.


  reply	other threads:[~2009-07-06  7:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03 15:52 Tristan Gingold
2009-07-03 16:49 ` Mark Kettenis
2009-07-06  7:08   ` Tristan Gingold
2009-07-06 10:16     ` Mark Kettenis
2009-07-07  8:15       ` Tristan Gingold
2009-07-03 16:55 ` Joseph S. Myers
2009-07-06  7:00   ` Tristan Gingold [this message]
2009-07-04 15:31 ` H.J. Lu
2009-07-06  6:56   ` Tristan Gingold

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=66568D6F-02DA-426F-8FA5-538F20931289@adacore.com \
    --to=gingold@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.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