News:

When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.

Main Menu

FYI: MSYS2 rolling out mingw-w64-x86_64-gcc-11.2.0-1

Started by AndrewCot, October 22, 2021, 05:59:00 AM

Previous topic - Next topic

AndrewCot

Just did a MSYS2 update and spotted mingw-w64-x86_64-gcc-11.2.0-1 and other GCC collection is being updated from 10.3.0 to 11.2.0

ollydbg

If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

AndrewCot

Wxwidgets 3.1.5 & C::B source both built successfully with no changes required.

I have NOT done any testing yet.

ollydbg

This is the first version of msys2's GCC, which solved this annoying gcc bug when debugging.
See bug description here: an annoying gcc bug which cause bad debugging experience is fixed in gcc trunk
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

AndrewCot

I successfully rebuilt wxWidget and C::B from the C::B I built using GCC 11.2, so the resulting C::B binaries can re-build C::B from source.
I was also able to compile and debug (using GDB) one of my simple test program.

I updated my unofficial installers to use the new binaries and have made them available on sourceforge (see https://forums.next.codeblocks.org/index.php/topic,24592.0.html for details).

gd_on

Cool.
There is one thing which annoys me a little bit : there are new warnings in the wxWidgets compilation itself (in spinctlg.cpp) and more in the wxWidget's samples concerning in particular deprecated comparisons (also in my own wxWidgets programs). You can avoid them by adding the compilations flags -Wno-deprecated-enum-enum-conversion and/or -Wno-deprecated-float-enum-conversion. Apparently, this is because I use -std=gnu++20, but with previous g++ (10.3), the same options did not give the same warnings.
Windows 11 64 bits (25H2), svn C::B (last version or almost!), wxWidgets 3.3.2, Msys2 Compilers 16.1.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

AndrewCot

I did another MSYS2 update and GDB 11.1 package was in the update list and a few other packages.

ollydbg

Quote from: AndrewCot on October 28, 2021, 06:21:42 AM
I did another MSYS2 update and GDB 11.1 package was in the update list and a few other packages.
Good news. I also updated my MSYS2 suite to the latest version.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

ollydbg

If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

AndrewCot

Thanks for the info.

I have been bitten way way way back in GCC 2.x days with incompatibility issues. This is not an issue if you build wxWidget from source and then use it when building C::B, which is what I have done.

ollydbg

Quote from: AndrewCot on October 28, 2021, 11:32:09 AM
Thanks for the info.

I have been bitten way way way back in GCC 2.x days with incompatibility issues. This is not an issue if you build wxWidget from source and then use it when building C::B, which is what I have done.

I work around this issue by

-fabi-version=14

see here:

c++ - wxWidgets runtime error (Mismatch version) - Stack Overflow
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

AndrewCot

Thank you very mush for the link as I was not aware of the ability to set the ABI version.

ollydbg

#12
Quote from: ollydbg on October 28, 2021, 09:52:27 AM
I see one issue when using msys2's wx library:

See here: The wxWidgets library should be rebuilt against the latest gcc 11.x Issue 2677 msys2/MSYS2-packages

I got different ABI mismatch report.

This issue is fixed now, I see the msys2 dev closed my issue by some commits.

In this page: https://packages.msys2.org/queue

I see the status is:

Quote
2021-10-28    mingw-w64-wxWidgets    3.0.5.1-6    →    3.0.5.1-7    Ready for upload but waiting for dependencies
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

ollydbg

If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

AndrewCot

Thanks. It just appeared in the upgrade list this morning for me.