From: "Martin Schwidefsky" <schwidefsky@de.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: linux-kernel@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: sizeof (siginfo_t) problem
Date: Tue, 15 Jul 2003 13:58:46 +0200 [thread overview]
Message-ID: <OF688246EA.0B58B996-ONC1256D64.00411F64-C1256D64.0041CE23@de.ibm.com> (raw)
> This means it does not work on any kernels so far, if we don't add a pad
> to the kernel and just fix __ARCH_SI_PREAMBLE_SIZE on s390x, then GCC
> will suddenly work with all newer kernels but will never work with older
> kernels.
This is a kernel bug and I'm inclined to say that this has to be fixed in
the kernel and only there. If it didn't work at all so far nobody will
complain that it suddenly works with the kernel fix. It is an ABI change
but for an ABI that didn't work so far. I don't see a problem with the
simple fix to use __ARCH_SI_PREAMBLE_SIZE (4 * sizeof(int)) for s390x.
blue skies,
Martin
next reply other threads:[~2003-07-15 11:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 11:58 Martin Schwidefsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-14 18:52 sizeof (siginfo_t) problem Ulrich Weigand
2003-07-14 18:31 Ulrich Weigand
2003-07-14 18:35 ` Jakub Jelinek
2003-07-14 12:40 Jakub Jelinek
2003-07-14 13:55 ` Jamie Lokier
2003-07-14 15:02 ` Andreas Schwab
2003-07-14 15:48 ` David Mosberger
2003-07-14 15:57 ` Jakub Jelinek
2003-07-14 16:52 ` Stephen Rothwell
2003-07-14 17:00 ` Jakub Jelinek
2003-07-14 17:11 ` Stephen Rothwell
2003-07-14 17:14 ` Jakub Jelinek
2003-07-14 17:25 ` Stephen Rothwell
2003-07-14 17:45 ` Jakub Jelinek
2003-07-19 18:32 ` Anton Blanchard
2003-07-21 0:08 ` Stephen Rothwell
2003-07-22 13:42 ` Russell King
2003-07-22 13:57 ` Stephen Rothwell
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=OF688246EA.0B58B996-ONC1256D64.00411F64-C1256D64.0041CE23@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).