ih8mj at fjf.gnu.de
Sun Dec 19 02:04:00 CET 2004
Adriaan van Os wrote:
> The back-end team would no longer have false excuses "oh, did you
> integrate gpc been into gcc" or refuse to fix bugs (e.g.
> <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10901>) by giving a bug
> the lowest possible "priority".
Well, this page does contain a reproducible C program for this bug,
which was incidentally also written by me (see
http://www.gnu-pascal.de/crystal/gpc/en/mail8313.html), precisely so
developers wouldn't have to bother with GPC in order to fix this
bug. (And, of course, to make sure the bug isn't in our frontend.)
Even if GPC was integrated, I suppose they'd rather use this C test
when fixing the bug instead of a Pascal test, because most
developers are more familiar with C. And that's fine because it's a
generic backend bug, not specific to either frontend. They can do
this now just as well as later when GPC might be integrated.
But if nobody cares to fix the bug, they don't need any "excuses",
of course (it's free software etc.).
So I fail to see that GPC integration would make any difference here
Frank Heckenbach, frank at g-n-u.de, http://fjf.gnu.de/, 7977168E
GPC To-Do list, latest features, fixed bugs:
NEW! GPC download signing key: ACB3 79B2 7EB2 B7A7 EFDE D101 CD02 4C9D 0FE0 E5E8
More information about the Gpc