From: Cesar S. <ces...@gm...> - 2011-09-15 01:29:38
|
Dear MinGW community, I am pleased to announce the mingw.org release of GCC 4.6.1. GCC is the GNU Compiler Collection, a fairly portable optimizing compiler. This MinGW port generates 32-bit code for Windows, and should run on any 32- or 64-bit Windows operating system. No local patches were used. WARNING: Due to build issues, the Ada language is absent from this release. If you need Ada, please avoid upgrading to this release. Notable new feature: -------------------- The -fno-keep-inline-dllexport flag avoids generating inline functions and methods decorated with __declspec(dllexport). When to use: ------------ Since GCC 4.5.0, methods defined in classes decorated with __declspec(dllexport) are always generated and included in object files. This causes a general increase in object size, since many copies of dllexport'd inline functions and methods end up in object files. Memory use is also increased at link time. See also: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43601 To avoid this, do: 1) Compile all C++ sources with the -fno-keep-inline-dllexport compiler flag. 2) Compile a separate dummy source file, that includes all headers, with -fkeep-inline-dllexport. This will generate all dllexported inline methods and functions, just once. The resulting DLL size should not be affected, but the object size and the link time should be back to normal. Known Issue: ------------- The Ada and Java languages are absent, pending resolution of build issues. * The last mingw.org release offering Ada was GCC 4.5.2-1. * The last mingw.org release offering Java was GCC 4.4.0. Testsuite results: ------------------ The result of the testsuite run for this compiler is available at: http://gcc.gnu.org/ml/gcc-testresults/2011-08/msg02381.html To install: ----------- Run the latest graphical mingw-get-inst installer, checking the option to download the latest repository catalogs. To upgrade: ----------- (Be sure you have latest version of mingw-get) mingw-get update mingw-get upgrade gcc mingw-get upgrade gcc-c++ (optional) mingw-get upgrade gcc-fortran (optional) mingw-get upgrade gcc-objc (optional) Regards, Cesar |
From: Cesar S. <ces...@gm...> - 2011-09-15 02:18:18
|
On 9/14/2011 10:29 PM, Cesar Strauss wrote: > I am pleased to announce the mingw.org release of GCC 4.6.1. I seem to have uploaded a previous build with LTO disabled by accident. I will release an update shortly. Cesar |
From: Charles W. <cwi...@us...> - 2011-09-15 02:29:10
|
On 9/14/2011 10:17 PM, Cesar Strauss wrote: > On 9/14/2011 10:29 PM, Cesar Strauss wrote: >> I am pleased to announce the mingw.org release of GCC 4.6.1. > > I seem to have uploaded a previous build with LTO disabled by accident. > I will release an update shortly. Do we need to warn people that the ABI is now different? http://www.cygwin.com/ml/cygwin-apps/2011-08/msg00236.html "C++ ABI for 4.6.x has also changed for mingw* (including mingw.org) with the introduction of thiscall, not sure if this will affect Cygwin itself." Now, we (mingw.org) don't ship any C++ libraries, so we don't have to worry about ABI compatibility issues with regards to our offerings -- but our users might have to worry about it. P.S. Thanks for this new update. -- Chuck |
From: Cesar S. <ces...@gm...> - 2011-09-15 03:20:21
|
On 9/14/2011 11:28 PM, Charles Wilson wrote: > Do we need to warn people that the ABI is now different? > > http://www.cygwin.com/ml/cygwin-apps/2011-08/msg00236.html > "C++ ABI for 4.6.x has also changed for mingw* (including mingw.org) > with the introduction of thiscall, not sure if this will affect Cygwin > itself." Indeed, thanks. Cesar |
From: Charles W. <cwi...@us...> - 2011-09-15 04:01:24
|
On 9/14/2011 10:28 PM, Charles Wilson wrote: > Now, we (mingw.org) don't ship any C++ libraries With one possible exception! libstdc++-6.dll If I have a *complex* C++ application -- that is, not just Hello, World -- that was built using MinGW gcc-4.5.2 and linked against the current gcc-4.5.2 version of libstdc++-6.dll, and and I replace that DLL with the new gcc-4.6.0 version...will my app continue to run correctly? > so we don't have to > worry about ABI compatibility issues with regards to our offerings -- > but our users might have to worry about it. Perhaps I spoke too soon: since we do ship libstdc++-6.dll. (I assume that we did not -- and should not? do not plan to? -- bump the DLL version of libstdc++ to "7" or anything like that.) Now, maybe libstdc++ is not actually built using the new thiscall convention, so there may not be any appreciable difference between the 4.5.2 and 4.6.0 versions of that DLL. JonY, Kai -- any guidance here? -- Chuck |
From: Kai T. <kti...@go...> - 2011-09-15 07:45:17
|
2011/9/15 Charles Wilson <cwi...@us...>: > On 9/14/2011 10:28 PM, Charles Wilson wrote: >> Now, we (mingw.org) don't ship any C++ libraries > > With one possible exception! libstdc++-6.dll > > If I have a *complex* C++ application -- that is, not just Hello, World > -- that was built using MinGW gcc-4.5.2 and linked against the current > gcc-4.5.2 version of libstdc++-6.dll, and and I replace that DLL with > the new gcc-4.6.0 version...will my app continue to run correctly? > >> so we don't have to >> worry about ABI compatibility issues with regards to our offerings -- >> but our users might have to worry about it. > > Perhaps I spoke too soon: since we do ship libstdc++-6.dll. (I assume > that we did not -- and should not? do not plan to? -- bump the DLL > version of libstdc++ to "7" or anything like that.) > > Now, maybe libstdc++ is not actually built using the new thiscall > convention, so there may not be any appreciable difference between the > 4.5.2 and 4.6.0 versions of that DLL. > > JonY, Kai -- any guidance here? > > -- > Chuck The 4.6.x branch supports thiscall-convention, but first in 4.7.x gcc it gets default calling-convention for standard-class-memeber-functions. So for 4.6.x there shouldn't be any issue to be expected AFAICS. In 4.7.x version (current trunk) there will be some new features for 32-bit windows targets. So thiscall will be default-calling-convention for none varidic, none static class-member functions, the aggregate-callee-pops-return switch is turned on by default, and there are new attributes ms_abi/sysv_abi for 32-bit, too. Additionally some cleanup for rtd were done. Regards, Kai |
From: Cesar S. <ces...@gm...> - 2011-09-15 10:13:06
|
On 9/14/2011 11:17 PM, Cesar Strauss wrote: > On 9/14/2011 10:29 PM, Cesar Strauss wrote: > >> I am pleased to announce the mingw.org release of GCC 4.6.1. > > I seem to have uploaded a previous build with LTO disabled by accident. > I will release an update shortly. Done. Please upgrade again to receive GCC 4.6.1-2. Cesar |
From: asmwarrior <asm...@gm...> - 2011-09-15 14:47:47
|
On 2011-9-15 15:45, Kai Tietz wrote: > So thiscall will be > default-calling-convention for none varidic, none static class-member > functions, Hi, Kai: What does "non varidic" mean? Thanks. asmwarrior ollydbg from codeblocks' forum |
From: Kai T. <kti...@go...> - 2011-09-15 17:28:46
|
2011/9/15 asmwarrior <asm...@gm...>: > > > On 2011-9-15 15:45, Kai Tietz wrote: >> >> So thiscall will be >> default-calling-convention for none varidic, none static class-member >> functions, > > Hi, Kai: > > What does "non varidic" mean? > > Thanks. It means that it class-method doesn't have variable (wildcard)-arguments (...) Kai |
From: David G. <DGr...@am...> - 2011-09-15 16:09:14
|
Dear MinGW community, ... snip ... WARNING: Due to build issues, the Ada language is absent from this release. If you need Ada, please avoid upgrading to this release. AAAAARRGH!!! I use Ada for almost all of my Windows development. What are the problems with the Ada build? I may be able to help get it going. |
From: Cesar S. <ces...@gm...> - 2011-09-16 02:25:56
|
On 9/15/2011 12:38 PM, David Gressett wrote: > AAAAARRGH!!! > I use Ada for almost all of my Windows development. What are the > problems with the Ada build? I may be able to help get it going. Thanks for your offer. One build failure seems to already have been fixed in 4.7: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47163 However, it seems there are new failures: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49084 The best way to help is: 1) Download the developer version of gcc; 2) Build gcc with Ada enabled; 3) Note any build failures; 4) Search the gcc bugzilla for similar errors; 5) If it's a new bug, please report it; 6) If possible, try to fix it yourself; 7) If you find a fix, please submit it to the gcc patch mailing list. Note: if the fix is not trivial, be prepared to sign a copyright assignment or a disclaimer. The same reasoning also applies to fixing the Java build, by the way. Regards, Cesar |
From: Fabian G. <fa...@gr...> - 2011-10-20 07:48:42
|
Am 16.09.2011 04:25, schrieb Cesar Strauss: > One build failure seems to already have been fixed in 4.7: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47163 Could you apply the patch attached to this bug report to the MinGW package and provide ada again? As far as I can tell it comprises the exact two changes that were recently suggested in another thread: Am 19.10.2011 21:35, schrieb Teemu Nätkinniemi: > Before starting pkgbuild apply gcc/buildsys.patch and > gcc/g-socthi-mingw.patch from TDM's sources: > > http://sourceforge.net/projects/tdm-gcc/files/Sources/TDM%20Sources/gcc-4.6.1-tdmsrc-2.zip/download - Fabian |