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: Joel Sherrill <joel dot sherrill at OARcorp dot com>
- To: Rob Taylor <robt at flyingpig dot com>
- Cc: "Gcc at Gcc dot Gnu. Org" <gcc at gcc dot gnu dot org>
- Date: Tue, 24 Sep 2002 12:10:09 -0500
- Subject: Re: help with reporting bug compiling proprietary code
- Organization: OAR Corporation
- References: <055f01c263cd$31054670$9b00a8c0@highend.co.uk>
- Reply-to: joel dot sherrill at OARcorp dot com
Rob Taylor wrote:
>
> > 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.
Is it sufficient to globally replace meaningful names with automatically
generated
ones so the functionality and purpose of the code is disguised? I have
done this
in the past after I have cut things down as far as I can. At least it
is just
(X1 + X2) * X3 and not as clear.
> Thanks,
>
> Rob Taylor robt@flyingpig.com
> Flying Pig Systems http://www.flyingpig.com
> Tel: +44 20 8280 9230
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985