unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Llorens <daniel.llorens@bluewin.ch>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Patchset related to array functions
Date: Wed, 31 Aug 2016 13:36:56 +0200	[thread overview]
Message-ID: <63395AE2-FE6B-4D2D-AD69-43EA68FB32A3@bluewin.ch> (raw)
In-Reply-To: <87oa49jmok.fsf@pobox.com>


On 31 Aug 2016, at 11:46, Andy Wingo <wingo@pobox.com> wrote:

> On Wed 31 Aug 2016 11:28, Andy Wingo <wingo@pobox.com> writes:
> 
>> On Thu 14 Jul 2016 20:20, Andy Wingo <wingo@pobox.com> writes:
>> 
>>> I think the concerns are:
>>> 
>>> (1) Do inlined definitions get inlined?
>>> (2) Are external definitions reified as well?
>>> (3) Do we avoid reifying definitions in each compilation unit?
>>> (4) Can you dlsym() an inline function?
>>> 
>>> All these answers should be yes.  No benchmarking needed, just
>>> inspection of the build artifacts under different configurations.
>> 
>> I want to be able to use C11 atomics in Guile, internally.  I think
>> externally as far as the interface goes we can probably upgrade to C99
>> given that even Emacs uses it these days.  I will try to answer these
>> four questions with GCC with C89 and C99, and if the answers are good I
>> will upgrade to C99 first, for the build.
> 
> Hah!  Turns out we have been compiling in GCC's default mode the whole
> time, which is gnu11.  I suspect many users have been doing that too.
> We might as well go ahead and require C99 internally plus the C11
> features we want.  Again for the external interface (stdint.h et al) we
> can also probably require C99 for Guile 2.2, so that we can use uint32_t
> and not scm_t_uint32.
> 
> Andy

Hi,

I've sent a patch to use C99 inline in a separate email. It's kind of obvious, but let me know if it makes sense (or not) and I'll write a proper commit message. 

Regards

	Daniel


  reply	other threads:[~2016-08-31 11:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12  7:48 Patchset related to array functions Daniel Llorens
2016-07-12 14:11 ` Andy Wingo
2016-07-12 17:16   ` Daniel Llorens
2016-07-14  9:46     ` Andy Wingo
2016-07-14 15:41       ` [PATCH] " Daniel Llorens
2016-07-14 18:20         ` Andy Wingo
2016-07-15 12:54           ` [PATCH] " Daniel Llorens
2016-08-31  9:28           ` [PATCH] " Andy Wingo
2016-08-31  9:46             ` Andy Wingo
2016-08-31 11:36               ` Daniel Llorens [this message]
2016-08-31 14:45               ` Eli Zaretskii
2016-07-15 10:52         ` Chris Vine
2016-07-16  9:07           ` Andy Wingo
2016-07-16 10:34             ` Chris Vine
2016-07-15 17:41       ` Mark H Weaver
2016-07-16  8:30         ` Andy Wingo

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63395AE2-FE6B-4D2D-AD69-43EA68FB32A3@bluewin.ch \
    --to=daniel.llorens@bluewin.ch \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).