Guidelines for the use of the C++14 language in critical and
safety-related systems Sample code compile list(73)
https://www.autosar.org/fileadmin/user_upload/standards/adaptive/17-03/AUTOSAR_RS_CPP14Guidelines.pdf
Autosar Guidelines C++14, example code compile list(
#目的(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の特徴と課題を明確にする。
#A8-4-2.cpp
##算譜(source code)
//Guidelines for the use of the C++14 language in critical and safety-related systems
const char* msg="Rule A8-4-2 (required, implementation, automated)All exit paths from a function with non-void return type shall have an explicit return statement with an expression.(73)A8-4-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
using namespace std;/// @line add using
///start AUTOSAR: From here to the "///end AUTOSAR" is from AUTOSAR without code having /// comment in line.
// $Id: A8-4-2.cpp 271687 2017-03-23 08:57:35Z piotr.tanski $
#include <cstdint>
#include <stdexcept>
std::int32_t f1() noexcept // Non-compliant
{
return true;/// @ line for warning
}
std::int32_t f2(std::int32_t x) noexcept(false)
{
if (x > 100)
{
throw std::logic_error("Logic Error"); // Compliant by exception
}
cout <<"x="<<x<<endl;/// @ line for output
return x; // Compliant
}
std::int32_t f3(std::int32_t x, std::int32_t y)
{
cout <<"x="<<x<<" y="<<y<<endl;/// @ line for output
if (x > 100 || y > 100)
{
throw std::logic_error("Logic Error"); // Compliant by exception
}
if (y > x)
{
return (y - x); // Compliant
}
return (x - y); // Compliant
}
///end AUTOSAR
int start() { /// @{} for start
int32_t i=20;
int32_t j=51;
f1();
f2(i);
f3(i,j);
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 a8-4-2
$ clang++ a8-4-2.cpp -I./ -std=c++14 -Wall
x=20
x=20 y=51
Rule A8-4-2 (required, implementation, automated)All exit paths from a function with non-void return type shall have an explicit return statement with an expression.(73)A8-4-2.cpp
$ clang++ a8-4-2.cpp -I./ -std=c++17 -Wall
x=20
x=20 y=51
Rule A8-4-2 (required, implementation, automated)All exit paths from a function with non-void return type shall have an explicit return statement with an expression.(73)A8-4-2.cpp
$ clang++ a8-4-2.cpp -I./ -std=c++2a -Wall
x=20
x=20 y=51
Rule A8-4-2 (required, implementation, automated)All exit paths from a function with non-void return type shall have an explicit return statement with an expression.(73)A8-4-2.cpp
$ g++-8 a8-4-2.cpp -I./ -std=c++14 -Wall
x=20
x=20 y=51
Rule A8-4-2 (required, implementation, automated)All exit paths from a function with non-void return type shall have an explicit return statement with an expression.(73)A8-4-2.cpp
$ g++-8 a8-4-2.cpp -I./ -std=c++17 -Wall
x=20
x=20 y=51
Rule A8-4-2 (required, implementation, automated)All exit paths from a function with non-void return type shall have an explicit return statement with an expression.(73)A8-4-2.cpp
$ g++-8 a8-4-2.cpp -I./ -std=c++2a -Wall
x=20
x=20 y=51
Rule A8-4-2 (required, implementation, automated)All exit paths from a function with non-void return type shall have an explicit return statement with an expression.(73)A8-4-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 役立つまたは意味のある出力
関数呼び出し時の大きさが100を超えていると例外が発生している。
今回は例外が発生しない状態にしている。
#参考文献(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 初稿 20180611