NetBSD Problem Report #15312

Received: (qmail 17845 invoked from network); 20 Jan 2002 12:04:36 -0000
Message-Id: <200201201204.g0KC4ZW05829@quartz.clock.org>
Date: Sun, 20 Jan 2002 04:04:35 -0800 (PST)
From: "Erik E. Fair" <fair@quartz.clock.org>
Reply-To: fair@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Subject: GENERIC3X config should have makeoptions CFLAG= -m68030 added
X-Send-Pr-Version: 3.95

>Number:         15312
>Category:       port-sun3
>Synopsis:       GENERIC3X config should have makeoptions CFLAG= -m68030 added
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    port-sun3-maintainer
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Jan 20 12:05:00 +0000 2002
>Closed-Date:    Sun Feb 10 18:24:00 +0000 2002
>Last-Modified:  Tue Feb 12 09:17:00 +0000 2002
>Originator:     Erik E. Fair
>Release:        NetBSD 1.5.2
>Organization:
International Organization of Internet Clock Watchers
>Environment:

>Description:
	The sun3x always has an mc68030 CPU, and so the kernels for those
	systems can be compiled specifically for that CPU.

	This is similar to NetBSD/arm32 on the DNARD ("Shark") which always
	has a StrongARM CPU in it; their "SHARK" config specifies gcc options
	to optimize for that CPU.

	The only question is, would this make any difference?
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: chs 
State-Changed-When: Sun Feb 10 10:23:24 PST 2002 
State-Changed-Why:  
sun3x kernels will now be built with -m68030. 

From: "Erik E. Fair" <fair@clock.org>
To: chs@netbsd.org
Cc: port-sun3-maintainer@netbsd.org,
   NetBSD GNATS Problem Report Tracking System <gnats-bugs@gnats.netbsd.org>
Subject: Re: port-sun3/15312
Date: Tue, 12 Feb 2002 01:15:30 -0800

 Excellent! Thank you.

 	Erik <fair@clock.org>
>Unformatted:

Home	PR Database Search