xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] tools/ia64: Cull more ia64 code
Date: Tue, 13 Aug 2013 14:13:28 +0100	[thread overview]
Message-ID: <520A30F8.1070707@citrix.com> (raw)
In-Reply-To: <520A4C3C02000078000EB8A0@nat28.tlf.novell.com>

On 13/08/13 14:09, Jan Beulich wrote:
>>>> On 13.08.13 at 15:00, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> --- a/tools/libfsimage/common/fsimage_grub.c
>> +++ b/tools/libfsimage/common/fsimage_grub.c
>> @@ -138,28 +138,6 @@ fsig_log2 (unsigned long word)
>>    return word;
>>  }
>>  
>> -#elif defined(__ia64__)
>> -
>> -#if __GNUC__ >= 4 || (__GNUC__ == 3 && __GNUC_MINOR__ >= 4)
>> -# define ia64_popcnt(x) __builtin_popcountl(x)
>> -#else
>> -# define ia64_popcnt(x)                                     \
>> -  ({                                                        \
>> -    uint64_t ia64_intri_res;                                \
>> -    asm ("popcnt %0=%1" : "=r" (ia64_intri_res) : "r" (x)); \
>> -    ia64_intri_res;                                         \
>> -  })
>> -#endif
>> -
>> -unsigned long
>> -fsig_log2 (unsigned long word)
>> -{
>> -  unsigned long result;
>> -
>> -  result = ia64_popcnt((word - 1) & ~word);
>> -  return result;
>> -}
>> -
>>  #elif defined(__powerpc__)
>>  
>>  #ifdef __powerpc64__
> Why not rip out the PPC stuff here at once?
>
> Jan
>

Can do - this appears to be the only ppc which can be ripped out.  v2 on
its way

~Andrew

      reply	other threads:[~2013-08-13 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 13:00 [PATCH] tools/ia64: Cull more ia64 code Andrew Cooper
2013-08-13 13:09 ` Jan Beulich
2013-08-13 13:13   ` Andrew Cooper [this message]

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=520A30F8.1070707@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).