public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: matti.rintala@tut.fi To: gcc-gnats@gcc.gnu.org Cc: matti.rintala@tut.fi Subject: libstdc++/3904: STL does not use ::operator new as required in standard Date: Tue, 31 Jul 2001 12:26:00 -0000 [thread overview] Message-ID: <200107311923.f6VJNrH07043@mustikkakukko.cs.tut.fi> (raw) >Number: 3904 >Category: libstdc++ >Synopsis: STL does not use ::operator new as required in standard >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Jul 31 12:26:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Matti Rintala >Release: 3.0 >Organization: >Environment: System: Linux mustikkakukko.cs.tut.fi 2.4.5 #1 Tue May 29 19:53:48 EEST 2001 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../gcc-3.0/configure --host=athlon-pc-linux-gnu --prefix=/usr/local/gcc-3.0 --enable-shared --enable-threads --with-cpu=athlon --enable-cpp >Description: ISO C++ standard states that by default STL containers use std::allocator to obtain memory. std::allocator in turn is required to use ::operator new and ::operator delete. However, STL in GCC specifically detects the use of std::allocator and uses malloc() in this case (this behaviour comes from the SGI STL code base). This breaks programs which override the default ::operator new and ::operator delete. I understand the need for customised dynamic memory handling (which its own free memory lists etc) in STL, because it increases performance. However, even these kinds of optimisations should use ::operator new instead of malloc() so that they don't break the standard. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-07-31 12:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-31 12:26 matti.rintala [this message] 2001-08-07 10:58 ljrittle
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=200107311923.f6VJNrH07043@mustikkakukko.cs.tut.fi \ --to=matti.rintala@tut.fi \ --cc=gcc-gnats@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: linkBe 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).