Date: Mon, 11 Nov 2002 18:39:01 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: John Baldwin <jhb@FreeBSD.org> Cc: alpha@FreeBSD.org, Andrew Gallatin <gallatin@cs.duke.edu> Subject: Re: ev4/5/6 issue ? Message-ID: <57358.1037036341@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 11 Nov 2002 12:23:15 EST." <XFMail.20021111122315.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <XFMail.20021111122315.jhb@FreeBSD.org>, John Baldwin writes: > >On 11-Nov-2002 Poul-Henning Kamp wrote: >> In message <15823.51765.171947.796322@grasshopper.cs.duke.edu>, Andrew Gallatin >> writes: >> >>>Your initial assertion that this might be happening because the >>>libraries are built for ev6 on beast could be true. Can you verify >>>that that 12001f4e4 is indeed inside a library function using nm? >> >> Well, GDB said that much already. >> >>>That doesn't solve the initial problem of why your make was busted, >>>though. If its in the libs, then your libs are likely busted too. >>>Perhaps you'll also need to build a libc on beast, explicitly >>>setting your cpuflags to ev4. Or perhaps the compiler is emitting >>>FIX instructions when it should not. >> >> I think ev4 should be the default on beast. > >This release wasn't built on beast. It was built on a DS20 (which >is an EV6). However, it should be built with '-mcpu=ev4 -mtune=ev6' >so it should not be using any !ev4 instructions. Perhaps -mtune >is broken? Could be, but I tried to build some binaries on beast to recover and was bitten by beast generating ev6 as default. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57358.1037036341>