public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Mark Geisert <mark@maxrnd.com>
Cc: Marco Atzeri <marco.atzeri@gmail.com>, cygwin@cygwin.com
Subject: Re: type mismatch on cpuset.h
Date: Mon, 6 Mar 2023 09:55:52 +0100	[thread overview]
Message-ID: <ZAWqmGwaqbDtwNF8@calimero.vinschen.de> (raw)
In-Reply-To: <41f9bb68-d5e0-58d7-701f-a84b9db6b9a9@gmail.com>

Hi Mark,

On Mar  6 07:57, Marco Atzeri via Cygwin wrote:
> Hi,
> 
> building latest gdal I noticed a type mismatch, that forced me to build
> with "-fpermissive"
> 
> on /usr/include/sys/cpuset.h
> 
>  #define CPU_ALLOC(num)      __builtin_malloc (CPU_ALLOC_SIZE(num))
> 
> 
> but on
> https://linux.die.net/man/3/cpu_alloc
> 
>  cpu_set_t *CPU_ALLOC(int num_cpus)
> 
> 
> so void* versus cpu_set_t*

Marco is correct.  cpuset.h was your pet project a while back.  Would
you like to pick it up?  Maybe we should convert all the macros into
type-safe inline functions, or macros calling type-safe (inline)
functions, as on Linux as well as on BSD?


Thanks,
Corinna

  reply	other threads:[~2023-03-06  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06  6:57 Marco Atzeri
2023-03-06  8:55 ` Corinna Vinschen [this message]
2023-03-06  9:14   ` 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=ZAWqmGwaqbDtwNF8@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    --cc=mark@maxrnd.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).