bug report with downloaded copiler

[Joe Buck]

On Wed, Mar 03, 2004 at 12:37:13PM -0600, Nathan Holladay wrote:
> The current compiler that I am using was downloaded as an executable
> from Sun freeware (gcc 3.3.2). The bug information page at
> http://gcc.gnu.org/bugs.html indicates that you do not want:
> 
> "Bugs in releases or snapshots of GCC not issued by the GNU Project.
> Report them to whoever provided you with the release"
> 
>   I do not particularly want to ask my system administrator to download
> and compile gcc 3.3.2 himself when we already have what appears to be a
> quite valid version, and when the bug is a simple, apparently erroneous
> parse error that can be produced in a small amount of code and seems
> unlikely to be system/compilation specific.
> Should I have him compile gcc 3.3.2 (gcc 3.3.3 does not appear to be at
> the location given in the website), or can I go ahead and report the
> bug?

Well, it depends.  If the package that you download from a third party is
non-functional (doesn't work at all, or important headers or libraries are
missing), it makes no sense to report the problem to the GCC list.

However, if it mostly functions but appears to have a bug, then please go
ahead and file a bug report.  If a GCC tester can duplicate it with an
FSF release, then it will be treated as a confirmed bug.  That would seem
to apply in your case.  So please, go ahead and file a bug with Bugzilla
( http://gcc.gnu.org/bugzilla/ ).