LoginSignup
0
0

More than 5 years have passed since last update.

Autosar Guidelines C++14, example code compile list(143)Rule A16-0-1 The pre-processor shall only be used

Posted at

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

目的(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の特徴と課題を明確にする。

A16-0-1.cpp

算譜(source code)

A16-0-1.cpp
//Guidelines for the use of the C++14 language in critical and safety-related systems
const char* msg="Rule A16-0-1 (required, implementation, automated) The pre-processor shall only be used for unconditional and conditional file inclusion and include guards, and using the following directives: (1) #ifndef, (2) #ifdef, (3) #if, (4) #if defined, (5) #elif, (6) #else, (7) #define, (8) #endif, (9) #include.(143)A16-0-1.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

using namespace std;/// @line add using

/// @ start AUTOSAR: From here to the "///end AUTOSAR" are from the AUTOSAR code without some code having /// comment in line.
// $Id: A16-0-1.cpp 271687 2017-03-23 08:57:35Z piotr.tanski $
#pragma once // Non-compliant - implementation-defined feature

#ifndef HEADER_FILE_NAME // Compliant - include guard
#define HEADER_FILE_NAME // Compliant - include guard

#include <cstdint> // Compliant - unconditional file inclusion

#ifdef WIN32
#include <windows.h> // Compliant - conditional file inclusion
#endif

#ifdef WIN32
std::int32_t fn1(
  std::int16_t x,
  std::int16_t y) noexcept; // Non-compliant - not a file inclusion
#endif

#if defined VERSION && VERSION > 2011L // Compliant
#include <array> // Compliant - conditional file inclusion
#elif VERSION > 1998L // Compliant
#include <vector> // Compliant - conditional file inclusion
#endif // Compliant

#define MAX_ARRAY_SIZE 1024U // Non-compliant
#ifndef MAX_ARRAY_SIZE // Non-compliant
#error "MAX_ARRAY_SIZE has not been defined" // Non-compliant
#endif // Non-compliant
#undef MAX_ARRAY_SIZE // Non-compliant

#define MIN(a, b) (((a) < (b)) ? (a) : (b)) // Non-compliant
#define PLUS2(X) ((X) + 2) // Non-compliant - function should be used instead
#define PI 3.14159F // Non-compliant - constexpr should be used instead
#define std ::int32_t long // Non-compliant - ’using’ should be used instead
#define STARTIF if( // Non-compliant - language redefinition
#define HEADER "filename.h" // Non-compliant - string literal

void fn2() noexcept
{
#ifdef __linux__ // Non-compliant - ifdef not used for file inclusion

// ...

#elif WIN32 // Non-compliant - elif not used for file inclusion

// ...

#elif __APPLE__ // Non-compliant - elif not used for file inclusion

// ...

#else // Non-compliant - else not used for file inclusion

// ...

#endif // Non-compliant - endif not used for file inclusion or include guards
}
#endif // Compliant - include guard
/// @ end AUTOSAR
int start() { /// @{} for start
#ifdef WIN32
  fn1();
#endif
  fn2();
  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.
}

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

cpa.sh
$ ../cpa.sh a16-0-1
$ clang++ a16-0-1.cpp -I./ -std=c++14 -Wall
a16-0-1.cpp:14:9: warning: #pragma once in main file [-Wpragma-once-outside-header]
#pragma once // Non-compliant - implementation-defined feature
        ^
1 warning generated.
Rule A16-0-1 (required, implementation, automated) The pre-processor shall only be used for unconditional and conditional file inclusion and include guards, and using the following directives: (1) #ifndef, (2) #ifdef, (3) #if, (4) #if defined, (5) #elif, (6) #else, (7) #define, (8) #endif, (9) #include.(143)A16-0-1.cpp
$ clang++ a16-0-1.cpp  -I./ -std=c++17 -Wall
a16-0-1.cpp:14:9: warning: #pragma once in main file [-Wpragma-once-outside-header]
#pragma once // Non-compliant - implementation-defined feature
        ^
1 warning generated.
Rule A16-0-1 (required, implementation, automated) The pre-processor shall only be used for unconditional and conditional file inclusion and include guards, and using the following directives: (1) #ifndef, (2) #ifdef, (3) #if, (4) #if defined, (5) #elif, (6) #else, (7) #define, (8) #endif, (9) #include.(143)A16-0-1.cpp
$ clang++ a16-0-1.cpp  -I./ -std=c++2a -Wall
a16-0-1.cpp:14:9: warning: #pragma once in main file [-Wpragma-once-outside-header]
#pragma once // Non-compliant - implementation-defined feature
        ^
1 warning generated.
Rule A16-0-1 (required, implementation, automated) The pre-processor shall only be used for unconditional and conditional file inclusion and include guards, and using the following directives: (1) #ifndef, (2) #ifdef, (3) #if, (4) #if defined, (5) #elif, (6) #else, (7) #define, (8) #endif, (9) #include.(143)A16-0-1.cpp

$ g++-8 a16-0-1.cpp  -I./ -std=c++14  -Wall
a16-0-1.cpp:14:9: warning: #pragma once in main file
 #pragma once // Non-compliant - implementation-defined feature
         ^~~~
Rule A16-0-1 (required, implementation, automated) The pre-processor shall only be used for unconditional and conditional file inclusion and include guards, and using the following directives: (1) #ifndef, (2) #ifdef, (3) #if, (4) #if defined, (5) #elif, (6) #else, (7) #define, (8) #endif, (9) #include.(143)A16-0-1.cpp
$ g++-8 a16-0-1.cpp  -I./ -std=c++17  -Wall
a16-0-1.cpp:14:9: warning: #pragma once in main file
 #pragma once // Non-compliant - implementation-defined feature
         ^~~~
Rule A16-0-1 (required, implementation, automated) The pre-processor shall only be used for unconditional and conditional file inclusion and include guards, and using the following directives: (1) #ifndef, (2) #ifdef, (3) #if, (4) #if defined, (5) #elif, (6) #else, (7) #define, (8) #endif, (9) #include.(143)A16-0-1.cpp
$ g++-8 a16-0-1.cpp  -I./ -std=c++2a  -Wall
a16-0-1.cpp:14:9: warning: #pragma once in main file
 #pragma once // Non-compliant - implementation-defined feature
         ^~~~
Rule A16-0-1 (required, implementation, automated) The pre-processor shall only be used for unconditional and conditional file inclusion and include guards, and using the following directives: (1) #ifndef, (2) #ifdef, (3) #if, (4) #if defined, (5) #elif, (6) #else, (7) #define, (8) #endif, (9) #include.(143)A16-0-1.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++の比較検討項目

本件なし

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

参考文献(reference)

C++N4741 2018

Working Draft, Standard for Programming Language C++
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/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/

文書履歴

ver 0.10 初稿 20180612

0
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
0