[parisc-linux] Linux/PA-RISC speed (was Re: C240 Graphics, 64bit kernel and more)
John David Anglin
Thu, 15 Nov 2001 10:51:20 -0500 (EST)
> Of course there are bugs in binutils/gcc. But are there KNOW bugs/issues
> a software developer (not a kernel freak) has to be aware of ?
These are the main gcc issues that I am aware of:
1) 32-bit ABI -- 5-7 byte structures are not passed correctly per ABI.
2) I would say avoid "-O3" on mainline at the moment. 3.0.2 is better.
The cause of the bug is unknown.
> What about glibc ?
> Are threads fully supported ? Are gcc's ObjC, Java and C++ compilers
> also working ?
ObjC builds and testsuite results are similar to i386. Is anybody
actually using it? I believe that the library is installed in the
wrong location. There may still be issues with the testsuite using
the installed library rather than the build library.
Java: the library doesn't build. Needs porting for both parisc-linux
and hpux, I believe.
C++: lack of weak symbol support causes some problems with template
instantiation under hpux. Not sure how this is working under parisc-linux
but weak support should help.
Fortran: there are some bugs that need work on main. Stick with 3.0.x
At least based on the testsuite results, C++ STL threads work under hpux.
Don't know of any issues under linux. The primary problem is locking.
It would be useful if the gcc testsuite were run on various parisc-linux
linux configurations: 1.X and 2.0 processors, 32 and 64 bit, gcc mainline
and 3.0.2. Then, post the results using the contrib/test-summary script to
email@example.com. This would help a lot to determine the status
of things for gcc under parisc-linux. Volunteer(s)?
I am planning to set up a 64-bit test system in the near future.
J. David Anglin firstname.lastname@example.org
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)