From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] wishlist projects, looking for volunteers
Date: Mon, 29 Apr 2002 23:21:37 -0700 [thread overview]
Message-ID: <20020430062137.GF30370@tausq.org> (raw)
Hi all,
Just thought I'd post a list of some interesting (IMHO) user-space
projects for parisc-linux. Feel free to volunteer on anything you
find interesting :-) many of these are good ways to learn things about
an OS/architecture that you don't usually have a chance to do so on more
established platforms. Plus there are lots of people (on this list) who
are willing to answer questions :-)
binutils related
- for hppa64-linux binutils, the linker is always putting dynamic
sections into the resulting binary, even though they are not always
needed. there is a sketch of how to fix this at
http://lists.parisc-linux.org/pipermail/parisc-linux/2002-April/016049.html
- hppa's gas can only be compiled as 32-bit only or 64-bit only. it
would be nice to make it so that it can be compiled to do both (mode
chosen using a command line switch). this is how sparc handles mixed
32-bit/64-bit environments
gdb related
- gdb doesn't work very well on hppa, single stepping with step/next
often does not work (looks like it can't find the stopping point for
the next statement). needs to be investigated and fixed
- gdb doesn't recognize the dwarf debug info that you get with
gcc-3.1/gcc-3.2. needs to be enhanced (i think Dave might have already
done some work in this area)
- we are also in need of a hppa gdb maintainer. anyone interested? :-)
gcc related
- The debian gcc package currently does not build 64-bit compilers. this
shouldn't be too hard to fix (can use sparc as a template), just needs
some experimentation to get it packaged properly
Java
- kaffe port to parisc-linux. i got the interpreter working (sorta) but
many things don't yet work. would be a good project to learn about
JITs and such...
ltrace
- this is a function-call level tracer (as opposed to strace, which is
more on the syscall level). The current ltrace source has some
assumptions about ELF relocation layout that doesn't work on hppa. It
shouldn't be *hard* to fix this if you understand how pa relocation
stubs are generated...
glibc
- there seems to be a problem with the loader going into an infinite
loop when programs are linked with certain libraries that are linked
against libpthread. Helge had mentioned to me that he's seen this with
KDE, also things that are linked against the plib library seems to
have this problem...
c++ fixing
- http://auric.debian.org/~tausq/buildd/hppa-latest.html has a list of
debian packages that don't yet build on hppa (the ones that are listed
as "Failed"). many of these are c++ packages that are not coded
correctly and don't work with the stricter c++ standard enforced by
the 3.x compilers. try to fix these and file bugs...
i'm sure there are other things i'm missing.....
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next reply other threads:[~2002-04-30 6:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 6:21 Randolph Chung [this message]
2002-05-02 17:15 ` [parisc-linux] wishlist projects, looking for volunteers Richard Hirst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020430062137.GF30370@tausq.org \
--to=randolph@tausq.org \
--cc=parisc-linux@parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox