Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: hjl.tools@gmail.com
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: Support x32 siginfo_t conversion
Date: Sat, 12 May 2012 21:16:00 -0000	[thread overview]
Message-ID: <201205122116.q4CLG6lN019181@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <CAMe9rOoEX+eYQmKPz-ev4DBKPY40niysoMAUZ+404OFpOaDmTA@mail.gmail.com>	(hjl.tools@gmail.com)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4432 bytes --]

> Date: Fri, 11 May 2012 13:55:29 -0700
> From: "H.J. Lu" <hjl.tools@gmail.com>
> 
> On Fri, May 11, 2012 at 1:11 PM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> >> Date: Fri, 11 May 2012 12:21:33 -0700
> >> From: "H.J. Lu" <hongjiu.lu@intel.com>
> >>
> >> Hi,
> >>
> >> This patch implements x32 siginfo_t conversion.  Tested on Linux/x86-64.
> >> OK to install?
> >>
> >> Thanks.
> >>
> >>
> >> H.J.
> >> --
> >>       * amd64-linux-nat.c (compat_x32_clock_t): New.
> >>       (compat_x32_siginfo_t): Likewise.
> >>       (compat_x32_siginfo_from_siginfo): Likewise.
> >>       (siginfo_from_compat_x32_siginfo): Likewise.
> >>       (amd64_linux_siginfo_fixup): Call compat_x32_siginfo_from_siginfo
> >>       and siginfo_from_compat_x32_siginfo for x32.
> >>
> >> diff --git a/gdb/amd64-linux-nat.c b/gdb/amd64-linux-nat.c
> >> index 3be8404..97c9a49 100644
> >> --- a/gdb/amd64-linux-nat.c
> >> +++ b/gdb/amd64-linux-nat.c
> >> @@ -591,6 +591,67 @@ typedef struct compat_siginfo
> >>    } _sifields;
> >>  } compat_siginfo_t;
> >>
> >> +/* For x32, clock_t in _sigchld is 64bit aligned at 4 bytes.  */
> >> +typedef long __attribute__ ((__aligned__ (4))) compat_x32_clock_t;
> >
> > Sorry, but that isn't acceptable.
> >
> > Is your X32 ABI really that broken?
> >
> >> +typedef struct compat_x32_siginfo
> >> +{
> >> +  int si_signo;
> >> +  int si_errno;
> >> +  int si_code;
> >> +
> >> +  union
> >> +  {
> >> +    int _pad[((128 / sizeof (int)) - 3)];
> >> +
> >> +    /* kill() */
> >> +    struct
> >> +    {
> >> +      unsigned int _pid;
> >> +      unsigned int _uid;
> >> +    } _kill;
> >> +
> >> +    /* POSIX.1b timers */
> >> +    struct
> >> +    {
> >> +      compat_timer_t _tid;
> >> +      int _overrun;
> >> +      compat_sigval_t _sigval;
> >> +    } _timer;
> >> +
> >> +    /* POSIX.1b signals */
> >> +    struct
> >> +    {
> >> +      unsigned int _pid;
> >> +      unsigned int _uid;
> >> +      compat_sigval_t _sigval;
> >> +    } _rt;
> >> +
> >> +    /* SIGCHLD */
> >> +    struct
> >> +    {
> >> +      unsigned int _pid;
> >> +      unsigned int _uid;
> >> +      int _status;
> >> +      compat_x32_clock_t _utime;
> >> +      compat_x32_clock_t _stime;
> >> +    } _sigchld;
> >> +
> >> +    /* SIGILL, SIGFPE, SIGSEGV, SIGBUS */
> >> +    struct
> >> +    {
> >> +      unsigned int _addr;
> >> +    } _sigfault;
> >> +
> >> +    /* SIGPOLL */
> >> +    struct
> >> +    {
> >> +      int _band;
> >> +      int _fd;
> >> +    } _sigpoll;
> >> +  } _sifields;
> >> +} compat_x32_siginfo_t __attribute__ ((__aligned__ (8)));
> >
> > Same here.  I don't think you need alignment here, even with the broken ABI.
> >
> > If it really is too late to fix the X32 ABI, you'll have to write this
> > portably by splitting _utime and _stime into two 32-bit variables and
> > write code that correctly sets the upper and lower 32-bits.
> >
> >
> 
> X32 ABI choice is done on purpose.  X32 siginfo_t has
> 
> typedef long __attribute__ ((__aligned__ (4))) compat_x32_clock_t;
> 
> typedef struct compat_x32_siginfo
> {
>   int si_signo;
>   int si_errno;
>   int si_code;
> 
>   union
>   {
> ...
>     /* SIGCHLD */
>     struct
>     {
>       unsigned int _pid;
>       unsigned int _uid;
>       int _status;
>       compat_x32_clock_t _utime;
>       compat_x32_clock_t _stime;
>     } _sigchld;
> ...
> } compat_x32_siginfo_t __attribute__ ((__aligned__ (8)));
> 
> struct info is aligned at 8 bytes and type of _utime/_stime is aligned
> at 4 bytes.  However,  _utime offset is 3 * 4 + 3 * 4 == 24 bytes. So
> in reality, the addresses of _utime/_stime are 8 bytes aligned.  There
> are no needs to split _utime and _stime into two 32-bit variables
> since their addresses are 64bits aligned.

But there is no way you can easily express that syntax with standard C
syntax[1].  That's why you had to resort to using GCC's __attribute__
syntax.  For GDB you'll have to figure out a way to do this without
using __attribute__ ((__aligned__ (...))).

My recommendation would be to define a compat_x32 structure just for
SIGCHLD (without using a union) and use the normal 32-bit comap
structure for all the other conversions.

Cheers,

Mark


[1] Well there is in C11, but you can't rely on that being properly
    implemented for at least another 5 years or so.


  reply	other threads:[~2012-05-12 21:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 19:21 H.J. Lu
2012-05-11 20:11 ` Mark Kettenis
2012-05-11 20:55   ` H.J. Lu
2012-05-12 21:16     ` Mark Kettenis [this message]
2012-05-12 23:16       ` H.J. Lu
2012-05-13  2:25         ` H.J. Lu

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=201205122116.q4CLG6lN019181@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.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