Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rational behind -std=gnu++14, and change it to -std=c++14 #16936

Open
mratsim opened this issue Feb 4, 2021 · 2 comments
Open

Rational behind -std=gnu++14, and change it to -std=c++14 #16936

mratsim opened this issue Feb 4, 2021 · 2 comments

Comments

@mratsim
Copy link
Collaborator

mratsim commented Feb 4, 2021

Since Nim 1.2, Nim is using the -std=gnu++14 to compile C++ code.

What's the rationale behind it? Could -std=c++14 achieve the same goal?

Currently Arraymancer Cuda backend is only usable with Nim 1.0 due to that as there is no way to remove that options apart from override the user nim.cfg file. mratsim/Arraymancer#478

#13798 does not help, the flag must be absent from the command line.

@timotheecour
Copy link
Member

@mratsim I was also wondering about this recently; can you try a PR that changes it to -std=c++14 and see what breaks?

@Araq
Copy link
Member

Araq commented Feb 5, 2021

We use GNU extensions like ranges inside switch and computed gotos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants