From owner-freebsd-alpha  Mon Nov 11 10: 7: 1 2002
Delivered-To: freebsd-alpha@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2B58F37B401; Mon, 11 Nov 2002 10:07:00 -0800 (PST)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4C48043E3B; Mon, 11 Nov 2002 10:06:59 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA19871;
	Mon, 11 Nov 2002 13:06:58 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gABI6Q848106;
	Mon, 11 Nov 2002 13:06:26 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15823.61858.784838.471039@grasshopper.cs.duke.edu>
Date: Mon, 11 Nov 2002 13:06:26 -0500 (EST)
To: John Baldwin <jhb@FreeBSD.org>
Cc: alpha@FreeBSD.org, obrien@FreeBSD.org, kan@FreeBSD.org
Subject: Re: ev4/5/6 issue ?
In-Reply-To: <XFMail.20021111122315.jhb@FreeBSD.org>
References: <55809.1037029315@critter.freebsd.dk>
	<XFMail.20021111122315.jhb@FreeBSD.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-alpha.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-alpha>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-alpha>
X-Loop: FreeBSD.org


John Baldwin writes:
 > so it should not be using any !ev4 instructions.  Perhaps -mtune
 > is broken?
 > 
 > Hmm, actually, the whole release was compiled with
 > '-mcpu=ev5 -mtune=ev5'.  I do know that on alpha gcc "adjusts" itself
 > to whatever CPU it is built on, so maybe because the gcc in the release
 > make world was built on an EV6 it thinks it can emit EV6 instructions?
 > 
 > Weird.

I was worried about this self-adjustment myself, but I thought that it
was a function of gnu configure,  and would be taken care of by
the way we emulate or otherwise fake-out configre for the in-tree gcc.

gcc gurus?

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message