On Wed, 13 Jan 2010, Nelson A. de Oliveira wrote:
> But I want to confirm if it's indeed a problem with gcc 4.5 (and thus
> nothing will be necessary to change on our side) or if it's a problem
> in the code (that is now triggered by a stricter compiler).
> Better ask than wrongly and doubtfully reassign it to gcc-4.5 :-)
There is no visible sign that anybody cared to reassign this bug to gcc.
So what should we do with this bug?
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
