From: Richard Henderson <rth@twiddle.net>
To: Bernardo Innocenti <bernie@develer.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org,
Peter Chubb <peter@chubb.wattle.id.au>,
Andrew Morton <akpm@digeo.com>, Ian Molton <spyro@f2s.com>,
gcc@gcc.gnu.org
Subject: Re: [PATCH] Fix do_div() for all architectures
Date: Thu, 10 Jul 2003 15:04:04 -0700 [thread overview]
Message-ID: <20030710220404.GA20109@twiddle.net> (raw)
In-Reply-To: <200307102131.45474.bernie@develer.com>
On Thu, Jul 10, 2003 at 09:31:45PM +0200, Bernardo Innocenti wrote:
> Just to open some interesting speculation, do you think we'd
> get better code by just getting rid of __attribute__((pure))
> or by changing __do_div64() to do something like this?
>
> typedef struct { uint64_t quot, uint32_t rem } __quotrem64;
> __quotrem64 __do_div64(uint64_t div, uint32_t base) __attribute__((const));
No. Most targets require structures be returned in memory.
If people really care beyond the generic, they'll write
special assembly for it.
r~
next prev parent reply other threads:[~2003-07-10 21:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 23:33 [PATCH] Fix do_div() for all architectures Bernardo Innocenti
2003-07-06 7:47 ` Russell King
2003-07-06 15:40 ` Ian Molton
2003-07-07 4:26 ` Bernardo Innocenti
2003-07-08 18:27 ` Bernardo Innocenti
2003-07-08 18:31 ` Andrew Morton
2003-07-08 20:56 ` Bernardo Innocenti
2003-07-10 15:40 ` Richard Henderson
2003-07-10 16:18 ` Andrea Arcangeli
2003-07-10 16:39 ` Richard Henderson
2003-07-10 19:31 ` Bernardo Innocenti
2003-07-10 19:53 ` Dale Johannesen
2003-07-10 20:19 ` Andrea Arcangeli
2003-07-10 22:58 ` Bernardo Innocenti
2003-07-10 22:04 ` Richard Henderson [this message]
2003-07-10 23:13 ` Bernardo Innocenti
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 16:16 [PATCH] Kill div64.h dupes, parenthesize do_div() macro params Linus Torvalds
2003-07-03 10:43 ` [PATCH] Fix do_div() for all architectures Bernardo Innocenti
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=20030710220404.GA20109@twiddle.net \
--to=rth@twiddle.net \
--cc=akpm@digeo.com \
--cc=andrea@suse.de \
--cc=bernie@develer.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=spyro@f2s.com \
--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.