Dave Korn wrote:
> On 18 April 2007 10:29, Andrew Marlow wrote:
> 
>> Recently, on comp.sys.prime a PRIMOS emulator was announced. It is 
>> for quite an old version of Primos (rev 19.2) before Prime puts its 
>> weight behind an official C compiler. We on this ng are trying to 
>> track down an unofficial C compiler that was around at that time.
>> But someone suggested that maybe GCC might, at some point, be able to

>> emit code for PRIMOS. This would be PMA (Prime Macro Assembler).
>> I really hope that this could be done. I wonder what the chances are.
> 
>   If some of the newsgroup guys want to volunteer to do it, everyone 
> here will offer help and advice.

This is good to know, thanks :-)

> If you want to
> hire a contractor to do it, that would work too.  

That is not going to happen.

> But the
> odds of some random gcc hacker with no special interest in PRIMOS 
> suddenly deciding to volunteer that amount of time and effort for no 
> reason are ... small.

Er, yes. I don't have the skills myself. I was hoping that maybe some
ex-primates hung around in the GCC ml. Perhaps this was wildly
optimistic.

> 
>> Even if this work cannot be done for GCC it would be good to at least

>> get an official statement to that effect (would put us Primates out 
>> of our misery..).
> 
>   http://cygwin.com/acronyms#SHTDI
>   http://cygwin.com/acronyms#PTC

There may be some chance of this. In comp.sys.prime it was just
announced that the source for a very early unofficial version of the C
compiler has been found. I wonder if this might be a useful starting
point. Does this ml have a pointer (URL maybe) for any GCC implementing
a new backend documentation that I can point my fellow primates to?
Maybe one of them could use this info in conjunction with the source
that was just discovered.

> 
>> There is an emerald here the size of a plover's egg!
>   plugh!

Nothing happens.

> 
>     cheers,
>       DaveK

Regards,

Andrew Marlow
----
There is an emerald here the size of a plover's egg!
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html


******************************************************************************"
The data and information (collectively called Information) herein is the sole 
property of ICAP.  The Information is confidential, may be legally privileged 
and is intended solely for the use of the individual or entity to whom it is 
addressed.  Unauthorised disclosure, copying or distribution of the Information 
is strictly prohibited and the recipient of the Information shall not 
redistribute the Information in any form to a third party.  If you received 
this Information in error please tell us by reply (or telephone the sender) and 
delete all copies on your system.

References in this Information to ICAP are references to ICAP plc, a company 
incorporated in England with registered number 3611426 whose registered office 
is 2 Broadgate, London, EC2M 7UR and where the context requires, includes its 
subsidiary and associated undertakings.  As applicable, certain companies 
within the ICAP group are authorised and regulated by the Financial Services 
Authority.  Any investment research sent from ICAP will provide an impartial 
and objective assessment of the securities, companies or other matters that are 
the subject of their research and our Conflicts of Interest Management Policy 
regarding investment research can be viewed by requesting a copy from your 
usual contact at ICAP.  Please visit www.icap.com for further regulatory 
information including details regarding the European eCommerce Directive.

*******************************************************************************"
We have taken precautions to minimise the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message. We cannot accept liability for any loss or damage caused by 
software viruses. "
******************************************************************************* 
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                     

Reply via email to