This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: help with reporting bug compiling proprietary code
- From: "Rob Taylor" <robt at flyingpig dot com>
- To: "Rob Taylor" <robt at flyingpig dot com>, "Gcc at Gcc dot Gnu. Org" <gcc at gcc dot gnu dot org>
- Date: Tue, 24 Sep 2002 14:20:46 +0100
- Subject: RE: help with reporting bug compiling proprietary code
> I'm hitting a pretty serious optimisation bug in some proprietary code, and I
> don't seem to be able to provide a simple testcase (if I remove a
> single line of
> code, it goes away!). I can't post all the prepossessed source up on gnats for
> all the world to see, but I could wrangle allowing certain gcc maintainers
> access - what's the procedure in these cases?
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.
Thanks,
Rob Taylor robt@flyingpig.com
Flying Pig Systems http://www.flyingpig.com
Tel: +44 20 8280 9230