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
Compiler warnings on GCC and MinGW #24
Comments
Warnings on Windows, MinGW x32 with GCC 4.8.1:
|
Warnings on Windows, MinGW x64 with GCC 4.9.2:
|
Th first warning is kind of interesting. I thought we cleared it at 69c6989. |
Which one, in particular? |
Oh, you mean the second one... |
The line number seems to be different from the one in commit. |
I believe we cleared these warnings. From a Windows 7 x64 machine and MinGW:
|
And what about the warnings that are displayed on Linux during compilation with CRYPTOPP_NO_UNALIGNED_ACCESS defined? |
Note that I have reported three different types of warnings on different platforms. |
On Sun, Oct 25, 2015 at 5:53 AM, Ilya Bizyaev notifications@github.com
Hmm... I'm not sure. I thought this report was for MinGW. I believe they are cleared on Linux, too. |
Ok, I'll test them today, although I now have different Ubuntu and GCC versions on my PC. |
I have tested it on GCC 5.2.1 on Ubuntu 15.10, Linux 4.2.0-16-generic, and here is the only warning: g++ -DNDEBUG -g2 -O3 -fPIC -march=native -DCRYPTOPP_DISABLE_ASM -Wall -Wextra -Wno-type-limits -Wno-unknown-pragmas -pipe -c fipstest.cpp pragma GCC diagnostic ignored "-Wunneeded-internal-declaration" |
Warnings on Windows, MinGW x64 with GCC 4.9.2:
And finally, here is an error:
|
And nothing has changed on MinGW-32 either. So, I suppose, this issue should be reopened. |
|
There are lots of warnings when building Crypto++ with TDM-GCC 5.1.0. Here are some of them:
And both |
These are expected as we warn about impending changes. For these warnings, you need to:
We can't add it because it neutralizes what we are trying to achieve by warning folks. This one looks new or it was overlooked in the past. We might be able to fix it. Can you tell us what MinGW is defining it to?
It looks like the left part of the message was lost. Can you open up the offending file and add an
Yeah, we've seen some trouble with GCC 5.x. See, for example, Hang on Debian ARM64 QEMU Chroot. We think its an issue with the compiler, but we are not certain. We engaged one of the GCC devs about it. In the 3rd week of December, he checked the ARM64 platform using GCC Master, and he confirmed the issue is still present in GCC 6.0. I emailed him on Thursday, December 31 about it. I have not received a reply yet. I hope to get one soon.
|
I have just found out that incorrect cryptest.exe behaviour is not a Crypto++ problem. That's somewhat like an Avast and TDM conflict. I have disabled Avast, and Crypto++ has passed all tests. |
Here are the warnings that are displayed on Linux during compilation with CRYPTOPP_NO_UNALIGNED_ACCESS defined:
GCC version: 4.9.2, Ubuntu 15.04, Linux Kernel 3.19.0-25-generic.
The text was updated successfully, but these errors were encountered: