psptoolchain gcc 4.3.1 & gdb 6.8 available
-
- Posts: 203
- Joined: Sat Jul 05, 2008 8:03 am
psptoolchain gcc 4.3.1 & gdb 6.8 available
I've just uploaded on http://194.7.150.2/psptoolchain431.tgz
a update of the toolchain for linux
gcc 4.3.1 and GDB 6.8
a update of the toolchain for linux
gcc 4.3.1 and GDB 6.8
Committed, now lets see if people complain. :)$ svn commit
Deleting patches/gcc-4.3.0-PSP.patch
Adding patches/gcc-4.3.1-PSP.patch
Deleting scripts/002-gcc-4.3.0-stage1.sh
Adding scripts/002-gcc-4.3.1-stage1.sh
Deleting scripts/005-gcc-4.3.0-stage2.sh
Adding scripts/005-gcc-4.3.1-stage2.sh
Transmitting file data ...
Committed revision 2424.
-
- Posts: 203
- Joined: Sat Jul 05, 2008 8:03 am
Something is up with 4.3.x that causes binaries to ~double in size, I vaguely recall something from a mailing list that it's linking in code that is never used or doesn't need to be in the bin but I'll be darned if I can find the specifics again (I'm going by heimdall's win build specifically, though.)
I only suggest one final fix!
Since you used my patches you can reduce 1 patch that if it is applied to the correct project and you don't need to maintain it anymore.
trunk/psptoolchain/scripts/009-psplinkusb.sh
This was a patch from a older thread on this forum that i made to get psplinkusb to work better on the slims. If you apply it directly to the psplinkusb project then is one less patch.
And you forgot to remove gcc-4.1.0-PSP.patch, it still remains there but is kind of junk.
Since you used my patches you can reduce 1 patch that if it is applied to the correct project and you don't need to maintain it anymore.
trunk/psptoolchain/scripts/009-psplinkusb.sh
This was a patch from a older thread on this forum that i made to get psplinkusb to work better on the slims. If you apply it directly to the psplinkusb project then is one less patch.
And you forgot to remove gcc-4.1.0-PSP.patch, it still remains there but is kind of junk.
Ok fair enough, just for reference here's the thread that made me create the patch:
http://forums.ps2dev.org/viewtopic.php?p=72235
http://forums.ps2dev.org/viewtopic.php?p=72235
-
- Posts: 203
- Joined: Sat Jul 05, 2008 8:03 am
Still no problem with the 4.3.1 the path for psplinkusb isn't correct anymore with the release
present int the svn.
As said by heimdall:
at psptoolchain/build/psplinkusb/boot271
edit Makefile
ADD PSP_LARGE_MEMORY = 1
and use
mksfoex -d MEMSIZE=1 'PSPLink v3.0 OE' PARAM.SFO in place of mksfo
in main.c in the same directory add
PSP_HEAP_SIZE_KB(-64);
So we have a homebrew that use the extra memory if launched on a slim
present int the svn.
As said by heimdall:
at psptoolchain/build/psplinkusb/boot271
edit Makefile
ADD PSP_LARGE_MEMORY = 1
and use
mksfoex -d MEMSIZE=1 'PSPLink v3.0 OE' PARAM.SFO in place of mksfo
in main.c in the same directory add
PSP_HEAP_SIZE_KB(-64);
So we have a homebrew that use the extra memory if launched on a slim
just built the updated toolchain on ubuntu 8, compiles perfect, FLAWLESS.
Wanted to post my thanks to all the people who continually work to improve this jem of a toolchain. And also thanks to H for maintaining the win32 version, which i also use.
I believe most of the homebrew community present on other sites have no idea how much effort has gone into this, which is a shame!
Wanted to post my thanks to all the people who continually work to improve this jem of a toolchain. And also thanks to H for maintaining the win32 version, which i also use.
I believe most of the homebrew community present on other sites have no idea how much effort has gone into this, which is a shame!
Yeah, the makefile templates take care of stripping the binaries. As far as I can tell, GCC is the bit that changed between versions and if I'm remembering the commit notice right it has something to do with std stuffs.Heimdall wrote:About the "double size" my guess is that it is not related with GCC itself but with binutils.
Anyway did you try to strip your app after the linking is done?
strip -s yourproject.elf
this usually reduces the size of your binaries...
Any rate, here is an example along with the cli output (with gcc -v output as well - back when I had the cygwin toolchain working correctly it's final stripped binaries were identical in size/form to the dkpro ones.)
Notably, the build I just did of the same app (hello world elf template) with a dated linux toolchain with gcc 4.1.0 showed a <4k size diff to your 4.3.1 build (I can infer then something was fixed between 4.1.0 and 4.1.2, which was then lost in 4.3.1 - or was never present to begin with in the default ps2dev toolchains.) Hope it helps more than my poor memory and near utter lack of knowledge of what is going into making the toolchains tick.
btw: (doubled binary size) vs. (NULL pointers and the inability to reliably use switch()) = no contest in my book. Thanks for the GCC updates.
-
- Posts: 1
- Joined: Sun Sep 14, 2008 11:37 am
Edit: Nevermind.. I took a look at the patch file and I think I see the problem. :)
Sorry if this has already been ask.. I'm new to PSP development and wanted to just get my environment setup. I was able to get all the libraries and a new GCC 4.3.1 on my Ubuntu 8.04 box. I ran the toolchain-sudo.sh and it ran through mostly, but it exited with this error:
Any ideas what I need to do to get it to work?
Sorry if this has already been ask.. I'm new to PSP development and wanted to just get my environment setup. I was able to get all the libraries and a new GCC 4.3.1 on my Ubuntu 8.04 box. I ran the toolchain-sudo.sh and it ran through mostly, but it exited with this error:
Code: Select all
At revision 2431.
patching file boot271/Makefile
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 13.
2 out of 2 hunks FAILED -- saving rejects to file boot271/Makefile.rej
../scripts/009-psplinkusb.sh: Failed.
ERROR: Could not run the toolchain script.
-
- Posts: 203
- Joined: Sat Jul 05, 2008 8:03 am
The latest version of psptoolchain shouldn't be attempting to patch psplinkusb anymore, it was added to the psplinkusb source instead.
The changes that were added can be seen here: http://forums.ps2dev.org/viewtopic.php?p=73773#73773
The changes that were added can be seen here: http://forums.ps2dev.org/viewtopic.php?p=73773#73773