mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Morten Welinder <mwelinder@gmail.com>
To: musl@lists.openwall.com
Subject: Re: C11 threads
Date: Fri, 25 Jul 2014 09:42:52 -0400	[thread overview]
Message-ID: <CANv4PNmLoAgpz=a68TPikteiSJvE1WdP6tkaFd89i-gufL5vpg@mail.gmail.com> (raw)
In-Reply-To: <20140725130438.GA10402@port70.net>

> the musl math library currently defines distinct long double [...]

You cannot compare a "double" function pointer to a "long double"
function pointer.  The types are incompatible, even if they have the
same representation.

Hence I don't believe a C program can even tell if they are the same.

M.





On Fri, Jul 25, 2014 at 9:04 AM, Szabolcs Nagy <nsz@port70.net> wrote:
> * Jens Gustedt <jens.gustedt@inria.fr> [2014-07-25 13:06:44 +0200]:
>> Am Freitag, den 25.07.2014, 12:40 +0200 schrieb Szabolcs Nagy:
>> > * Jens Gustedt <jens.gustedt@inria.fr> [2014-07-25 12:00:37 +0200]:
>> > > /* Best of all worlds, these are just weak aliases */
>> > > int cnd_broadcast(cnd_t *);                   // pthread_cond_broadcast
>> >
>> > posix is not yet aligned with c11, but i think they will
>> > require inequal function pointers for these functions
>>
>> The term "inequal function pointer" had nothing pop up. Could you give
>> a reference to the relevant part in POSIX that makes the requirement
>> for a "strong" symbol?
>
>
> hm i might be wrong:
>
> there is a requirement in c and posix that the address of a
> standard function can be taken and that == is only true for
> function pointers if they point to the same function
>
> but i don't see any requirement that each library function
> must be distinct
>
> and there is a dr that implies the opposite:
>
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_078.html
>
> without explanation the response says h can return 0.
>
> the musl math library currently defines distinct long double
> functions even if long double and double have the same
> representation, they could be weak aliases if the standard
> allows this..


  parent reply	other threads:[~2014-07-25 13:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 10:00 Jens Gustedt
2014-07-25 10:40 ` Szabolcs Nagy
2014-07-25 11:06   ` Jens Gustedt
2014-07-25 13:04     ` Szabolcs Nagy
2014-07-25 13:38       ` Jens Gustedt
2014-07-25 13:42       ` Morten Welinder [this message]
2014-07-25 14:15         ` Szabolcs Nagy
2014-07-25 16:14       ` Rich Felker
2014-07-25 21:59         ` Jens Gustedt
2014-07-25 22:25           ` Rich Felker
2014-07-25 15:41     ` Rich Felker
2014-07-25 17:10       ` Jens Gustedt
2014-07-25 22:19         ` Rich Felker
2014-07-25 23:26           ` Jens Gustedt
2014-07-26  2:24             ` Rich Felker
2014-07-26  7:16               ` Jens Gustedt
2014-07-26  7:35                 ` Rich Felker
2014-07-26  8:32                   ` Jens Gustedt
2014-07-26  9:03                     ` Rich Felker
2014-07-26 11:15                       ` Jens Gustedt
2014-07-26 15:48                 ` Jens Gustedt

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='CANv4PNmLoAgpz=a68TPikteiSJvE1WdP6tkaFd89i-gufL5vpg@mail.gmail.com' \
    --to=mwelinder@gmail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).