All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>,
	Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] [Xenomai-git] Jan Kiszka : alchemy: Replace static variable no_alchemy_task with macro
Date: Wed, 05 Feb 2014 11:28:10 +0100	[thread overview]
Message-ID: <52F2123A.2070607@siemens.com> (raw)
In-Reply-To: <52F20E32.3010706@xenomai.org>

On 2014-02-05 11:10, Philippe Gerum wrote:
> On 02/05/2014 10:42 AM, Jan Kiszka wrote:
>> So you just want me to fold patch 2 and 3 together? I don't fully get it
>> yet.
> 
> I'm asking for a clarification: do you have more patches following these
> two? I understood from the past conversation that more work was
> required, so I'm assuming you will have. If so, then we may save a lot
> of time by seeing the complete change set that would fit the bill for
> supporting standard C/C++ restrictions, the way your current port work
> seems to require it.

I'm not aware of further issues after the __typeof__ thing. However, I
will try to run through all public headers in an automated way,
including them in strict modes to check if there is something remaining.
Maybe we can also hook this into our build tests here.

> 
>>
>>>
>>>>
>>>> The no_alchemy_task thing is not a dialect issue, so I think it's clear
>>>> now.
>>>
>>> This issue is only relevant to how smart the compiler you use is with
>>> respect to optimizing the output, when it sees a statically-scoped
>>> variable which is explicitly read-only.
>>
>> Right, so one of the issue it causes has nothing to do with [strict] C++
>> compliance.
> 
> Which is the reason why I tend to suspect patches claiming about fixing
> some perceived ugliness, factual information is better. This construct
> is valid, but does not fit well with the gcc release you are aiming at,
> which is another issue. Xenomai 3.x does impose minimum requirements on
> the compiler/toolchain, including sane/working support of builtin sync
> primitives and tls.
> 
> In this respect, your patch about no_alchemy_task would have been better
> explained by the goal of not depending on too recent optimizers, which
> does make sense to me. The language is important so that my limited
> mono-neuronal brain can deal with your commit logs.

OK, will do /s/ugliness/objective reason for ugliness/.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2014-02-05 10:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1WAhle-0006kB-0q@sd-51317.dedibox.fr>
2014-02-04 15:22 ` [Xenomai] [Xenomai-git] Jan Kiszka : alchemy: Replace static variable no_alchemy_task with macro Gilles Chanteperdrix
2014-02-04 16:36 ` Philippe Gerum
2014-02-04 17:12   ` Jan Kiszka
2014-02-04 17:27     ` Philippe Gerum
2014-02-04 17:32       ` Gilles Chanteperdrix
2014-02-04 17:35         ` Jan Kiszka
2014-02-04 17:39           ` Gilles Chanteperdrix
2014-02-04 17:39         ` Philippe Gerum
2014-02-04 17:44           ` Gilles Chanteperdrix
2014-02-04 17:46             ` Jan Kiszka
2014-02-04 17:48             ` Philippe Gerum
2014-02-04 17:53               ` Philippe Gerum
2014-02-04 18:03                 ` Jan Kiszka
2014-02-04 18:20                   ` Jan Kiszka
2014-02-04 18:26                     ` Gilles Chanteperdrix
2014-02-04 18:35                       ` Jan Kiszka
2014-02-05  9:07                         ` Philippe Gerum
2014-02-05  8:33                   ` Philippe Gerum
2014-02-05  8:49                     ` Jan Kiszka
2014-02-05  8:58                       ` Philippe Gerum
2014-02-05  9:06                         ` Jan Kiszka
2014-02-05  9:36                           ` Philippe Gerum
2014-02-05  9:42                             ` Jan Kiszka
2014-02-05 10:10                               ` Philippe Gerum
2014-02-05 10:28                                 ` Jan Kiszka [this message]
2014-02-06 15:24                                   ` Jan Kiszka
2014-02-05  7:30               ` dietmar.schindler
2014-02-04 17:31     ` Gilles Chanteperdrix
2014-02-04 17:35       ` Philippe Gerum

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=52F2123A.2070607@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.