Re: [PATCH] de4x5.c

Zlatko Calusic (Zlatko.Calusic@CARNet.hr)
12 Aug 1998 00:30:37 +0200


Linus Torvalds <torvalds@transmeta.com> writes:

> On 11 Aug 1998, Zlatko Calusic wrote:
> >
> > But, what about compatibility (or should I say compilability?) with
> > egcs. It is impossible to compile kernel with egcs without David's
> > patch. Oops at boot stage with something like DE4 in some of the
> > registers. Tried many times with different compilers/optimizations and
> > always failed. Works like a charm now with the patch applied.
>
> With a compiler problem, the only way to find the things tends to be to
> compile the same file with both compilers, and trying to find the
> differences that matter. Sometimes you can just run "diff" on the results,
> but usually there are too many register allocation (or label number)
> differences that confuse diff enough that it doesn't work out too well.
> Even so, just compiling the same file with gcc-2.7.2.1 and egcs and
> looking at it may well uncover the real reason for the problem.
>
> If you have egcs installed, you might just want to do
>
> make drivers/net/de4x5.s

Yep. But only if you know *which* file is really making trouble.

Writing oops (I got when compiled kernel with egcs) to paper, and
decoding it later, I got some addresses out of de4x5.c! Finding "DE"
or something in registers was pure luck. :)

But, thanks for info, anyway.

>
> and send me the asm-file - I could try to see if I see anything obvious
> (but I'd obviously much prefer if somebody else would do more of the work,
> as I'm essentially too lazy to really enjoy doing it myself ;)
>

And I won't blame you for that, that's for sure.

I can always use ye good old 2.7.2.3 GCC and everything will work
perfectly. And I'll do exactly that if we don't come up with the
solution.

So, I could now send you assembler source, or try myself to find where
problem lies, which is probably redundant work, 'cause there are some
clever people out there (Gabriel & David) that know what to do and
where to search for problems. :)

Me... I don't even know x86 assembly, even I'm doing some steps. I'm
more 6502/Z80 kinda guy. :)

Just one additional question: if the problem really lies in string.h,
what stops us to fix it there?

Regards,

-- 
Posted by Zlatko Calusic           E-mail: <Zlatko.Calusic@CARNet.hr>
---------------------------------------------------------------------
	There is an exception to every rule, except this one.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html