From: Dave Jones <davej@codemonkey.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Grzegorz Jaskiewicz <gj@pointblue.com.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] vmalloc, kmalloc - 2.4.x
Date: Tue, 4 Feb 2003 12:33:58 +0000 [thread overview]
Message-ID: <20030204123358.GB29160@codemonkey.org.uk> (raw)
In-Reply-To: <1044312846.28406.31.camel@imladris.demon.co.uk>
On Mon, Feb 03, 2003 at 10:54:06PM +0000, David Woodhouse wrote:
> GCC is likewise perfectly entitled to use floating point even if you
> only used integers in the source. There's a good reason why the SH port
> builds with '-mno-implicit-fp' and why all other ports should have this
> _before_ it becomes a problem rather than afterwards.
I was wondering about this yesterday when toying with the -march options
we now pass. With (for eg) -march=c3, we now tell gcc it can emit 3dnow
instructions if it wants, likewise SSE/SSE2 in other -march options.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2003-02-04 12:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1044284924.2402.12.camel@gregs>
[not found] ` <1044289102.21009.1.camel@irongate.swansea.linux.org.uk>
2003-02-03 15:40 ` [BUG] vmalloc, kmalloc - 2.4.x Grzegorz Jaskiewicz
2003-02-03 15:40 ` Grzegorz Jaskiewicz
2003-02-03 17:02 ` Benjamin Herrenschmidt
2003-02-03 17:18 ` Alan Cox
2003-02-03 22:54 ` David Woodhouse
2003-02-04 9:35 ` Arjan van de Ven
2003-02-04 12:33 ` Dave Jones [this message]
2003-02-03 15:13 Grzegorz Jaskiewicz
2003-02-03 15:19 ` Oliver Neukum
2003-02-03 15:19 ` Arjan van de Ven
2003-02-03 15:35 ` Grzegorz Jaskiewicz
2003-02-03 15:35 ` Arjan van de Ven
2003-02-03 22:52 ` David Woodhouse
2003-02-03 15:22 ` Arjan van de Ven
2003-02-03 15:42 ` Grzegorz Jaskiewicz
2003-02-03 15:52 ` Russell King
2003-02-03 15:58 ` Arnaldo Carvalho de Melo
2003-02-03 16:07 ` Grzegorz Jaskiewicz
2003-02-03 15:39 ` Richard B. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030204123358.GB29160@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=gj@pointblue.com.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.