All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Artem_Mygaiev@epam.com, xen-devel@lists.xenproject.org,
	Andrii_Anisov@epam.com, Oleksandr_Tyshchenko@epam.com
Subject: Re: [PATCH 07/12] xen/arm: cpuerrata: Match register size with value size in check_workaround_*
Date: Thu, 18 Apr 2019 20:01:44 +0100	[thread overview]
Message-ID: <5414f6ea-b776-3dfa-682a-d6b63bf2374f@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1904181148300.1370@sstabellini-ThinkPad-X260>



On 18/04/2019 19:52, Stefano Stabellini wrote:
> On Thu, 18 Apr 2019, Julien Grall wrote:
>> On 18/04/2019 19:23, Stefano Stabellini wrote:
>>> On Wed, 17 Apr 2019, Julien Grall wrote:
>>>> On 4/17/19 9:28 PM, Stefano Stabellini wrote:
>>>>> On Wed, 27 Mar 2019, Julien Grall wrote:
>> If it is considered compliant, then it does not make sense.
> 
> Yes, I think this is not compliant too. Also, from what I have been
> told, this example is famous for being one of the most extreme examples
> of MISRA-C non-compliance. I think the compliant version would be:
> 
> bool is_nonzero(int b)
> {
>      if (b != 0)
>        return true;
>      else
>        return false;
> }
> 
> This is also compliant:
> 
> bool is_nonzero(int b)
> {
>      return (b != 0);
> }
> 

I will use !!b here and in the next patch. But I still doubt you will be able to 
enforce it in Xen. if ( n ) is quite a common pattern.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Artem_Mygaiev@epam.com, xen-devel@lists.xenproject.org,
	Andrii_Anisov@epam.com, Oleksandr_Tyshchenko@epam.com
Subject: Re: [Xen-devel] [PATCH 07/12] xen/arm: cpuerrata: Match register size with value size in check_workaround_*
Date: Thu, 18 Apr 2019 20:01:44 +0100	[thread overview]
Message-ID: <5414f6ea-b776-3dfa-682a-d6b63bf2374f@arm.com> (raw)
Message-ID: <20190418190144.hRpaxUQ3J22CvTdAcpQgrU0emcfztu_Qnx4pKuj87Pg@z> (raw)
In-Reply-To: <alpine.DEB.2.10.1904181148300.1370@sstabellini-ThinkPad-X260>



On 18/04/2019 19:52, Stefano Stabellini wrote:
> On Thu, 18 Apr 2019, Julien Grall wrote:
>> On 18/04/2019 19:23, Stefano Stabellini wrote:
>>> On Wed, 17 Apr 2019, Julien Grall wrote:
>>>> On 4/17/19 9:28 PM, Stefano Stabellini wrote:
>>>>> On Wed, 27 Mar 2019, Julien Grall wrote:
>> If it is considered compliant, then it does not make sense.
> 
> Yes, I think this is not compliant too. Also, from what I have been
> told, this example is famous for being one of the most extreme examples
> of MISRA-C non-compliance. I think the compliant version would be:
> 
> bool is_nonzero(int b)
> {
>      if (b != 0)
>        return true;
>      else
>        return false;
> }
> 
> This is also compliant:
> 
> bool is_nonzero(int b)
> {
>      return (b != 0);
> }
> 

I will use !!b here and in the next patch. But I still doubt you will be able to 
enforce it in Xen. if ( n ) is quite a common pattern.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-04-18 19:01 UTC|newest]

