Autosar Guidelines C++14, example code compile list(33)Rule A5-0-2 The condition of an if-statement


Guidelines for the use of the C++14 language in critical and
safety-related systems Sample code compile list(33)
https://www.autosar.org/fileadmin/user_upload/standards/adaptive/17-03/AUTOSAR_RS_CPP14Guidelines.pdf

Autosar Guidelines C++14 example code compile list
https://qiita.com/kaizen_nagoya/items/8ccbf6675c3494d57a76

目的(purpose)

AutosarのC++ GuidelineをOS, 制御のプログラムで利用するにあたって、(1)hosted, freestandingのどちらを基本にすべきか。(2)C++2014,C++2017, C++202aのどれを用いると良いか, (3)どの処理系を併用すると良いかを検討するため、-std=c++14, -std=c++17, -std=c++2aの3種類で、複数のコンパイラでコンパイルすることにより、誤(error)、警告(warning)、関数・変数連携(link)、出力(output)、にどのような影響があるかを確認する。

成果(outcome)

複数の処理系の特徴が明確になるとともに、各標準段階, hosted, freestandingの特徴と課題を明確にする。

A5-0-2.cpp

算譜(source code)

A5-0-2.cpp
//Guidelines for the use of the C++14 language in critical and safety-related systems
const char* msg="Rule A5-0-2 (required, implementation, automated)The condition of an if-statement and the condition of an iteration statementshall have type bool.(33)A5-0-2.cpp";
//https://www.autosar.org/fileadmin/user_upload/standards/adaptive/17-03/AUTOSAR_RS_CPP14Guidelines.pdf
// There is no description about Autosar declear hosted or freestanding.
// If the Autosar intended both depending on the cases, autosar.h can choose one.
// Compile with -DHOSTED work as  hosted environment, -DFREESTANDING work as freestanding.

#include "autosar.h"/// @line add header file https://qiita.com/kaizen_nagoya/items/4bde8f21ab059b96cf2a
#include <cstdint>


using namespace std;/// @line add using

///start AUTOSAR: From here to the "///end AUTOSAR" is from AUTOSAR without code having /// comment in line.
// $Id: A5-0-2.cpp 271927 2017-03-24 12:01:35Z piotr.tanski $
#include <cstdint>
#include <memory>
extern std::int32_t* fn();
extern std::int32_t fn2();
extern bool fn3();
void f() noexcept(false)
{
  std::int32_t* ptr = nullptr;

  while ((ptr = fn()) != nullptr) // Compliant
  {
// Code
  }

// The following is a cumbersome but compliant example
  do
  {
    std::int32_t* ptr = fn();

    if (nullptr == ptr)
    {
      break;
    }

// Code
  } while (true); // Compliant

  std::unique_ptr<std::int32_t> uptr;
  if (!uptr) // Compliant - std::unique_ptr defines an explicit conversion to
// type bool.
  {
// Code
  }

  while (std::int32_t length = fn2()) // Compliant by exception
  {
// Code
  }

  while (bool flag = fn3()) // Compliant
  {
// Code
  }

  if (std::int32_t* ptr = fn())
    ; // Compliant by exception

  if (std::int32_t length = fn2())
    ; // Compliant by exception

  if (bool flag = fn3())
    ; // Compliant

  std::uint8_t u = 8;

  if (u)
    ; // Non-compliant

  bool boolean1 = false;
  bool boolean2 = true;

  if (u && (boolean1 <= boolean2))
    ; // Non-compliant

  for (std::int32_t x = 10; x; --x)
    ; // Non-compliant
}
///end AUTOSAR
int start() { /// @{} for start
  fn();
  cout<< msg << endl;
  ShutdownOS()  EXIT_SUCCESS;
/// Autosar OS 3.1.1, 2009: 7.1.2.2 Undefined Behaviour in OSEK OS
/// OS425 If ShutdownOS is called and ShutdownHook() returns then the operating system shall disable all interrupts and enter an endless loop.
}
a5-0-2a.cpp
#include "autosar.h"/// @line add header file https://qiita.com/kaizen_nagoya/items/4bde8f21ab059b96cf2a
using namespace std;/// @line add using

