Re: PR 43852: new configure option --disable-libstdcxx-verbose

2012-09-09 Thread Jonathan Wakely
On 27 August 2012 18:15, Jonathan Wakely wrote: > Unless anyone has objections I'm going to commit this to trunk, > implementing Sebastian's idea to disable the verbose terminate handler > and the "pure virtual function called" message, which write to stderr > when a process terminates. This allows

Re: PR 43852: new configure option --disable-libstdcxx-verbose

2012-08-28 Thread Joseph S. Myers
On Tue, 28 Aug 2012, Mike Stump wrote: > So, I was thinking about this a little... Native compilers usually want > the pretty verbose stuff and can usually pay the price. Cross compilers > as a class, are less able to pay the price. Maybe we want to default > based merely on target != host?

Re: PR 43852: new configure option --disable-libstdcxx-verbose

2012-08-28 Thread Jonathan Wakely
On 28 August 2012 18:29, Mike Stump wrote: > On Aug 27, 2012, at 10:15 AM, Jonathan Wakely wrote: >> Unless anyone has objections I'm going to commit this to trunk, > >> implementing Sebastian's idea to disable the verbose terminate handler >> and the "pure virtual function called" message, which w

Re: PR 43852: new configure option --disable-libstdcxx-verbose

2012-08-28 Thread Mike Stump
On Aug 27, 2012, at 10:15 AM, Jonathan Wakely wrote: > Unless anyone has objections I'm going to commit this to trunk, > implementing Sebastian's idea to disable the verbose terminate handler > and the "pure virtual function called" message, which write to stderr > when a process terminates. This

PR 43852: new configure option --disable-libstdcxx-verbose

2012-08-27 Thread Jonathan Wakely
Unless anyone has objections I'm going to commit this to trunk, implementing Sebastian's idea to disable the verbose terminate handler and the "pure virtual function called" message, which write to stderr when a process terminates. This allows embedded systems to avoid pulling in the demangler and