From: "Martin Schwidefsky" <schwidefsky@de.ibm.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Change s390 ssize_t back to long int
Date: Wed, 17 Sep 2003 09:36:00 -0000 [thread overview]
Message-ID: <OF62ED3256.457BE647-ONC1256DA4.00333AC0-C1256DA4.0034BFD7@de.ibm.com> (raw)
Hi Ulrich,
> I've applied the patch now. It should be clear that this is a break of
> the ABI from early glibc versions.
Yes, Jakub discussed this with me and we came to the conclusion that this
is acceptable. We only break if someone uses gcc 3.x with the old ssize_t
type of int to compile c++ code and mixes the binaries with code compiled
with gcc 3.x with the new ssize_t of long. The if here is that gcc 3.x
should only be used with a new libc which has a ssize_t of long.
blue skies,
Martin
next reply other threads:[~2003-09-17 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 9:36 Martin Schwidefsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 14:40 Jakub Jelinek
2003-09-14 8:04 ` Ulrich Drepper
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=OF62ED3256.457BE647-ONC1256DA4.00333AC0-C1256DA4.0034BFD7@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.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).