------- Comment #6 from wielemak at science dot uva dot nl 2006-03-03 10:55
-------
So true, but you have a test-case. Ok, its a big program, but it will do
the job for you in 5 minutes typing 3 commands. Turning it into a small
program is not a trivial exercise, while it definitely doesn't help verifying
whether the bug is still present and isn't even that likely to help finding
it. Quite likely simply reading the assembly of the function will tell you
the output is wrong. I guess it either skipped the assignment or writes to
the wrong place. My assembly experience is too outdated and I never saw
Alpha assembly.
True, you're a volunteer, but the same holds for me, fixing similar
problems in SWI-Prolog. My only criterium is something I can unpack and
run in a few commands. Only if it turns out that their is no way to tell
whether the bug is in my compiler or not without examining large parts of
the program I ask the submitter to create a small program.
Cheers --- Jan
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26511
