From: Arjan van de Ven <arjanv@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: using gcc built-ins for bitops?
Date: Thu, 24 Jun 2004 11:06:05 +0200 [thread overview]
Message-ID: <20040624090605.GA11805@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040624020022.0601d4ae.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On Thu, Jun 24, 2004 at 02:00:22AM -0700, Andrew Morton wrote:
> > and/or architectures.... is this worth doing?
>
> I guess it depends on the resulting code size and quality. Some extra
> conversions would be needed for that.
ok I'll see if I can get some detailed info on that
>
> For the implementation it would be nice to have the old-style
> implementations in one header and the new-style ones in a separate header.
> That would create a bit of an all-or-nothing situation, but that should be
> OK?
Perhaps. It's not impossible that say gcc 3.5 will add a few more builtins
even that then allow more functions to be converted, otoh that shouldn't be
impossible to cope with. I'll have a look to see how it pans out.
Greetings,
Arjan van de Ven
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-24 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 7:09 using gcc built-ins for bitops? Arjan van de Ven
2004-06-24 9:00 ` Andrew Morton
2004-06-24 9:06 ` Arjan van de Ven [this message]
2004-06-24 13:41 ` Ben Collins
2004-06-24 9:17 ` Arjan van de Ven
2004-06-24 11:31 ` Arjan van de Ven
2004-06-24 12:05 ` Jakub Jelinek
2004-06-24 12:35 ` Arjan van de Ven
2004-06-24 15:30 ` Linus Torvalds
2004-06-24 9:31 ` Paul Jackson
2004-06-24 10:36 ` Jakub Jelinek
2004-06-24 15:25 ` Linus Torvalds
2004-06-24 11:51 ` Gabriel Paubert
2004-06-24 12:21 ` Arjan van de Ven
[not found] <2awGH-DF-17@gated-at.bofh.it>
2004-06-24 13:46 ` Pascal Schmidt
2004-06-24 13:49 ` Arjan van de Ven
2004-06-24 13:51 ` Pascal Schmidt
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=20040624090605.GA11805@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.