From: Mark Mitchell <mark@codesourcery.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Nathan Froyd <froydnj@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] optimize bitmap_bit_p + bitmap_{clear,set}_bit
Date: Thu, 19 Aug 2010 20:05:00 -0000 [thread overview]
Message-ID: <4C6D8B5A.9050007@codesourcery.com> (raw)
In-Reply-To: <AANLkTimdGvq=59eKWnRydYiJtmtFbfmNEEL5n4-QE1++@mail.gmail.com>
Richard Guenther wrote:
>> This patch does the same thing for (nearly) all other relevant calls to
>> bitmap_bit_p. I might have missed a couple and I think there were one
>> or two that looked particularly tricky to untangle, so I left them
>> as-is.
>>
>> Tested on x86_64-unknown-linux-gnu. OK to commit?
>
> Ok.
I like this patch just for the fact that it simplifies use of the API,
in addition to the fact that it should theoretically be a bit faster.
Out of curiosity, did you measure any speedup?
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2010-08-19 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 16:24 Nathan Froyd
2010-08-19 16:53 ` Richard Guenther
2010-08-19 20:05 ` Mark Mitchell [this message]
2010-08-19 21:30 ` Nathan Froyd
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=4C6D8B5A.9050007@codesourcery.com \
--to=mark@codesourcery.com \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).