archive mirror
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <>
To: Jakub Jelinek <>
Subject: Re: sizeof (siginfo_t) problem
Date: Mon, 14 Jul 2003 20:52:20 +0200	[thread overview]
Message-ID: <> (raw)

Jakub Jelinek wrote:

>As I tried to write, we either can have all GCCs
>which will work properly only with new kernels (no pad added),
>or we can have new GCCs working with all kernels (if pad is added).
>Your choice...

I'll discuss this with Martin tomorrow, but right now I'd tend to
fixing the kernel, because this means you can fix an installed
system by upgrading only the kernel itself (and this upgrade
should not break anything).  The alternative would be not only
to upgrade libgcc (and possibly glibc), but all programs statically
linked with it as well as all programs that otherwise have the
signal stack layout hardcoded ...

Mit freundlichen Gruessen / Best Regards

Ulrich Weigand

  Dr. Ulrich Weigand
  Linux for S/390 Design & Development
  IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
  Phone: +49-7031/16-3727   ---   Email:

             reply	other threads:[~2003-07-14 18:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 18:52 Ulrich Weigand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15 11:58 sizeof (siginfo_t) problem Martin Schwidefsky
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).