Two issues with compiler --std= values

Static source code analysis tool for C and C++ code

Brought to you by: danielmarjamaki

Two issues with compiler --std= values

Forum: General Discussion

Creator: Andrew C Aitchison

Created: 2024-11-17

Updated: 2024-12-04

Andrew C Aitchison - 2024-11-17

I note two issues with compiler -std= values in the dmake tool:

"clang++" contains "g++", so with the test for g++ before the test for clang++, CXXFLAGS includes the gnu options when using clang++ - patch attached.

Here, -std is set to gnu++0x or c++0x (not even c++03) but elsewhere in the same file we use -std=c++11 (but not gnu++11 !). If we set std at all, should we not be consistent about which version ?

stdCXXmake.patch
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andrew C Aitchison - 2024-11-24

That doesn't read right. As is clang++ gets the g++ options.
The attached patch gives clang++ the correct options.

But why are we forcing a decades old standard and not even using the correct name ?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Oliver Stöneberg - 2024-12-04

Thanks for reporting this.

It just has always been inconsistent. And we were using the legacy aliases because we were (unnecessarily) supporting some ancient compilers for quite a while.

I filed https://trac.cppcheck.net/ticket/13375 about it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.