On 1 May 2014 17:18, Oleg Endo wrote:
> Jonathan,
>
> now that we're in stage 1 again, I'd like to revive the issue below. Do
> you have any particular plans? How should we proceed?
Hi Oleg, sorry for letting the thread die in January.
We will definitely want to deal with the missing constructo
Jonathan,
now that we're in stage 1 again, I'd like to revive the issue below. Do
you have any particular plans? How should we proceed?
Cheers,
Oleg
On Wed, 2014-01-29 at 23:45 +0100, Oleg Endo wrote:
> On Wed, 2014-01-29 at 21:38 +, Jonathan Wakely wrote:
> > On 29 January 2014 21:17, Ole
On Wed, 2014-01-29 at 21:38 +, Jonathan Wakely wrote:
> On 29 January 2014 21:17, Oleg Endo wrote:
> > My original intention was to eliminate code bloat when doing something
> > like throw std::logic_error ("cold coffee");
> > If the const char* overloads are inlined it will emit code to const
On 29 January 2014 21:17, Oleg Endo wrote:
> My original intention was to eliminate code bloat when doing something
> like throw std::logic_error ("cold coffee");
> If the const char* overloads are inlined it will emit code to construct
> an std::string from const char* in user code where the exce
On Wed, 2014-01-29 at 15:21 +, Jonathan Wakely wrote:
> On 26/01/14 15:15 +0100, Oleg Endo wrote:
> >> Files in libstdc++-v3/src/c++98/ seem to be never compiled with C++11.
> >> Thus I can think of two options:
> >> 1) Add const char* ctors for C++98 and C++11.
> >> 2) Add #ifdef'ed declaratio
On 26/01/14 15:15 +0100, Oleg Endo wrote:
Files in libstdc++-v3/src/c++98/ seem to be never compiled with C++11.
Thus I can think of two options:
1) Add const char* ctors for C++98 and C++11.
2) Add #ifdef'ed declarations to libstdc++-v3/include/std/stdexcept and
add a new file libstdc++-v3/src/c
Ping.
The patch in question is here:
http://gcc.gnu.org/ml/gcc-patches/2013-12/msg01688.html
On Thu, 2013-12-19 at 16:28 +0100, Oleg Endo wrote:
> On Thu, 2013-12-19 at 01:19 +, Jonathan Wakely wrote:
> > On 19 December 2013 00:10, Oleg Endo wrote:
> > > Hello,
> > >
> > > When writing code s