This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Possible Bug


> I will try using the latest version of GCC if necessary, but the machine
> that shows the failure is not "netable" so this would not be easy to
> do.  Enclosed are the driver C code and a dmesg dump showing the result
> of the two reads.

Thanks for your bug report. As it is, it is not as useful as it could
be. Please send preprocessor output instead of original source, that
way, people can try to reproduce it without having to get the exact
same kernel header files you were using (you also didn't indicate what
those were).

Furthermore, it would be very good if you could identify the place in
assembler file which is miscompiled. Please attach the assembler file
you get and indicate where exactly you are seeing wrong code emitted
(you may want to strip-down the preprocessor output to only include
the function in question, which also reduces the assembler file and
allows to throw-away much of the preprocessor output that is not used,
but that is not necessary).

With that information, somebody else could try and see whether the bug
still occurs in gcc 2.95.

Regards,
Martin


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]