> In the one I commented on, the error message reported was
> "Panic: ...
> Internal error, please report this bug"
>
> If that does not clearly indicate that is a bug I don't know what will!
I think we basically all agree here. As I pointed out that Richard
Maine had pointed out, such a message is ALWAYS a bug in some sense.
However, it does not mean that the ONLY problem is a bug in the
compiler; there might be a bug in the code as well...
> >I had several cases in the last 2 or 3 years, where it took me some
> >time, and help from the contributors of this list, to decide whether
> >a problem was a compiler bug or not.
...thus the need, while the compiler bug is being investigated, to
determine whether the code is non-standard. Of course, common things
are well-tested; it is things on the edge of the standard---possibly
requiring interpretations---which can cause trouble. Again, one can and
should separate the two questions: compiler bug? standard code?
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|