Guidelines for the use of the C++14 language in critical and
safety-related systems Sample code compile list(125)
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の特徴と課題を明確にする。
A15-1-3.cpp
算譜(source code)
//Guidelines for the use of the C++14 language in critical and safety-related systems
const char* msg="Rule A15-1-3 (advisory, implementation, automated)All thrown exceptions should be unique.(125)A15-1-3.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-1-3.cpp 271752 2017-03-23 12:07:07Z piotr.tanski $
#include <iostream>
#include <sstream>
#include <stdexcept>
#include <string>
static std::string composeMessage(const char* file,
const char* func,
std::int32_t line,
const std::string& message) noexcept
{
std::stringstream s;
s << "(" << file << ", " << func << ":" << line << "): " << message;
return s.str();
}
void f1()
{
// ...
throw std::logic_error("Error");
}
void f2()
{
// ...
throw std::logic_error("Error"); // Non-compliant - both exception type and
// error message are not unique
}
void f3()
{
// ...
throw std::invalid_argument(
"Error"); // Compliant - exception type is unique
}
void f4() noexcept(false)
{
// ...
throw std::logic_error("f3(): preconditions were not met"); // Compliant -
// error
// message is
// unique
}
void f5() noexcept(false)
{
// ...
throw std::logic_error(composeMessage(
__FILE__,
__func__,
__LINE__,
"postconditions were not met")); // Compliant - error message is unique
}
void f6() noexcept
{
try
{
f1();
f2();
f3();
}
catch (std::invalid_argument& e)
{
std::cout << e.what() << '\n'; // Only f3() throws this type of
// exception, it is easy to deduce which
// function threw
}
catch (std::logic_error& e)
{
std::cout << e.what() << '\n'; // f1() and f2() throw exactly the same
// exceptions, unable to deduce which
// function threw
}
try
{
f4();
f5();
}
catch (std::logic_error& e)
{
std::cout << e.what() << '\n'; // Debugging process simplified, because
// of unique error message it is known
// which function threw
}
}
/// @ end AUTOSAR
int start() { /// @{} for start
f6();
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 a15-1-3
$ clang++ a15-1-3.cpp -I./ -std=c++14 -Wall
Error
f3(): preconditions were not met
Rule A15-1-3 (advisory, implementation, automated)All thrown exceptions should be unique.(123)A15-1-3.cpp
$ clang++ a15-1-3.cpp -I./ -std=c++17 -Wall
Error
f3(): preconditions were not met
Rule A15-1-3 (advisory, implementation, automated)All thrown exceptions should be unique.(123)A15-1-3.cpp
$ clang++ a15-1-3.cpp -I./ -std=c++2a -Wall
Error
f3(): preconditions were not met
Rule A15-1-3 (advisory, implementation, automated)All thrown exceptions should be unique.(123)A15-1-3.cpp
$ g++-8 a15-1-3.cpp -I./ -std=c++14 -Wall
Error
f3(): preconditions were not met
Rule A15-1-3 (advisory, implementation, automated)All thrown exceptions should be unique.(123)A15-1-3.cpp
$ g++-8 a15-1-3.cpp -I./ -std=c++17 -Wall
Error
f3(): preconditions were not met
Rule A15-1-3 (advisory, implementation, automated)All thrown exceptions should be unique.(123)A15-1-3.cpp
$ g++-8 a15-1-3.cpp -I./ -std=c++2a -Wall
Error
f3(): preconditions were not met
Rule A15-1-3 (advisory, implementation, automated)All thrown exceptions should be unique.(123)A15-1-3.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