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

fix -Wmisleading-indentation warnings #19

Conversation

mfernan2
Copy link
Collaborator

I only fixed the indentation issues in this commit, not GCC 7.2.0's other complaint (throwing from destructors). The other warnings are in cxxtest code and it did not seem like the correct solution to modify the third-party code. Another interesting aspect is that my build output implies GCC is issuing these warnings because it is compiling as C++11. The top level makefiles set C++0x, so maybe somewhere down the recursive build the flags are being lost and GCC 7.2.0 is defaulting to C++11.

Newer versions of GCC (e.g. 7.2.0) include -Wmisleading-indentation in -Wall,
causing compilation to fail on a couple of files. Herein we fix the specific
lines causing warnings.
@ibeling
Copy link
Collaborator

ibeling commented Apr 23, 2018

Thanks for the note about C++11. Let's be careful that this isn't causing issues down the line. @guykatzz

@ibeling ibeling merged commit cf85db8 into NeuralNetworkVerification:master Apr 23, 2018
@mfernan2
Copy link
Collaborator Author

Debugged this a bit more and discovered the flags are being passed down correctly. I think GCC is referencing C++11 in its warnings because this is what C++0x became. I was not aware of this and had previously thought C++0x was a distinct, prior standard.

yuvaljacoby pushed a commit to yuvaljacoby/Marabou-1 that referenced this pull request Jun 9, 2020
matanost pushed a commit that referenced this pull request Nov 2, 2021
Newer versions of GCC (e.g. 7.2.0) include -Wmisleading-indentation in -Wall,
causing compilation to fail on a couple of files. Herein we fix the specific
lines causing warnings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants