https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44435
--- Comment #8 from joseph at codesourcery dot com ---
I have not been tracking the state of review or lack thereof for these
patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44435
Eric Gallager changed:
What|Removed |Added
CC||dj at redhat dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44435
--- Comment #6 from Eric Gallager ---
(In reply to jos...@codesourcery.com from comment #5)
> Subject: Re: gengtype: don't test undefined value after
> vasprintf failure
>
> On Mon, 7 Jun 2010, dj at redhat dot com wrote:
>
> > > If the libib
--- Comment #5 from joseph at codesourcery dot com 2010-06-07 20:17 ---
Subject: Re: gengtype: don't test undefined value after
vasprintf failure
On Mon, 7 Jun 2010, dj at redhat dot com wrote:
> > If the libiberty maintainers won't review the xvasprintf patch,
>
> I did: http://gcc
--- Comment #4 from jim at meyering dot net 2010-06-07 18:24 ---
Good! I see that there's already a patch to deal with all of the unchecked
asprintf calls, too.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44435
--- Comment #3 from dj at redhat dot com 2010-06-07 18:14 ---
Subject: Re: gengtype: don't test undefined value after vasprintf failure
> If the libiberty maintainers won't review the xvasprintf patch,
I did: http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00589.html
--
http://gcc.
--- Comment #2 from jsm28 at gcc dot gnu dot org 2010-06-06 15:53 ---
If the libiberty maintainers won't review the xvasprintf patch, perhaps
a global reviewer could do so? That would be better than fiddling with
local checks.
http://gcc.gnu.org/ml/gcc-patches/2009-11/msg01448.html
htt
