public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Manfred Hollstein <manfred@s-direktnet.de>
To: hjl@lucon.org, drepper@cygnus.com
Cc: kenner@vlsi1.ultra.nyu.edu, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: libstdc++-2.8.1 - Ready for testing
Date: Mon, 23 Feb 1998 13:07:00 -0000	[thread overview]
Message-ID: <199802231800.TAA27316@saturn.s-direktnet.de> (raw)
In-Reply-To: <m0y71Zo-00058gC@ocean.lucon.org>

On Mon, 23 February 1998, 09:22:00, hjl@lucon.org wrote:

 > > 
 > > Of course, they were not :-( Your patches for make check with gcc dir missing
 > > were not in. I'm just uploading a new version libstdc++-2.8.1-980222 and will
 > > delete yesterday's one. Sorry for the confusion.
 > > 
 > 
 > There is a new libio patch for glibc 2.1 submitted for egcs. Ulrich
 > should know if it is correct.

Do you mean this one?

On , 23 February 1998, 11:16:40, schwab@issan.informatik.uni-dortmund.de wrote:

 > This patch fixes some problems in libio in connection with glibc 2.1.
 > Note that the change of _IO_wchar_t is a binary incompatibility, so users
 > of glibc 2.1 snapshots need to recompile at least all code that uses
 > [io]fstream.
 > 
 > 
 > 1998-02-22  Andreas Schwab  <schwab@issan.informatik.uni-dortmund.de>
 > 
 > 	Changes for _G_IO_IO_FILE_VERSION == 0x20001:
 > 	* libioP.h (_IO_showmanyc_t, _IO_SHOWMANYC, _IO_imbue_t,
 > 	_IO_IMBUE): New definitions.
 > 	(struct _IO_jump_t): Add __showmanyc and __imbue fields.
 > 	(_IO_file_fopen): Add new fourth argument.
 > 	* filebuf.cc (filebuf::open): Pass new fourth argument to
 > 	_IO_file_fopen.
 > 	* iolibio.h (_IO_freopen): Likewise.
 > 	* streambuf.cc (streambuf::showmanyc, streambuf::imbue): New
 > 	functions.
 > 	* streambuf.h (_IO_wchar_t): Define to _G_wchar_t.
 > 	(ios::fill): Remove casts.
 > 	(struct streambuf): Add showmanyc and imbue members.
 > 
 > 	* iostream.cc (ostream::operator<<(double n)) [__GLIBC_MINOR__ >=
 > 	1]: Initialize new fields is_char of struct printf_info.
 > 	(ostream::operator<<(long double n)) [__GLIBC_MINOR__ >= 1]:
 > 	Likewise.

Ulrich, is it ok to apply?

Thanks

Manfred

  reply	other threads:[~1998-02-23 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-20 10:10 Manfred Hollstein
1998-02-20 12:26 ` H.J. Lu
1998-02-20 12:26   ` Manfred Hollstein
1998-02-21  9:51     ` Manfred Hollstein
1998-02-21 15:27       ` H.J. Lu
1998-02-22  3:20         ` Manfred Hollstein
1998-02-22  3:22           ` Manfred Hollstein
1998-02-23 11:00             ` H.J. Lu
1998-02-23 13:07               ` Manfred Hollstein [this message]
1998-02-23 11:54                 ` Ulrich Drepper
1998-02-22  4:57       ` Andi Kleen
1998-02-22  8:37         ` Manfred Hollstein
     [not found] <9802202130.AA05758@vlsi1.ultra.nyu.edu>
1998-02-21 14:20 ` Manfred Hollstein

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=199802231800.TAA27316@saturn.s-direktnet.de \
    --to=manfred@s-direktnet.de \
    --cc=drepper@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=gcc2@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).