[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pcc-list
Subject:    Re: [Pcc] Any future plans on existing sparc64 port?
From:       David Crawshaw <david.crawshaw () gmail ! com>
Date:       2014-03-24 21:39:01
Message-ID: CAF34+hvk5sdyXGUJBmHfnr-9wsZj8iWr=q9CfYO7tuMt_cCFbA () mail ! gmail ! com
[Download RAW message or body]

Sorry, I'm not planning to work on it any more.

On Thu, Feb 20, 2014 at 8:06 AM, Artem Falcon <lomka@gero.in> wrote:
> 20 февр. 2014 г., в 15:51, Anders Magnusson <ragge@ludd.ltu.se> \
> написал(а): 
> > Hi,
> > 
> > Artem Falcon skrev 2014-02-16 07:31:
> > > 
> > > ...
> > > % as -v
> > > GNU assembler version 2.15
> > > % cc -S domainname.c
> > > % cat domainname.s
> > > . section .rodata
> > > .type @(#) Copyright (c) 1988, 1993\012\011The Regents of the
> > > University of California.  All rights reserved.\012,#object
> > > .size @(#) Copyright (c) 1988, 1993\012\011The Regents of the
> > > University of California.  All rights reserved.\012,99
> > > ...
> > This was really odd, something is calling the wrong subroutine somewhere I assume
> > > 
> > > So my questions are: any plans to revive the sparc64 port and is it
> > > hard to eliminate these remaining (maybe more to come) issues?
> > > 
> > Not in the near future unfortunalely, unless someone steps up and want to fix it. \
> > I myself is unfortunately really behind when it comes to pcc, and have never been \
> > looking at the sparc architecture. 
> > Note that these faults you show are usually quite simple to fix if you know the \
> > architecture. 
> > -- Ragge
> 
> Thanks guys! I'll also wait for a response from David Crawshaw.
> Seems he was the only person behind sparc support in pcc.
> 
> --
> dukzcry
_______________________________________________
Pcc mailing list
Pcc@lists.ludd.ltu.se
http://lists.ludd.ltu.se/cgi-bin/mailman/listinfo/pcc


[prev in list] [next in list] [prev in thread] [next in thread]