| To: | Jun Sun <jsun@mvista.com> |
|---|---|
| Subject: | Re: Can't build a CONFIG_CPU_NEVADA kernel |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Wed, 14 Mar 2001 21:02:07 +0100 |
| Cc: | Daniel Jacobowitz <dan@debian.org>, linux-mips@oss.sgi.com |
| In-reply-to: | <3AAFCB24.E7910A9B@mvista.com>; from jsun@mvista.com on Wed, Mar 14, 2001 at 11:48:52AM -0800 |
| References: | <20010314084633.A25674@nevyn.them.org> <20010314195919.A1911@bacchus.dhis.org> <20010314140529.A29525@nevyn.them.org> <20010314202058.B1911@bacchus.dhis.org> <3AAFCB24.E7910A9B@mvista.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Wed, Mar 14, 2001 at 11:48:52AM -0800, Jun Sun wrote: > Although -mmad is generic, why do we need it for kernel compiling? If no good > reason, I propose to remove -mmad from the Makefile for Nevada chip. The compiler actually emits a few mmad instructions, so this instruction actually make a small difference. > Of course, we still need to fix the -mmad implying -m4650 bug ... I guess I leave the -mmad flag in the kernel source as reminder for somebody to fix this ... Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Can't build a CONFIG_CPU_NEVADA kernel, Jun Sun |
|---|---|
| Next by Date: | Re: Can't build a CONFIG_CPU_NEVADA kernel, Daniel Jacobowitz |
| Previous by Thread: | Re: Can't build a CONFIG_CPU_NEVADA kernel, Jun Sun |
| Next by Thread: | Re: Can't build a CONFIG_CPU_NEVADA kernel, Daniel Jacobowitz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |