Article View: comp.sys.acorn.tech
Article #704Formation of working group to port GCC 2.3.2 to RISCOS
From: Jordan K. Hubbard
Date: Sat, 19 Dec 1992 01:34
Date: Sat, 19 Dec 1992 01:34
56 lines
2972 bytes
2972 bytes
Hello,
As some of you know, I've recently taken up the task of adapting the
RISCiX port of gcc 2.3.2 to the RISCOS environment. I'm currently
targeting 3.1, but I don't see any particular reason (at this time)
why it won't be equally usable under 2.0.
I've taken it up for four reasons:
1. I already use gcc on daily 6 platforms (Amiga, 386BSD, SUNOS 4.1.2,
HPUX, AIX & PC532/Mach) and very much enjoy being able to standardize
on one compiler.
2. I've got a fair bit of experience with gcc, having done the Symmetric
port, and do a bit of ongoing work tweaking the PC532 version. I've
also been using it regularly since version 1.21.
3. 2.3.2 also supports C++, which is my current language of choice (despite
its somewhat massive flaws :-) and I don't have many alternatives on
the Archimedes.
4. I'd really enjoy porting it to the Archimedes.
Now, this picture is unfortunately not without flaws.
For one, I'm a fairly new Arch user and have a lot to learn about the
system (and my 3.1 PRMS have not yet arrived - ARGH). I'm hoping to
find other people who know a lot about AOF format to deal with the
issues of linkage and libraries. I am currently working with the
author of !AS (who is somewhat busy at the moment) to more closely
target his assembler. This is really not a problem for me, and I feel
confident that I can beat gcc into generating code that !AS largely
likes. The problems will arise when it comes time to link the objects
together. This is where I'm hoping other folks can come to my rescue
with a GPL/PUBLIC DOMAIN solution. Saying we should use Acorn's
linker isn't going to cut it - the entire development system MUST be
available to anyone, completely free of charge.
Secondly, I have limited time, with several other GNU/PD projects
rotting in my "in box" that I really need to spend some time on as
well. I will not be able to work full time on this, but I am willing
to coordinate and harass members of the group often enough to ensure
that progress doesn't grind to a complete halt! :-)
I think we have a very good start with the RISCiX port, and I'm quite
comfortable with hacking on the back end of 2.3.2. Let's get gcc on
the Arch and finally have a decent C development environment that
doesn't cost and arm and a leg.
Comments?
Jordan
--
Jordan Hubbard Lotus Development Ireland jkh@whisker.lotus.ie
I DO NOT SPEAK FOR LOTUS - IT HAS PLENTY OF LAWYERS TO DO THAT FOR IT ALREADY
Technical Details
Message-ID:
<JKH.92Dec19013413@whisker.lotus.ie>Path:
arc1-ca.pugleaf.net!sparky!uunet!mcsun!ieunet!dec4ie.ieunet.ie!jkhShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.acorn.tech Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!ieunet!dec4ie.ieunet.ie!jkh From: jkh@whisker.lotus.ie (Jordan K. Hubbard) Subject: Formation of working group to port GCC 2.3.2 to RISCOS Message-ID: <JKH.92Dec19013413@whisker.lotus.ie> Sender: usenet@ieunet.ie (USENET News System) Nntp-Posting-Host: whisker.lotus.ie Organization: Lotus Development Ireland Distribution: comp Date: Sat, 19 Dec 1992 01:34:13 GMT Lines: 56