RE: help with reporting bug compiling proprietary code

["Rob Taylor" <robt at flyingpig dot com>]

> > I should point out that I'm not asking for free support here and
> can work around
> > the bug, but I would rather the bug was fixed in gcc, as I'm sure would all.
> > Which is the reason for my query.
>
> You need to do your part of the volunteer work, which is to find a
> reproducible example!
>

I have a reproducible example - I have one .i file which displays the bug and
one .i file that doesn't with 1 function difference. I just can't post it up to
gnats, as there is proprietary code in that .i that I cant strip without the
problem going away..

If I could fix the bug myself I would, but the last time I studied gcc's
internals in any depth was over 3 years ago and I suspect it's rather changed
since then, from the looks of it it looks like there's a corner of the
optimisation code that doesnt notice when a const member variable has been
subjected to a const_cast and treats it like a real const variable

If noone's interested in fixing it then so be it - we can just wait until
someone finds a better test case. I've already worked around it (by changing the
const * const to a plain const* - don't ask me why on earth the original coder
was using a const*const member and casting away constness in the 1st place, but
i'm sure he had a good reason at the time)

Rob Taylor              robt@flyingpig.com
Flying Pig Systems      http://www.flyingpig.com
                        Tel: +44 20 8280 9230