From: Andreas Jaeger <aj@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
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: Sun, 23 Jan 2000 23:56:00 -0000 [thread overview]
Message-ID: <u8hfg3rjih.fsf@gromit.rhein-neckar.de> (raw)
In-Reply-To: <20000124084940.W2708@mff.cuni.cz>
>>>>> Jakub Jelinek writes:
> On Mon, Jan 24, 2000 at 08:14:29AM +0100, Andreas Jaeger wrote:
>>
>> Looking through the various asm-*/siginfo.h files in Linux 2.3.41pre2,
>> I've encountered only two platforms with problems: Alpha and Sparc.
>> Could the maintainers of these platforms please check the following
>> and take appropriate action?
>>
>> Alpha defines:
>> #define SI_PAD_SIZE ((SI_MAX_SIZE/sizeof(int)) - 4)
>> #define SIGEV_PAD_SIZE ((SIGEV_MAX_SIZE/sizeof(int)) - 4)
>>
>> but all other platforms have a 3 instead of a 4 for these two defines:
>> #define SI_PAD_SIZE ((SI_MAX_SIZE/sizeof(int)) - 3)
>> #define SIGEV_PAD_SIZE ((SIGEV_MAX_SIZE/sizeof(int)) - 3)
>>
>> Sparc and Sparc64 additionally define the member _trapno for _sigfault
>> - and SIGEMT is also only used by Sparc*:
>> /* SIGILL, SIGFPE, SIGSEGV, SIGBUS, SIGEMT */
>> struct {
>> void *_addr; /* faulting insn/memory ref. */
>> int _trapno; /* TRAP # which caused the signal */
>> } _sigfault;
>>
>>
>> Do we need Linux/alpha and Linux/sparc versions of <bits/siginfo.h>?
> (Again, something which I had scheduled for today anyway).
Good that I didn't investigate more work into it;-).
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)?
> 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?
> + struct
> + {
> + void *si_addr; /* Faulting insn/memory ref. */
> + int si_trapno;
> + } _sigfault;
The rest looks fine.
Thanks,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de
next prev parent reply other threads:[~2000-01-23 23:56 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 [this message]
2000-01-24 0:08 ` Jakub Jelinek
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=u8hfg3rjih.fsf@gromit.rhein-neckar.de \
--to=aj@suse.de \
--cc=jakub@redhat.com \
--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).