mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: Multi-threaded performance progress
Date: Tue, 26 Aug 2014 13:09:25 +0200	[thread overview]
Message-ID: <1409051365.8054.19.camel@eris.loria.fr> (raw)
In-Reply-To: <20140826104433.GW22308@port70.net>

[-- Attachment #1: Type: text/plain, Size: 2321 bytes --]

Hello,

Am Dienstag, den 26.08.2014, 12:44 +0200 schrieb Szabolcs Nagy:
> * Jens Gustedt <jens.gustedt@inria.fr> [2014-08-26 09:04:14 +0200]:
> >  - one or two simple functions, such as the timespec_get that I posted
> >  - if we don't have C11 threads the feature test macro __STDC NO_THREAD__
> >  - perhaps some other feature test macros for unsupported features
> 
> further missing c11 things:
> 
> time.h needs TIME_UTC for timespec_get base parameter

I had that in my patch for timespec_get, too. This would perhaps need
some short discussion for the policy to apply.

It would be nice to propose all the POSIX clocks that musl implements
as extensions. That is explicitly allowed by C. Unfortunately the
constraint from C11 is that the TIME_XXX values can't be 0, so the
current CLOCK_XXX values don't work and we'd have to translate.

I had chosen the easy way, any TIME value is interpreted as
CLOCK_REALTIME, and that value is just echoed as return value of the
function.

> stdalign.h should only define alignas and alignof ifndef c++
> assert.h needs static_assert ifndef c++
> float.h needs *_DECIMAL_DIG and *_HAS_SUBNORM (i have a patch for this)
> uchar.h

ah, yes, this is probably still a bit of work to do

> stdatomic.h (or __STDC_NO_ATOMICS__)

Not necessarily, this is primarily a compiler feature and not a
library feature. With gcc 4.9 this works. (Well, with some hickups,
because they use POSIX lock features under the hood in libatomic,
instead of implementing them properly with atomic_flag.)

gcc version before that don't have sufficient C11 support, anyhow. In
particular I think that _Generic is only implemented from 4.9 onward.

On a longer term, we could think of replacing libatomic calls, too,
but this isn't urgent at all.

> (thread_local, alignas, alignof, static_assert, noreturn are keywords
> in c++, stdnoreturn.h is not specified by c++14 so that probably does
> not need the ifndef but the others do)

right

Jens


-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-08-26 11:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  3:43 Rich Felker
2014-08-26  7:04 ` Jens Gustedt
2014-08-26 10:44   ` Szabolcs Nagy
2014-08-26 11:09     ` Jens Gustedt [this message]
2014-08-26 16:35   ` Jens Gustedt
2014-08-26 17:32     ` Rich Felker
2014-08-26 17:53     ` Rich Felker
2014-08-26 18:30       ` Jens Gustedt
2014-08-26 19:05         ` Rich Felker
2014-08-26 19:34           ` Jens Gustedt
2014-08-26 20:26             ` Rich Felker
2014-08-26 21:15               ` Jens Gustedt
2014-08-26 21:36                 ` Rich Felker
2014-08-27  9:53                   ` Jens Gustedt
2014-08-27 16:47                     ` Rich Felker

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=1409051365.8054.19.camel@eris.loria.fr \
    --to=jens.gustedt@inria.fr \
    --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).