public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] Cygwin: Make gcc-specific code in <sys/cpuset.h> compiler-agnostic
Date: Fri, 7 Jul 2023 16:46:24 +0100	[thread overview]
Message-ID: <8bc70b04-7c0b-15de-b090-e2f38c424dd9@dronecode.org.uk> (raw)
In-Reply-To: <ZKfeaMftPy8HmXyy@calimero.vinschen.de>

On 07/07/2023 10:44, Corinna Vinschen wrote:
> Hi Mark,
> 
> On Jul  7 00:41, Mark Geisert wrote:
>> The current version of <sys/cpuset.h> cannot be compiled by Clang due to
>> the use of __builtin* functions.  Their presence here was a dubious
>> optimization anyway, so their usage has been converted to standard
>> library functions.  A popcnt (population count of 1 bits in a word)
>> function is provided here because there isn't one in the standard library
>> or elsewhere in the Cygwin DLL.
> 
> And clang really doesn't provide it?  That's unfortunate.

I suspect if we had a current clang this would not be a problem.

There's probably something to be said for solving this problem by 
removing our old and unmaintained clang packages...


  parent reply	other threads:[~2023-07-07 15:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  7:41 Mark Geisert
2023-07-07  9:44 ` Corinna Vinschen
2023-07-07 10:13   ` Mark Geisert
2023-07-07 10:45     ` Corinna Vinschen
2023-07-07 15:46   ` Jon Turney [this message]
2023-07-07 15:49     ` Corinna Vinschen
2023-07-07 18:54   ` Brian Inglis
2023-07-08 19:22     ` Brian Inglis
2023-07-08 20:59       ` Mark Geisert
2023-07-08 21:53         ` Mark Geisert
2023-07-09  4:27           ` Brian Inglis
2023-07-09  7:58             ` Mark Geisert

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=8bc70b04-7c0b-15de-b090-e2f38c424dd9@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-patches@cygwin.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).