int32_t i=256;

int32_t* fn() {
  int32_t* ip=&i;
  cout <<"ip="<<ip<<endl;
  return ip;
}
int32_t fn2() {
  cout <<"i="<<i<<endl;
  return i;
}
bool fn3() {
  cout<<"fn3:bool"<<(i>0) <<endl;
  return (i>0);
}

編纂・実行結果(compile and go)

cpa.sh
$ ../cpa2.sh a5-0-2 a5-0-2a 
$ clang++ a5-0-2.cpp a5-0-2a.cpp  -std=c++14 -Wall
ip=0x10a0c9100
Rule A5-0-2 (required, implementation, automated)The condition of an if-statement and the condition of an iteration statementshall have type bool.(32)A5-0-2.cpp
rm: a5-0-2l13: No such file or directory
$ clang++ a5-0-2.cpp  a5-0-2a.cpp  -std=c++17 -Wall
ip=0x10c0e3100
Rule A5-0-2 (required, implementation, automated)The condition of an if-statement and the condition of an iteration statementshall have type bool.(32)A5-0-2.cpp
$ clang++ a5-0-2.cpp  a5-0-2a.cpp  -std=c++2a -Wall
ip=0x1072c1100
Rule A5-0-2 (required, implementation, automated)The condition of an if-statement and the condition of an iteration statementshall have type bool.(32)A5-0-2.cpp

$ g++-8 a5-0-2.cpp a5-0-2a.cpp  -std=c++14  -Wall
a5-0-2.cpp: In function 'void f()':
a5-0-2.cpp:50:22: warning: unused variable 'length' [-Wunused-variable]
  while (std::int32_t length = fn2()) // Compliant by exception
                      ^~~~~~
a5-0-2.cpp:55:14: warning: unused variable 'flag' [-Wunused-variable]
  while (bool flag = fn3()) // Compliant
              ^~~~
a5-0-2.cpp:60:20: warning: unused variable 'ptr' [-Wunused-variable]
  if (std::int32_t* ptr = fn())
                    ^~~
a5-0-2.cpp:63:19: warning: unused variable 'length' [-Wunused-variable]
  if (std::int32_t length = fn2())
                   ^~~~~~
a5-0-2.cpp:66:11: warning: unused variable 'flag' [-Wunused-variable]
  if (bool flag = fn3())
           ^~~~
ip=0x10b088130
Rule A5-0-2 (required, implementation, automated)The condition of an if-statement and the condition of an iteration statementshall have type bool.(32)A5-0-2.cpp
$ g++-8 a5-0-2.cpp a5-0-2a.cppp -std=c++17  -Wall
a5-0-2.cpp: In function 'void f()':
a5-0-2.cpp:50:22: warning: unused variable 'length' [-Wunused-variable]
  while (std::int32_t length = fn2()) // Compliant by exception
                      ^~~~~~
a5-0-2.cpp:55:14: warning: unused variable 'flag' [-Wunused-variable]
  while (bool flag = fn3()) // Compliant
              ^~~~
a5-0-2.cpp:60:20: warning: unused variable 'ptr' [-Wunused-variable]
  if (std::int32_t* ptr = fn())
                    ^~~
a5-0-2.cpp:63:19: warning: unused variable 'length' [-Wunused-variable]
  if (std::int32_t length = fn2())
                   ^~~~~~
a5-0-2.cpp:66:11: warning: unused variable 'flag' [-Wunused-variable]
  if (bool flag = fn3())
           ^~~~
ip=0x10e199130
Rule A5-0-2 (required, implementation, automated)The condition of an if-statement and the condition of an iteration statementshall have type bool.(32)A5-0-2.cpp
$ g++-8 a5-0-2.cpp a5-0-2a.cppp -std=c++2a  -Wall
a5-0-2.cpp: In function 'void f()':
a5-0-2.cpp:50:22: warning: unused variable 'length' [-Wunused-variable]
  while (std::int32_t length = fn2()) // Compliant by exception
                      ^~~~~~
