From: Jakub Jelinek <jakub@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>,
Richard Henderson <rth@redhat.com>,
Steven Munroe <munroesj@us.ibm.com>
Subject: Re: [PATCH] Optimized __sched_cpucount for alphaev67, power5 and above and ia64
Date: Wed, 18 Jul 2007 09:01:00 -0000 [thread overview]
Message-ID: <20070718090457.GZ4603@sunsite.mff.cuni.cz> (raw)
In-Reply-To: <20070717205304.EE29B4D05CF@magilla.localdomain>
On Tue, Jul 17, 2007 at 01:53:04PM -0700, Roland McGrath wrote:
> Seems like this might come up somewhere else. I'd be inclined to add a
> sysdeps header file for POPCNT alone (or rename it).
Maybe, though I'm not sure if we need one sysdep header for each such a
macro, that might be an overkill.
Jakub
next prev parent reply other threads:[~2007-07-18 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 20:43 Jakub Jelinek
2007-07-17 20:53 ` Roland McGrath
2007-07-18 9:01 ` Jakub Jelinek [this message]
2007-07-18 9:05 ` Roland McGrath
2007-07-18 14:52 ` Ulrich Drepper
2007-07-18 16:17 ` Richard Henderson
2007-07-19 17:26 ` Ulrich Drepper
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=20070718090457.GZ4603@sunsite.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=munroesj@us.ibm.com \
--cc=roland@redhat.com \
--cc=rth@redhat.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).