usage of ldscripts/mipsirx.xn... in iop-gcc

Discuss the development of software, tools, libraries and anything else that helps make ps2dev happen.

Moderators: cheriff, Herben

Post Reply
muckle
Posts: 5
Joined: Thu Sep 08, 2005 1:24 am
Location: under the bed

usage of ldscripts/mipsirx.xn... in iop-gcc

Post by muckle »

Anyone know why the contents of $PS2DEV/iop/iop/ldscripts aren't processed when using iop-gcc??? I'm in the process of evaluating switching from the "dreaded-broken combo EE-IOP C/C++ gcc3.2.2 version of about a year back (which I've used quite happily until I recently found some nasty and unpredictable relocation bugs in the code generated by ps2-gcc).

Part of making C++ work on the iop (nasty comments > /dev/null please), involves fixing the mipsirx.xn script to (a) handle ctor/dtors and (b) pack all the .gnu.linkonce... sections together.

The latest version of iop-gcc appears to ignore ldscripts/* (that is, I can move it to another name and the link still merrily proceeds along)- and of course no globals ctors are called. No matter that, I can call them if only I knew where they were... hence the need to a linker script to allow me to plant some symbols.

yes, I can use -T linkscript (which I am doing), but I was wondering if this had been researched and fixed...
Post Reply