Re: Trouble with building multilib GCC (MinGW)
> As far as I can tell from your original note, your build failed because > you do not have a 64-bit version of the library -lkernel32. That is not > a gcc library. I assume it is a Windows library. I don't know if you > are missing a 64-bit version of the library, or if the bug is that you > should not be linking against -lkernel32 for a 64-bit build. E.g., > perhaps there is a -lkernel64 on Windows, I don't know. I have built both versions of CRT for 32 and 64 bit. 32bit CRT in //lib path, and 64bit in //lib64 If you see logfile: http://pastebin.com/KiGHVgVQ then you can see that for linking 32bit and 64bit libgcc_s_sjlj-1.dll are used 32bit CRT. If in Makefile for 64bit version I replace //lib with //lib64 - linking is successfully. I.e. the problem is that wrong Makefiles are created. I want to understand why? Ping?
Re: auto/decltype question about implementation
> Can you please tell, auto is implemented based on the decltype > implementation with some semantics, or they are two completely > different implementations? > > And one more question: in which files/functions I can view the > implementation of auto and decltype? Ping? -- Regards, niXman
fine grained control over testsuite
Q: is there a way to prevent a test timing out ? I see a lot of this sort of thing : Running /opt/bw/src/gcc-4.5.3/gcc/testsuite/gcc.c-torture/compile/compile.exp ... WARNING: program timed out. FAIL: gcc.c-torture/compile/pr46534.c -O0 (test for excess errors) WARNING: program timed out. FAIL: gcc.c-torture/compile/pr46534.c -O1 (test for excess errors) WARNING: program timed out. FAIL: gcc.c-torture/compile/pr46534.c -O2 (test for excess errors) WARNING: program timed out. FAIL: gcc.c-torture/compile/pr46534.c -O3 -fomit-frame-pointer (test for excess errors) WARNING: program timed out. . . . Somewhat annoying as I am in no particular hurry. :-) dc -- -- http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B +-+---+ | Dennis Clarke | Solaris and Linux and Open Source | | dcla...@blastwave.org | Respect for open standards. | +-+---+
Re: auto/decltype question about implementation
On 11 March 2012 15:32, niXman wrote: >> And one more question: in which files/functions I can view the >> implementation of auto and decltype? Search for RID_AUTO and RID_DECLTYPE in gcc/cp/*.c
Re: auto/decltype question about implementation
2012/3/11 Jonathan Wakely : > On 11 March 2012 15:32, niXman wrote: >>> And one more question: in which files/functions I can view the >>> implementation of auto and decltype? > > Search for RID_AUTO and RID_DECLTYPE in gcc/cp/*.c Thanks Jonathan. -- Regards, niXman
Re: Trouble with building multilib GCC (MinGW)
Hello, To successfully compile multilib with mingw-w64, you should follow procedure described as in http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/trunk/mingw-w64-doc/howto-build/mingw-w64-howto-build-adv.txt the main points are: 1- build and install binutils 2- install headers 2b- link /x86_64-w64-mingw32/include to path>/mingw/include 3- build and install gmp, mpfr and mpc (or make sure to copy them sources respectively in /gmp /mpfr and /mpc ) 4- build and install gcc ( make all-gcc && make install-gcc) 5- build and install mingw-w64 crt 5b- link /x86_64-w64-mingw32/lib to path>/x86_64-w64-mingw32/lib64 5c- link /x86_64-64-mingw32 to /mingw (this is only needed for stage 2 and stage 3 building, this directory may be erased once installation has finished ;) ) Don't forget to verify that content of /mingw/lib and /mingw/lib64 correspond exactly to path>/x86_64-w64-mingw32/lib (and to path>/x86_64-w64-mingw32/lib64) 6- build and install libgcc (make all-target-libgcc && make install-target-libgcc ) 7- check that there are no missplaced library into /lib/gcc/x86_64-w64-mingw32/lib or /lib/gcc/x86_64-w64-mingw32/lib32 (they should be in respectively /lib/gcc/x86_64-w64-mingw32/4.7.0 or /lib/gcc/x86_64-w64-mingw32/4.7.0/32 ) 8- complete build process (3 stages ;)) and install script (make && make install) 9- Once build and install is finished, consider to get 2 distinct directories, added to PATH variable for the dll: one where to find 64 bit dll version and one where to find 32 bit dll version Pay attention to the fact that the install script can mix different versions of the dll in the folder / bin. I personnaly recommand to copy manually one version (32 bit or 64 bit) into this path . I just still have problem to compile ada with multilib support :-S Hope it helps PS Excuse me for my bad english, my natural speaking is french :-)
gcc-4.8-20120311 is now available
Snapshot gcc-4.8-20120311 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20120311/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 185201 You'll find: gcc-4.8-20120311.tar.bz2 Complete GCC MD5=54bd15e37c762d69bb95dff8af0629ba SHA1=c152c8f8043f09c49cd6b7fd9710aad31ec0bef2 Diffs from 4.8-20120304 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.8 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
