Guidelines for the use of the C++14 language in critical and
safety-related systems Sample code compile list(130)
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の特徴と課題を明確にする。
#A15-3-2.cpp
##算譜(source code)
//Guidelines for the use of the C++14 language in critical and safety-related systems
const char* msg="Rule A15-3-2 (required, implementation, non-automated)If a function throws a checked exception, it shall be handled when meaningful actions can be taken, otherwise it shall be propagated.(130)A15-3-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" are from the AUTOSAR code without some code having /// comment in line.
//% $Id: A15-3-2.cpp 271752 2017-03-23 12:07:07Z piotr.tanski $
#include <cstdint>
#include <iostream>
#include <stdexcept>
class CommunicationError : public std::exception
{
// Implementation
};
// @throw CommunicationError Exceptional communication errors
extern void send(std::uint8_t* buffer) noexcept(false);
void sendData1(std::uint8_t* data) noexcept(false)
{
try
{
send(data);
}
catch (CommunicationError& e)
{
std::cerr << "Communication error occured" << std::endl;
throw; // Non-compliant - exception is not handled, just re-thrown
}
}
extern void busRestart() noexcept;
extern void bufferClean() noexcept;
void sendData2(std::uint8_t* data) noexcept(false)
{
try
{
send(data);
}
catch (CommunicationError& e)
{
std::cerr << "Communication error occured" << std::endl;
bufferClean();
throw; // Compliant - exception is partially handled and re-thrown
}
}
void f1() noexcept
{
std::uint8_t* buffer = nullptr;
// ...
try
{
sendData2(buffer);
}
catch (CommunicationError& e)
{
std::cerr << "Communication error occured" << std::endl;
busRestart();
// Compliant - including SendData2() exception handler, exception is now
// fully handled
}
}
void sendData3(std::uint8_t* data) noexcept
{
try
{
send(data);
}
catch (CommunicationError& e)
{
std::cerr << "Communication error occured" << std::endl;
bufferClean();
busRestart();
// Compliant - exception is fully handled
}
}
/// @ end AUTOSAR
int start() { /// @{} for start
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.
}
#include "autosar.h"/// @line add header file https://qiita.com/kaizen_nagoya/items/4bde8f21ab059b96cf2a
using namespace std;/// @line add using
void send(std::uint8_t* buffer) noexcept(false) {
cout << buffer<<endl;/// @ line for output
}
void busRestart() noexcept {
cout <<"busRestart()"<<endl;/// @ line for output
}
void bufferClean() noexcept {
cout <<"bufferClean()"<<endl;/// @line for output;
}
##編纂・実行結果(compile and go)
$ ../cpa2.sh a15-3-2 a15-3-2a
$ clang++ a15-3-2.cpp a15-3-2a.cpp -std=c++14 -Wall
Rule A15-3-2 (required, implementation, non-automated)If a function throws a checked exception, it shall be handled when meaningful actions can be taken, otherwise it shall be propagated.(130)A15-3-2.cpp
$ clang++ a15-3-2.cpp a15-3-2a.cpp -std=c++17 -Wall
Rule A15-3-2 (required, implementation, non-automated)If a function throws a checked exception, it shall be handled when meaningful actions can be taken, otherwise it shall be propagated.(130)A15-3-2.cpp
$ clang++ a15-3-2.cpp a15-3-2a.cpp -std=c++2a -Wall
Rule A15-3-2 (required, implementation, non-automated)If a function throws a checked exception, it shall be handled when meaningful actions can be taken, otherwise it shall be propagated.(130)A15-3-2.cpp
$ g++-8 a15-3-2.cpp a15-3-2a.cpp -std=c++14 -Wall
Rule A15-3-2 (required, implementation, non-automated)If a function throws a checked exception, it shall be handled when meaningful actions can be taken, otherwise it shall be propagated.(130)A15-3-2.cpp
$ g++-8 a15-3-2.cpp a15-3-2a.cppp -std=c++17 -Wall
Rule A15-3-2 (required, implementation, non-automated)If a function throws a checked exception, it shall be handled when meaningful actions can be taken, otherwise it shall be propagated.(130)A15-3-2.cpp
$ g++-8 a15-3-2.cpp a15-3-2a.cppp -std=c++2a -Wall
Rule A15-3-2 (required, implementation, non-automated)If a function throws a checked exception, it shall be handled when meaningful actions can be taken, otherwise it shall be propagated.(130)A15-3-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++の比較検討項目
本件なし
###5. 役立つまたは意味のある出力
#参考文献(reference)
###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/
#文書履歴(document history)
ver 0.10 初稿 20180612
ver 0.11 一覧追記 20180613