--- Comment #30 from manu at gcc dot gnu dot org 2009-07-07 22:20 ---
FIXED in GCC 4.5.
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
Status|REO
--- Comment #29 from manu at gcc dot gnu dot org 2009-07-07 22:18 ---
Subject: Bug 31246
Author: manu
Date: Tue Jul 7 22:18:35 2009
New Revision: 149354
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149354
Log:
2009-07-08 Manuel López-Ibáñez
PR c++/31246
--- Comment #28 from manu at gcc dot gnu dot org 2009-02-07 21:07 ---
There is a patch here:
http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00972.html
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #27 from manu at gcc dot gnu dot org 2008-10-22 08:35 ---
(In reply to comment #5)
> Note, however, that, as far as I can see, such try/catch are *not* in the
> library code proper, but *all* synthesized by the C++ front-end.
Does anyone has any idea where in the C++ front-e
--- Comment #26 from gdr at integrable-solutions dot net 2008-08-26 05:45
---
Subject: Re: Strange -Wunreachable-code warning with _GLIBCXX_DEBUG
On Sat, Aug 23, 2008 at 1:43 PM, paolo dot carlini at oracle dot com
<[EMAIL PROTECTED]> wrote:
> --- Comment #23 from paolo dot carlin
--- Comment #25 from manu at gcc dot gnu dot org 2008-08-23 18:50 ---
This looks clearer to me. Maybe Jason or Mark have some idea where this code is
generated. It should be clear that it is compiler-generated and we can set
DECL_ARTIFICIAL or TREE_NO_WARNING. Then we just have to make s
