updated mingw
Moderator: InsideQC Admins
50 posts
• Page 4 of 4 • 1, 2, 3, 4
completed build of gcc-4.6.1 from svn.
the 64 bit compiler can now bootstrap itself again (was indeed a binutils problem) link time optimizer crashed on 64 bit when loading the plugin.
up on my site now is a fresh build of the insight debugger from cvs with latest gdb and a new version of a mingw built python (2.7.1).
both insight and gdb can use python for debugging.
theres also a server and if some prefer to debug via a terminal theres a pdcurses front for gdb also.
dont let the simple interface fool you insight is a very powerfull debugger indeed ,besides not supporting JIT it can do anything msvc can.
as for the new gcc builds ill repack them soon.
the 64 bit compiler can now bootstrap itself again (was indeed a binutils problem) link time optimizer crashed on 64 bit when loading the plugin.
up on my site now is a fresh build of the insight debugger from cvs with latest gdb and a new version of a mingw built python (2.7.1).
both insight and gdb can use python for debugging.
theres also a server and if some prefer to debug via a terminal theres a pdcurses front for gdb also.
dont let the simple interface fool you insight is a very powerfull debugger indeed ,besides not supporting JIT it can do anything msvc can.
as for the new gcc builds ill repack them soon.
-

revelator - Posts: 2567
- Joined: Thu Jan 24, 2008 12:04 pm
- Location: inside tha debugger
btw if theres interrest i also have a special build of the llvm-gcc compiler.
llvm is normally used on apple with there xcode compiler on windows theres not yet any ide for it (codeblocks wont work either)
so its commandline only.
the good thing about this compiler is the code checking and optimization options.
it works by outputting bytecode that the llvm-gcc frontend can then compile.
the llvm-gcc frontend is a rather old 4.2 gcc but that doesnt matter
since the heavy stuff will be taken care of by the llvm backend.
i have a darkplaces executable compiled with it if anyone wants to compare with other builds.
llvm is normally used on apple with there xcode compiler on windows theres not yet any ide for it (codeblocks wont work either)
so its commandline only.
the good thing about this compiler is the code checking and optimization options.
it works by outputting bytecode that the llvm-gcc frontend can then compile.
the llvm-gcc frontend is a rather old 4.2 gcc but that doesnt matter
since the heavy stuff will be taken care of by the llvm backend.
i have a darkplaces executable compiled with it if anyone wants to compare with other builds.
-

revelator - Posts: 2567
- Joined: Thu Jan 24, 2008 12:04 pm
- Location: inside tha debugger
gcc-4.6.1 released.
just need to check if my old patches for 4.6.0 still needs to be applied then ill make some new packages.
4.6.1 had several bugfixes reported by users (me included)
i spotted a typo in the cpp source which caused the entire compiler to crash when bootstrapped, its fixed in 4.6.1.
cpp not working also ment that codeblocks couldnt parse the project files so all in all id say i did a mighty fine job on hunting that bugger down
just need to check if my old patches for 4.6.0 still needs to be applied then ill make some new packages.
4.6.1 had several bugfixes reported by users (me included)
i spotted a typo in the cpp source which caused the entire compiler to crash when bootstrapped, its fixed in 4.6.1.
cpp not working also ment that codeblocks couldnt parse the project files so all in all id say i did a mighty fine job on hunting that bugger down
-

revelator - Posts: 2567
- Joined: Thu Jan 24, 2008 12:04 pm
- Location: inside tha debugger
gcc-4.6.1 release for both 32 and 64 bit are up on my google code site now
to update your previous gcc delete /mingw32/libexec/gcc or /mingw64/libexec/gcc folder also delete /mingw32/lib/gcc or /mingw64/lib/gcc folder and lastly get rid of any i686-w64-mingw32-previousversion.gcc or whatever same for x86_64.
now overwrite everything with the new package.
there you go.
to update your previous gcc delete /mingw32/libexec/gcc or /mingw64/libexec/gcc folder also delete /mingw32/lib/gcc or /mingw64/lib/gcc folder and lastly get rid of any i686-w64-mingw32-previousversion.gcc or whatever same for x86_64.
now overwrite everything with the new package.
there you go.
-

revelator - Posts: 2567
- Joined: Thu Jan 24, 2008 12:04 pm
- Location: inside tha debugger
50 posts
• Page 4 of 4 • 1, 2, 3, 4
Who is online
Users browsing this forum: No registered users and 2 guests