Thread overview: 104+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 18:45 [PATCH 00/12] xen/arm: Add support to build with clang Julien Grall
2019-03-27 18:45 ` [PATCH 01/12] xen: clang: Support correctly cross-compile Julien Grall
2019-03-28  9:55   ` Jan Beulich
2019-03-28 10:14     ` Andrew Cooper
2019-03-28 10:28       ` Jan Beulich
2019-03-28 10:43         ` Andrew Cooper
2019-03-28 10:56           ` Jan Beulich
2019-03-29 10:09             ` Julien Grall
2019-03-29  9:41     ` Julien Grall
2019-03-29 10:14       ` Jan Beulich
2019-04-19 18:47         ` Stefano Stabellini
2019-04-19 18:47           ` [Xen-devel] " Stefano Stabellini
2019-04-24 20:18           ` Julien Grall
2019-04-24 20:18             ` [Xen-devel] " Julien Grall
2019-03-27 18:45 ` [PATCH 02/12] xen/arm: fix get_cpu_info() when built with clang Julien Grall
2019-04-17 20:45   ` Stefano Stabellini
2019-04-17 20:45     ` [Xen-devel] " Stefano Stabellini
2019-04-17 21:00     ` Julien Grall
2019-04-17 21:00       ` [Xen-devel] " Julien Grall
2019-04-18 18:03       ` Stefano Stabellini
2019-04-18 18:03         ` [Xen-devel] " Stefano Stabellini
2019-09-29 14:26         ` Julien Grall
2019-10-01  1:15           ` Stefano Stabellini
2019-10-01  1:22             ` Stefano Stabellini
2019-10-01  9:49               ` Julien Grall
2019-10-01  9:47             ` Julien Grall
2019-03-27 18:45 ` [PATCH 03/12] xen/arm: zynqmp: Fix header guard for xilinx-zynqmp-eemi.h Julien Grall
2019-04-17 20:20   ` Stefano Stabellini
2019-04-17 20:20     ` [Xen-devel] " Stefano Stabellini
2019-03-27 18:45 ` [PATCH 04/12] xen/arm: memaccess: Initialize correctly *access in __p2m_get_mem_access Julien Grall
2019-03-27 19:08   ` Razvan Cojocaru
2019-03-27 18:45 ` [PATCH 05/12] xen/arm64: bitops: Match the register size with the value size in flsl Julien Grall
2019-03-27 19:03   ` Andrew Cooper
2019-03-27 20:13     ` Julien Grall
2019-04-17 20:24       ` Stefano Stabellini
2019-04-17 20:24         ` [Xen-devel] " Stefano Stabellini
2019-04-17 21:02         ` Julien Grall
2019-04-17 21:02           ` [Xen-devel] " Julien Grall
2019-04-18 18:40           ` Stefano Stabellini
2019-04-18 18:40             ` [Xen-devel] " Stefano Stabellini
2019-04-18 18:57             ` Julien Grall
2019-04-18 18:57               ` [Xen-devel] " Julien Grall
2019-04-18 19:00               ` Stefano Stabellini
2019-04-18 19:00                 ` [Xen-devel] " Stefano Stabellini
2019-03-27 18:45 ` [PATCH 06/12] xen/arm64: sysreg: Implement the 32-bit helpers using the 64-bit helpers Julien Grall
2019-03-27 19:15   ` Andrew Cooper
2019-03-27 20:21     ` Julien Grall
2019-04-17 20:26   ` Stefano Stabellini
2019-04-17 20:26     ` [Xen-devel] " Stefano Stabellini
2019-03-27 18:45 ` [PATCH 07/12] xen/arm: cpuerrata: Match register size with value size in check_workaround_* Julien Grall
2019-04-17 20:28   ` Stefano Stabellini
2019-04-17 20:28     ` [Xen-devel] " Stefano Stabellini
2019-04-17 21:15     ` Julien Grall
2019-04-17 21:15       ` [Xen-devel] " Julien Grall
2019-04-18 18:23       ` Stefano Stabellini
2019-04-18 18:23         ` [Xen-devel] " Stefano Stabellini
2019-04-18 18:47         ` Julien Grall
2019-04-18 18:47           ` [Xen-devel] " Julien Grall
2019-04-18 18:52           ` Stefano Stabellini
2019-04-18 18:52             ` [Xen-devel] " Stefano Stabellini
2019-04-18 19:01             ` Julien Grall [this message]
2019-04-18 19:01               ` Julien Grall
2019-04-18 19:04               ` Stefano Stabellini
2019-04-18 19:04                 ` [Xen-devel] " Stefano Stabellini
2019-03-27 18:45 ` [PATCH 08/12] xen/arm: cpufeature: Match register size with value size in cpus_have_const_cap Julien Grall
2019-04-17 20:29   ` Stefano Stabellini
2019-04-17 20:29     ` [Xen-devel] " Stefano Stabellini
2019-04-17 21:16     ` Julien Grall
2019-04-17 21:16       ` [Xen-devel] " Julien Grall
2019-03-27 18:45 ` [PATCH 09/12] xen/arm: guest_walk: Avoid theoritical unitialized value in get_top_bit Julien Grall
2019-04-17 20:31   ` Stefano Stabellini
2019-04-17 20:31     ` [Xen-devel] " Stefano Stabellini
2019-03-27 18:45 ` [PATCH 10/12] xen/arm: mm: Mark check_memory_layout_alignment_constraints as unused Julien Grall
2019-03-27 19:10   ` Andrew Cooper
2019-04-09 12:09     ` Julien Grall
2019-04-09 12:09       ` [Xen-devel] " Julien Grall
2019-03-27 18:45 ` [PATCH 11/12] xen/arm: traps: Mark check_stack_alignment_constraints " Julien Grall
2019-03-27 18:45 ` [PATCH 12/12] xen/arm64: __cmpxchg and __cmpxchg_mb should always be inline Julien Grall
2019-04-17 20:35   ` Stefano Stabellini
2019-04-17 20:35     ` [Xen-devel] " Stefano Stabellini
2019-03-28 11:27 ` [PATCH 00/12] xen/arm: Add support to build with clang Artem Mygaiev
2019-03-29 10:13   ` Julien Grall
2019-04-16 22:43     ` Stefano Stabellini
2019-04-16 22:43       ` [Xen-devel] " Stefano Stabellini
2019-04-17  9:42       ` Julien Grall
2019-04-17  9:42         ` [Xen-devel] " Julien Grall
2019-04-18  9:15         ` Artem Mygaiev
2019-04-18  9:15           ` [Xen-devel] " Artem Mygaiev
2019-04-18 10:43           ` Julien Grall
2019-04-18 10:43             ` [Xen-devel] " Julien Grall
2019-04-18 11:15             ` Artem Mygaiev
2019-04-18 11:15               ` [Xen-devel] " Artem Mygaiev
2019-04-18 18:33               ` Julien Grall
2019-04-18 18:33                 ` [Xen-devel] " Julien Grall
2019-04-23 13:39                 ` Artem Mygaiev
2019-04-23 13:39                   ` [Xen-devel] " Artem Mygaiev
2019-04-24 21:07                   ` Julien Grall
2019-04-24 21:07                     ` [Xen-devel] " Julien Grall
2019-04-25  3:31                     ` Artem Mygaiev
2019-04-25  3:31                       ` [Xen-devel] " Artem Mygaiev
2019-04-24 11:01                 ` Roger Pau Monné
2019-04-24 11:01                   ` [Xen-devel] " Roger Pau Monné
2019-04-18 11:13 ` Julien Grall
2019-04-18 11:13   ` [Xen-devel] " Julien Grall

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=5414f6ea-b776-3dfa-682a-d6b63bf2374f@arm.com \
    --to=julien.grall@arm.com \
    --cc=Andrii_Anisov@epam.com \
    --cc=Artem_Mygaiev@epam.com \
    --cc=Oleksandr_Tyshchenko@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.