Compiler Settings: limited to C++ 14 standard

[kakas]

I just found out that in the "Compiler Flags" section of the compiler settings, the c++ standard goes up only to C++ 14.
Thought I have latest gnu compilers installed.
It's the same with both nightly build(April 1st 2024) and stable release of CB.

[blauzahn]

Strange. Nevertheless, you can always add flags (e.g. -std=c++20 or more warnings) in other compiler options.

I use cb under Linux only and have newer standards listed for years.

[nenin]

I just found out that in the "Compiler Flags" section of the compiler settings, the c++ standard goes up only to C++ 14.
Thought I have latest gnu compilers installed.
It's the same with both nightly build(April 1st 2024) and stable release of CB.

You can directly introduce any options supported by compiler in "Other compiler options". "Compiler Flags" is outdated and missing some important flags like "-march=x86-64-v2" [/b]

[kakas]

You can directly introduce any options supported by compiler in "Other compiler options". "Compiler Flags" is outdated and missing some important flags like "-march=x86-64-v2" [/b]

oh, I see
I wonder if this should be reported as a bug somewhere

[kakas]

Strange. Nevertheless, you can always add flags (e.g. -std=c++20 or more warnings) in other compiler options.

I use cb under Linux only and have newer standards listed for years.

yea, I just used to ignore flags in tutorials/guides thinking I just have some outdated piece of software.

It might be just a windows thing.

[nenin]

You can directly introduce any options supported by compiler in "Other compiler options". "Compiler Flags" is outdated and missing some important flags like "-march=x86-64-v2" [/b]

oh, I see
I wonder if this should be reported as a bug somewhere

In nighties I have standard support up to C++ 2020 and C 2017. But there are so many other flags for the the GCC...