Guidelines for the use of the C++14 language in critical and
safety-related systems Sample code compile list(58)
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の特徴と課題を明確にする。
A7-1-3.cpp
算譜(source code)
//Guidelines for the use of the C++14 language in critical and safety-related systems
const char* msg="Rule A7-1-3 (required, implementation, automated)CV-qualifiers shall be placed on the right hand side of the type that is a typedef or a using name.(58)A7-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" is from AUTOSAR without code having /// comment in line.
// $Id: A7-1-3.cpp 271687 2017-03-23 08:57:35Z piotr.tanski $
#include <cstdint>
using IntPtr = std::int32_t*;
using IntConstPtr = std::int32_t* const;
using ConstIntPtr = const std::int32_t*;
void fn(const std::uint8_t& input) // Compliant
{
std::int32_t value1 = 10;
std::int32_t value2 = 20;
const IntPtr ptr1 =
&value1; // Non-compliant - deduced type is std::int32_t*
// const, not const std::int32_t*
// ptr1 = &value2; // Compilation error, ptr1 is read-only variable
IntPtr const ptr2 =
&value1; // Compliant - deduced type is std::int32_t* const
// ptr2 = &value2; // Compilation error, ptr2 is read-only variable
IntConstPtr ptr3 = &value1; // Compliant - type is std::int32_t* const, no
// additional qualifiers needed
// ptr3 = &value2; // Compilation error, ptr3 is read-only variable
ConstIntPtr ptr4 = &value1; // Compliant - type is const std::int32_t*
const ConstIntPtr ptr5 = &value1; // Non-compliant, type is const
// std::int32_t* const, not const const
// std::int32_t*
ConstIntPtr const ptr6 =
&value1; // Compliant - type is const std::int32_t* const
cout <<"value2="<<value2<<endl;/// @ line for output
cout <<"ptr1="<<ptr1<<" ptr2="<<ptr2<<" ptr3="<<ptr3<<" ptr4="<<ptr4<<" ptr5="<<ptr5<<" ptr6="<<ptr6<<endl;/// @ line for output
}
///end AUTOSAR
int start() { /// @{} for start
const uint8_t ui=13;
const uint8_t& uir=ui;
fn(uir);
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 a7-1-3
$ clang++ a7-1-3.cpp -I./ -std=c++14 -Wall
value2=20
ptr1=0x7ffeea5536e4 ptr2=0x7ffeea5536e4 ptr3=0x7ffeea5536e4 ptr4=0x7ffeea5536e4 ptr5=0x7ffeea5536e4 ptr6=0x7ffeea5536e4
Rule Rule A7-1-3 (required, implementation, automated)CV-qualifiers shall be placed on the right hand side of the type that is a typedef or a using name.(58)A7-1-3.cpp
$ clang++ a7-1-3.cpp -I./ -std=c++17 -Wall
value2=20
ptr1=0x7ffee94906e4 ptr2=0x7ffee94906e4 ptr3=0x7ffee94906e4 ptr4=0x7ffee94906e4 ptr5=0x7ffee94906e4 ptr6=0x7ffee94906e4
Rule Rule A7-1-3 (required, implementation, automated)CV-qualifiers shall be placed on the right hand side of the type that is a typedef or a using name.(58)A7-1-3.cpp
$ clang++ a7-1-3.cpp -I./ -std=c++2a -Wall
value2=20
ptr1=0x7ffeead646e4 ptr2=0x7ffeead646e4 ptr3=0x7ffeead646e4 ptr4=0x7ffeead646e4 ptr5=0x7ffeead646e4 ptr6=0x7ffeead646e4
Rule Rule A7-1-3 (required, implementation, automated)CV-qualifiers shall be placed on the right hand side of the type that is a typedef or a using name.(58)A7-1-3.cpp
$ g++-8 a7-1-3.cpp -I./ -std=c++14 -Wall
value2=20
ptr1=0x7ffeeda426f4 ptr2=0x7ffeeda426f4 ptr3=0x7ffeeda426f4 ptr4=0x7ffeeda426f4 ptr5=0x7ffeeda426f4 ptr6=0x7ffeeda426f4
Rule Rule A7-1-3 (required, implementation, automated)CV-qualifiers shall be placed on the right hand side of the type that is a typedef or a using name.(58)A7-1-3.cpp
$ g++-8 a7-1-3.cpp -I./ -std=c++17 -Wall
value2=20
ptr1=0x7ffee9ad06f4 ptr2=0x7ffee9ad06f4 ptr3=0x7ffee9ad06f4 ptr4=0x7ffee9ad06f4 ptr5=0x7ffee9ad06f4 ptr6=0x7ffee9ad06f4
Rule Rule A7-1-3 (required, implementation, automated)CV-qualifiers shall be placed on the right hand side of the type that is a typedef or a using name.(58)A7-1-3.cpp
$ g++-8 a7-1-3.cpp -I./ -std=c++2a -Wall
value2=20
ptr1=0x7ffee9bac6f4 ptr2=0x7ffee9bac6f4 ptr3=0x7ffee9bac6f4 ptr4=0x7ffee9bac6f4 ptr5=0x7ffee9bac6f4 ptr6=0x7ffee9bac6f4
Rule Rule A7-1-3 (required, implementation, automated)CV-qualifiers shall be placed on the right hand side of the type that is a typedef or a using name.(58)A7-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 初稿 20180610