public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Pétur Runólfsson" <peturr02@ru.is>
To: jlquinn@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: libstdc++/9828: Regression: Segmentation fault in num_put::put
Date: Thu, 03 Apr 2003 15:46:00 -0000	[thread overview]
Message-ID: <20030403154600.28127.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/9828; it has been noted by GNATS.

From: =?iso-8859-1?Q?P=E9tur_Run=F3lfsson?= <peturr02@ru.is>
To: "Jerry Quinn" <jlquinn@optonline.net>,
	<paolo@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Cc: <libstdc++@gcc.gnu.org>
Subject: RE: libstdc++/9828: Regression: Segmentation fault in num_put::put
Date: Thu, 3 Apr 2003 15:36:27 -0000

 Jerry Quinn wrote:
 > Another is that locales carry the cache info to avoid this problem.
 
 I think this might be the best solution; it is very common to
 create a stringstream just to format one number (see for
 example boost::lexical_cast or operator<<(ostream&, complex&)).
 Storing the cache in the locale would allow such code to take
 advantage of the caches.
 
 It should be easy to implement this using the same techniques
 as are used for storing facets in locales.
 
 Regards,
 Petur


             reply	other threads:[~2003-04-03 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03 15:46 Pétur Runólfsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-03 16:36 Benjamin Kosnik
2003-04-03 16:26 Benjamin Kosnik
2003-04-03 16:16 Benjamin Kosnik
2003-04-03 14:46 Jerry Quinn
2003-03-25 13:46 jlquinn
2003-03-25 13:15 Paolo Carlini
2003-03-25 13:06 Paolo Carlini
2003-03-25  6:46 Jerry Quinn
2003-03-24 13:41 paolo
2003-02-24  9:26 peturr02

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=20030403154600.28127.qmail@sources.redhat.com \
    --to=peturr02@ru.is \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jlquinn@gcc.gnu.org \
    /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).