Re: Oops linux 2.4.23-pre6 on amd64

From: Tony Hoyle (tmh_at_nodomain.org)
Date: 10/05/03

  • Next message: Olaf Dietsche: "Re: [PATCH] 2.6.0-test6: Filesystem capabilities 0.15" 
    Date:	Sat, 04 Oct 2003 23:34:36 +0100
To: Andi Kleen <ak@colin2.muc.de>

    Andi Kleen wrote:
    >>Oops, scratch that last one... It's invalid too as I used the original
    >>oops rather than the new one. This one's the right one (honest!).
    >
    >
    > I cannot see anything obviously wrong. At which kernel version did the
    > problem start? And is your compiler version known to be not buggy ?

    AFAIK there is only one version that supports compiling to amd64 (only
    one for debian anyway) - I'm on 3.3.2-0pre4.biarch1. It is a bit flaky
    (in 32bit it'll happily do a make -j255 without worrying... going to 64
    bit needs about 10 attempts to do a single compile because it keeps
    falling over with internal compiler errors/segfaults/etc.).

    The problem with a brand new architecture is until the toolset
    stabliizes I have to cross my fingers and hope. Certainly if it's
    compiling dodgy code it'll explain why Alsa is about as stable as a
    drunk in a high wind...

    OK I'll forget it for now & go back to 32bit for a couple of months then
    try again.

    Tony

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Olaf Dietsche: "Re: [PATCH] 2.6.0-test6: Filesystem capabilities 0.15"

    Relevant Pages

    • Re: How so ?
      ... as s is a pointer to an array of char -- but no one ever bothers, ... and the compiler will complain in g++. ... This one actually works in VMS -- or did, ... The old "oops I forgot that extra char" problem. ...
      (microsoft.public.win32.programmer.ui)
    • Re: Do not misuse Coverity please (Was: sound/oss/cs46xx.c: fix a check after use)
      ... > No, there is a third case: the pointer can be NULL, but the compiler ... just hope that the gcc folks know their business:) ... > with -O0, it will oops. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Another sizeof question
      ... so it is not evaluated by sizeof. ... Oops, yes. ... int n = 42; ... the compiler do with the result of computing xanyway? ...
      (comp.lang.c)
    • Re: Nochn Closure Proposal
      ... for each e in the receiver. ... und der Typ von E wird vom cOmpiler bestimmt? ... Oops, nein, das ist eine Methode von Readermit read: ...
      (de.comp.lang.java)
    • Re: Q: Checking the size of a non-allocated array?
      ... an actual argument is already invalid ... First note that you don't have an unallocated array in the subroutine. ... it is comparable to disassociated or undefined pointers. ... Obviously the compiler has ...
      (comp.lang.fortran)
    Loading