a5-0-2.cpp:55:14: warning: unused variable 'flag' [-Wunused-variable]
  while (bool flag = fn3()) // Compliant
              ^~~~
a5-0-2.cpp:60:20: warning: unused variable 'ptr' [-Wunused-variable]
  if (std::int32_t* ptr = fn())
                    ^~~
a5-0-2.cpp:63:19: warning: unused variable 'length' [-Wunused-variable]
  if (std::int32_t length = fn2())
                   ^~~~~~
a5-0-2.cpp:66:11: warning: unused variable 'flag' [-Wunused-variable]
  if (bool flag = fn3())
           ^~~~
ip=0x103d4b130
Rule A5-0-2 (required, implementation, automated)The condition of an if-statement and the condition of an iteration statementshall have type bool.(32)A5-0-2.cpp

検討事項(agenda)

1. 自律(freestanding)環境. 接待(hosted)環境

C++N4606 1.4 Implementation compliance p.4

2. 対応OSの水準、対応通信規約、応用機能による分類

freestanding用の関数、ライブラリ等

3. C++2014, C++2017, C++202aの比較項目

本件なし

4. clang++, g++の比較検討項目

clang++警告なし、g++警告あり

5 役立つまたは意味のある出力

参考文献(reference)

プログラミング言語教育のXYZ

https://qiita.com/kaizen_nagoya/items/1950c5810fb5c0b07be4
プログラミング言語教育のXYZ(youtube)
https://www.youtube.com/watch?v=He1_tg4px-w&t=486s

C++N4741 2018

Working Draft, Standard for Programming Language C++
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/n4741.pdf

C++N4741, 2018 Standard Working Draft on ISO/IEC 14882 sample code compile list
https://qiita.com/kaizen_nagoya/items/3294c014044550896010

C++N4606 2016

Working Draft, Standard for Programming Language C++
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/n4606.pdf

C++N4606, 2016符号断片編纂一覧(example code compile list)
Working Draft 2016, ISO/IEC 14882(1)
https://qiita.com/kaizen_nagoya/items/df5d62c35bd6ed1c3d43/

 CEDD(Compile Error Driven Design)

初めての CEDD(Compile Error Driven Design) 8回直してコンパイル。
https://qiita.com/kaizen_nagoya/items/9494236aa1753f3fd1e1

コンパイルエラーを記録するとよい理由7つ
https://qiita.com/kaizen_nagoya/items/85c0e92b206883140e89

C Puzzle Bookの有り難み5つ、C言語規格及びCコンパイラの特性を認識
https://qiita.com/kaizen_nagoya/items/d89a48c1536a02ecdec9

C言語(C++)に対する誤解、曲解、無理解、爽快。
https://qiita.com/kaizen_nagoya/items/3f3992c9722c1cee2e3a

Qiitaに投稿するCのStyle例(暫定)
https://qiita.com/kaizen_nagoya/items/946df1528a6a1ef2bc0d

C++N4606 Working Draft 2016, ISO/IEC 14882, C++ standardのコード断片をコンパイルするためにしていること
https://qiita.com/kaizen_nagoya/items/a8d7ee2f2e29e76c19c1

コンパイル用shell script C版(clangとgcc)とC++版(clang++とg++)
https://qiita.com/kaizen_nagoya/items/74220c0577a512c2d7da

[C][C++]の国際規格案の例題をコンパイルするときの課題7つ。
https://qiita.com/kaizen_nagoya/items/5f4b155030259497c4de

docker gnu(gcc/g++) and llvm(clang/clang++)
https://qiita.com/drafts/059874ea39c4de64c0f7

文書履歴(document history)

ver 0.10 初稿 20180610
ver 0.11 一覧追記 参考文献欄追記 20180616