On Thu, Jan 24, 2013 at 7:15 PM, Jonathan Wakely jwakely@gmail.com wrote:
Googlers, please include the libstdc++ list on patches to the
libstdc++ code, even if it's only to a google branch. I don't read
gcc-patches but am still interested in the changes you make to the
code on your
On Thu, Jan 24, 2013 at 4:15 PM, Jonathan Wakely jwakely@gmail.com wrote:
This does look like something that could be included in debug mode,
but probably not until we're back in Stage 1. Please either put it in
Bugzilla (and CC me) or if you're diligent enough to remember please
email
On Thu, Jan 24, 2013 at 1:23 AM, Paul Pluzhnikov ppluzhni...@google.com wrote:
This patch allows us to catch use of destructed strings.
Google ref: b/5430313
Ok for google/gcc-4_7 and google/integration?
OK.
Diego.
On Wed, 23 Jan 2013, Paul Pluzhnikov wrote:
This patch allows us to catch use of destructed strings.
Hello,
while a number of the google debug patches are just cheaper versions (that
don't break the ABI) of what libstdc++'s debug mode provides, this
overwriting of classes on destruction is
On 24 January 2013 19:03, Marc Glisse wrote:
On Wed, 23 Jan 2013, Paul Pluzhnikov wrote:
This patch allows us to catch use of destructed strings.
Hello,
while a number of the google debug patches are just cheaper versions (that
don't break the ABI) of what libstdc++'s debug mode provides,
This patch allows us to catch use of destructed strings.
Google ref: b/5430313
Ok for google/gcc-4_7 and google/integration?
--
Paul Pluzhnikov
Index: libstdc++-v3/include/ext/sso_string_base.h
===
---
