public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Re: Do we need Linux/alpha and Linux/sparc versions of <bits/siginfo.h>?
Date: Mon, 24 Jan 2000 00:08:00 -0000	[thread overview]
Message-ID: <20000124091256.X2708@mff.cuni.cz> (raw)
In-Reply-To: <u8hfg3rjih.fsf@gromit.rhein-neckar.de>

> Jakub, what do you think?  Are now (with your patch and Linux
> 2.3.41pre2) all siginfo problems fixed?  Is 32bit uid support complete
> (apart from some cleaning up)?

If Linus eats my siginfo kernel patch (it clashes with your NSIGCHLD,
hopefully Linus will want to resolve that failed hunk), then hopefully
all should be ready, apart from a few missing kernel siginfo generation points.
Now the whole thing has to be heavily tested with 2.3 and 2.2 kernels.

> 
>  > IMHO, we need only separate version of sparc siginfo, plus use __WORDSIZE
>  > in the generic linux version (I think ia64, ppc64, mips64 etc. could use it
>  > as well):
> MIPS has already a special version since some constants have different
> values than the rest of the kernel :-(
>  > [...]
> New Sparc specific <bits/siginfo.h>:
>  > +
>  > +	/* SIGILL, SIGFPE, SIGSEGV, SIGBUS.  */
> You didn't add SIGEMT in the comment - is this correct?

Oopsie, you're right, should be there as well.
On the other side, the comments are pretty misleading in SIGCHLD and SIGPOLL
cases. Those structure layouts are for child deatch signal (which can be any
signal) and you can pass si_band/si_fd with signals other than SIGPOLL as
well.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jakub@redhat.com | http://sunsite.mff.cuni.cz/~jj
Linux version 2.3.40 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________

      reply	other threads:[~2000-01-24  0:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-23 23:15 Andreas Jaeger
2000-01-23 23:45 ` Jakub Jelinek
2000-01-23 23:56   ` Andreas Jaeger
2000-01-24  0:08     ` Jakub Jelinek [this message]

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=20000124091256.X2708@mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=aj@suse.de \
    --cc=libc-hacker@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).