From: Zack Weinberg <zack@codesourcery.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org, apinski@apple.com
Subject: Re: speeding up parts of gcc by using ffs
Date: Mon, 06 Jan 2003 18:08:00 -0000 [thread overview]
Message-ID: <87ptraf9sp.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <448174DB-2155-11D7-983A-000393A6D2F2@physics.uc.edu> (Andrew Pinski's message of "Mon, 6 Jan 2003 01:00:13 -0800")
Andrew Pinski <pinskia@physics.uc.edu> writes:
> A follow of the comments I received, I have only right now added the
> simple cases of HOST_BITS_PER_WIDE_INT == HOST_BITS_PER_INT and
> HOST_BITS_PER_INT == HOST_BITS_PER_LONG. I might implement the other
> part of the patch for when HOST_BITS_PER_WIDE_INT ==
> HOST_BITS_PER_LONG_LONG and HOST_BITS_PER_WIDE_INT ==
> HOST_BITS_PER_LONG but this might take some time because I have to add
> some more builtins but it will clean things up.
I'm not enthusiastic about all the #ifdefs.
glibc provides ffsl and ffsll which take 'long' and 'long long'
respectively; may I suggest that you follow these steps:
1) put ffsl and ffsll into libiberty.
2) have hwint.h #define ffs_hwi and ffs_hwidesti appropriately
3) use ffs/ffsl/ffsll/ffs_hwi throughout the compiler
4) create __builtin_ffsl and __builtin_ffsll
zw
next prev parent reply other threads:[~2003-01-06 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 6:16 speeding up parts of gcc by using count_leading_zero (long) Andrew Pinski
2003-01-05 7:03 ` Zack Weinberg
2003-01-05 7:17 ` Peter Barada
2003-01-05 8:41 ` Zack Weinberg
2003-01-06 10:51 ` speeding up parts of gcc by using ffs Andrew Pinski
2003-01-06 18:08 ` Zack Weinberg [this message]
2003-01-06 18:28 ` Joseph S. Myers
2003-01-08 9:51 ` Andrew Pinski
2003-01-08 11:20 ` Falk Hueffner
2003-01-08 11:21 ` Andrew Pinski
2003-01-08 11:26 ` Falk Hueffner
2003-01-09 0:24 ` Richard Henderson
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=87ptraf9sp.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=apinski@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
/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).