1/1 
|
the future of or32 gcc port [was: gcc-3.2.3 bugs after merge]
by Unknown on Jan 28, 2004 |
Not available! | ||
|
* Heiko Panther (heiko.panther@web.de) wrote:
Regarding different ABI versions:
I was not aware there were two official ABIs (old and new) around at all. So if Scott says UC-gcc-3.4 uses the outdated ABI, then my 3.2.3 does too. Matjaz, you proposed to go back to gcc-3.1 if it works with everything, and go to newer gcc versions from there. I agree with that. I examined the crash Matjaz reported with uclinux and gcc-2.3.2. Looks like it will take some serious amount of gcc debugging to locate the problem. I won't do that, since it seems likely that the version will be abandoned anyway. it looks like UC+OC gcc-3.2.3 just didn't work out. does anybody have a problem with switching to Scott's ABI ? if so would anybody be prepared to fix the UC+OC gcc ? I'd especialy like to hear from UC people since the last thing i want is to have more than one compiler. it will just cause confusion, incompatible OS-es and more work for everybody. i'm not just going to start updating CVS right now. i'd like hear from all who think this issue is important for them and i'd like to have all the discoussion about ABI change, optimizations and everything now, once and for all. right now we have just one compiler that works ok with ALL OS-es. if nobody else can/is willing to produce a working compiler than that's it. so any complaints, comments, suggestions, code,... now is the time! best regards, p. |
|||
1/1