-
Notifications
You must be signed in to change notification settings - Fork 207
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
Error compiling with GCC 8.3.0 #622
Comments
Thanks for reporting. Don't use screenshots. Use formatting syntax instead. |
Another error I encountered while compiling
|
Did you use GNU Toolchain from Arm/Linaro? That is, GNU-A Downloads. |
I didn't do that, I just upgraded the gcc to a higher version and these issues were solved. |
To reproduce and help resolve the issue on your end, I would suggest downloading GNU-A and selecting gcc-8.3.0 for your experiments. Please proceed with this and report back the results. Once you do, I can begin to reproduce the issue on my side. |
I did what you suggested, but it still has that error. |
Yes, I am able to reproduce with both gcc-8.3.0 and gcc-9.2.1 (Arm/Linaro builds). |
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into stange instructions. Fixing the error by not running the tests when using gcc-8.3 and gcc-9.2 fixes DLTcollab#622
Cross compiling with gcc-8.3 and gcc-9.2 would cause operand mismatch error in some tests. The C code of some tests were compiled into unexpected instructions. Fixing the error by not running the tests with gcc prior to 10. Close #622
When I use gcc8.3.0 and gcc9.2.1 to compile and test on ubuntu and redhat, the following error is reported, but when I compile with gcc11.2.0 it is normal, but I don't see you say that there is a limit to the version of gcc, I want to know where this situation is caused.
The text was updated successfully, but these errors were encountered: