From: Ben Collins <bcollins@debian.org>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: using gcc built-ins for bitops?
Date: Thu, 24 Jun 2004 09:41:04 -0400 [thread overview]
Message-ID: <20040624134103.GB9774@phunnypharm.org> (raw)
In-Reply-To: <20040624090605.GA11805@devserv.devel.redhat.com>
> 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.
You could have an asm-generic/bitops-builtin.h and arch's could #include
that after defining all the HAVE_BUILTIN_xxx macros they want. I suspect
not all architectures will get the most correct built-ins (e.g. the arch
may be able to optimize better than gcc's builtin is doing).
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next prev parent reply other threads:[~2004-06-24 16:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 7:09 Arjan van de Ven
2004-06-24 9:00 ` Andrew Morton
2004-06-24 9:06 ` Arjan van de Ven
2004-06-24 13:41 ` Ben Collins [this message]
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=20040624134103.GB9774@phunnypharm.org \
--to=bcollins@debian.org \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®