Michael Hawkins | 1 Jul 2012 16:12
Picon
Favicon

SDCC for 80C85

I've this once before but got no response. I would like to see if anyone is interested in helping me develop SDCC for the 80C85. Anyone? Can anyone point me a general direction to begin?

Mike

From: "sdcc-user-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org" <sdcc-user-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
To: sdcc-user <at> lists.sourceforge.net
Sent: Sunday, July 1, 2012 7:19 AM
Subject: Sdcc-user Digest, Vol 74, Issue 1

Send Sdcc-user mailing list submissions to
    sdcc-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.sourceforge.net/lists/listinfo/sdcc-user
or, via email, send a message with subject or body 'help' to
    sdcc-user-request-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org

You can reach the person managing the list at
    sdcc-user-owner <at> lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Sdcc-user digest..."


Today's Topics:

  1. Re: SDCC 3.2.0 Release Candidate 2 (Philipp Klaus Krause)
  2. Re: SDCC 3.2.0 Release Candidate 2 (Claude Sylvain)
  3. Re: SDCC 3.2.0 Release Candidate 2 (Borut Ra?em)
  4. Re: SDCC 3.2.0 Release Candidate 2 (Claude Sylvain)
  5. Re: SDCC 3.2.0 Release Candidate 2 (Borut Ra?em)
  6. Re: SDCC 3.2.0 Release Candidate 3 (Borut Ra?em)
  7. Re: SDCC 3.2.0 Release Candidate 3 (M L)


----------------------------------------------------------------------

Message: 1
Date: Sat, 30 Jun 2012 18:07:58 +0200
From: Philipp Klaus Krause <pkk-dH2bkuHepfc@public.gmane.org>
Subject: Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 2
To: sdcc-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Message-ID: <4FEF245E.4050803-dH2bkuHepfc@public.gmane.org>
Content-Type: text/plain; charset=UTF-8

On 30.06.2012 16:49, Claude Sylvain wrote:

>                       +++
> z80instructionSize() failed to parse line node
> z80instructionSize() failed to parse line node    rst 0x10
> z80instructionSize() failed to parse line node
> z80instructionSize() failed to parse line node
> z80instructionSize() failed to parse line node    rst 0x18
> z80instructionSize() failed to parse line node
> ...
> z80instructionSize() failed to parse line node  di
> z80instructionSize() failed to parse line node  di
>                       +++

The --no-peep must be what makes the difference here. Can you give a
small example file that reproduces the problem? I susprect that the
problem can only occour when there is a combination of inline assembly
and C control structures in one function.

Philipp



------------------------------

Message: 2
Date: Sat, 30 Jun 2012 12:55:24 -0400
From: Claude Sylvain <csylvain-DHvJIA+2X6OFjAsv1I7E3VaTQe2KTcn/@public.gmane.org>
Subject: Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 2
To: sdcc-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Message-ID: <4FEF2F7C.5040905-DHvJIA+2X6OFjAsv1I7E3VaTQe2KTcn/@public.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


On 2012-06-30 12:07, Philipp Klaus Krause wrote:

>
> On 30.06.2012 16:49, Claude Sylvain wrote:
>
>>                       +++
>> z80instructionSize() failed to parse line node
>> z80instructionSize() failed to parse line node    rst 0x10
>> z80instructionSize() failed to parse line node
>> z80instructionSize() failed to parse line node
>> z80instructionSize() failed to parse line node    rst 0x18
>> z80instructionSize() failed to parse line node
>> ...
>> z80instructionSize() failed to parse line node  di
>> z80instructionSize() failed to parse line node  di
>>                       +++
>
> The --no-peep must be what makes the difference here. Can you give a
> small example file that reproduces the problem? I susprect that the
> problem can only occour when there is a combination of inline assembly
> and C control structures in one function.
>

Hello Philipp,

- I made a mistake when setting up my built environment.
  The above mentioned errors do not exist with SDCC 3.2.0rc3.


Sorry for this,
Claude






------------------------------

Message: 3
Date: Sat, 30 Jun 2012 20:37:19 +0200
From: Borut Ra?em <borut.razem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 2
To: sdcc-user-5NWGOfrQmnd4wTydcyPnfg@public.gmane.orgceforge.net
Message-ID: <4FEF475F.9060409 <at> gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 30. 06. 2012 16:49, Claude Sylvain wrote:
> On 2012-06-24 14:54, Borut Ra??em wrote:
>
>> SDCC 3.2.0 Release Candidate 2 source, doc and binary packages for x86
>> Linux, 32 bit Windows and universal Mac OS X are available  in
>> corresponding folders at:
>> http://sourceforge.net/projects/sdcc/files
>>
>> If you find a mistake, please send a mail to sdcc-devel mailing list
>> sdcc-devel-5NWGOfrQmnetEtDZOKyKiw@public.gmane.orgrge.net.
>>
>> I would appreciate any reports about a success or failure of running
>> pre-compiled binary packages.
>>
> - Installed SDCC 3.2.0 RC3 (not RC2) on a Windows 7 Professional
>    64-bit computer, and the result is the following:
>
>     - Installer suggest "C:\Program Files\SDCC" instead
>       of "C:\Program Files (x86)\SDCC".
>       Have to modify manually to "C:\Program Files (x86)\SDCC" to
>       have SDCC installed in 32-bit programs directory.

Claude, I uploaded a corrected version at
http://sourceforge.net/projects/sdcc/files/sdcc-win32/3.2.0/sdcc-3.2.0-rc3a-setup.exe.
Can you please try it and let me know if it works for you?

Thanks for the report!

Borut



------------------------------

Message: 4
Date: Sat, 30 Jun 2012 15:28:20 -0400
From: Claude Sylvain <csylvain-DHvJIA+2X6OFjAsv1I7E3VaTQe2KTcn/@public.gmane.org>
Subject: Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 2
To: sdcc-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Message-ID: <4FEF5354.70509-DHvJIA+2X6OFjAsv1I7E3VaTQe2KTcn/@public.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed


On 2012-06-30 14:37, Borut Ra?em wrote:

>
> On 30. 06. 2012 16:49, Claude Sylvain wrote:
>
>> On 2012-06-24 14:54, Borut Ra?em wrote:
>>
>>> SDCC 3.2.0 Release Candidate 2 source, doc and binary packages for x86
>>> Linux, 32 bit Windows and universal Mac OS X are available  in
>>> corresponding folders at:
>>> http://sourceforge.net/projects/sdcc/files
>>>
>>> If you find a mistake, please send a mail to sdcc-devel mailing list
>>> sdcc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org.
>>>
>>> I would appreciate any reports about a success or failure of running
>>> pre-compiled binary packages.
>>>
>> - Installed SDCC 3.2.0 RC3 (not RC2) on a Windows 7 Professional
>>      64-bit computer, and the result is the following:
>>
>>     - Installer suggest "C:\Program Files\SDCC" instead
>>       of "C:\Program Files (x86)\SDCC".
>>       Have to modify manually to "C:\Program Files (x86)\SDCC" to
>>       have SDCC installed in 32-bit programs directory.
>
> Claude, I uploaded a corrected version at
>
http://sourceforge.net/projects/sdcc/files/sdcc-win32/3.2.0/sdcc-3.2.0-rc3a-setup.exe.
> Can you please try it and let me know if it works for you?
>

Hello Borut,

- Just tested the new setup file ("sdcc-3.2.0-rc3a-setup.exe"),
  and the install directory bug is fixed.
  i.e.: Installing in the correct directory
  ("C:\Program Files (x86)\SDCC").


Claude





------------------------------

Message: 5
Date: Sat, 30 Jun 2012 22:38:49 +0200
From: Borut Ra?em <borut.razem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 2
To: sdcc-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Message-ID:
    <CADXbRGioiXZfM=Aaf7PNsbo=RXtDMnijWPPVgH2xmSJrJUWreQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Content-Type: text/plain; charset="utf-8"

On Sat, Jun 30, 2012 at 9:28 PM, Claude Sylvain <
csylvain-DHvJIA+2X6OFjAsv1I7E3VaTQe2KTcn/@public.gmane.org> wrote:

>
> On 2012-06-30 14:37, Borut Ra?em wrote:
>
>  >
>  > On 30. 06. 2012 16:49, Claude Sylvain wrote:
>  >
>  >> On 2012-06-24 14:54, Borut Ra?em wrote:
>  >>
>  >>> SDCC 3.2.0 Release Candidate 2 source, doc and binary packages for x86
>  >>> Linux, 32 bit Windows and universal Mac OS X are available  in
>  >>> corresponding folders at:
>  >>> http://sourceforge.net/projects/sdcc/files
>  >>>
>  >>> If you find a mistake, please send a mail to sdcc-devel mailing list
>  >>> sdcc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org.
>  >>>
>  >>> I would appreciate any reports about a success or failure of running
>  >>> pre-compiled binary packages.
>  >>>
>  >> - Installed SDCC 3.2.0 RC3 (not RC2) on a Windows 7 Professional
>  >>      64-bit computer, and the result is the following:
>  >>
>  >>    - Installer suggest "C:\Program Files\SDCC" instead
>  >>      of "C:\Program Files (x86)\SDCC".
>  >>      Have to modify manually to "C:\Program Files (x86)\SDCC" to
>  >>      have SDCC installed in 32-bit programs directory.
>  >
>  > Claude, I uploaded a corrected version at
>  >
>
> http://sourceforge.net/projects/sdcc/files/sdcc-win32/3.2.0/sdcc-3.2.0-rc3a-setup.exe
> .
>  > Can you please try it and let me know if it works for you?
>  >
>
> Hello Borut,
>
> - Just tested the new setup file ("sdcc-3.2.0-rc3a-setup.exe"),
>    and the install directory bug is fixed.
>    i.e.: Installing in the correct directory
>    ("C:\Program Files (x86)\SDCC").


Great!

Thanks again for the report.

Borut
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 6
Date: Sat, 30 Jun 2012 22:56:55 +0200
From: Borut Ra?em <borut.razem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 3
To: Sdcc-User <sdcc-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,     Sdcc-Devel
    <sdcc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Message-ID: <4FEF6817.7000202-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Content-Type: text/plain; charset=windows-1252; format=flowed

Claude Sylvain found an error in sdcc installer: installer suggests
"C:\Program Files\SDCC" instead of "C:\Program Files (x86)\SDCC". I
repacked the sdcc 3.2.0 RC3 Windows setup package and renamed it to
sdcc-3.2.0-rc3a-setup.exe. You can find the package at:
http://sourceforge.net/projects/sdcc/files/sdcc-win32/3.2.0/sdcc-3.2.0-rc3a-setup.exe/download.

P.S.: the Windows setup package content is exactly the same as for RC3.
This change does not affect packages for other platforms.

Borut

On 29. 06. 2012 18:56, Borut Ra?em wrote:
> SDCC 3.2.0 Release Candidate 3 source, doc and binary packages for x86
> Linux, 32 bit Windows and universal Mac OS X are available  in
> corresponding folders at:
> http://sourceforge.net/projects/sdcc/files
>
> If you find a mistake, please send a mail to sdcc-devel mailing list
> sdcc-devel-5NWGOfrQmnetEtDZOKyKiw@public.gmane.orgrge.net.
>
> I would appreciate any reports about a success or failure of running
> pre-compiled binary packages. I'm specially interested on Mac OS X ppc
> architecture since I can not test it. Please let me know if the
> pre-built binaries run on this platform.
>
> Bout





------------------------------

Message: 7
Date: Sun, 1 Jul 2012 13:19:23 +0200
From: M L <maricolist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 3
To: sdcc-user-5NWGOfrQmncRDUWM+popnw@public.gmane.orgforge.net
Message-ID:
    <CAATe3A8Kh2SX1Yfrc+wPpQmin7W6HHT3vxRq+5AGDbkRnbN+Qg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Content-Type: text/plain; charset=ISO-8859-2

Does updated manual says now anything about NOT SUPPORTED option
--stack-auto on pic16 port? I wasted many days for searching why libs
compiled with --stack-auto won't work correctly. There is only one or
two posts on list with such warning, manual in pic16 chapter says
nothing about this problem.

regards,
--
Marico


2012/6/29, Borut Ra?em <borut.razem <at> gmail.com>:
> SDCC 3.2.0 Release Candidate 3 source, doc and binary packages for x86
> Linux, 32 bit Windows and universal Mac OS X are available  in
> corresponding folders at:
> http://sourceforge.net/projects/sdcc/files
>
> If you find a mistake, please send a mail to sdcc-devel mailing list
> sdcc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org.
>
> I would appreciate any reports about a success or failure of running
> pre-compiled binary packages. I'm specially interested on Mac OS X ppc
> architecture since I can not test it. Please let me know if the
> pre-built binaries run on this platform.
>
> Bout
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Sdcc-user mailing list
> Sdcc-user-5NWGOfrQmncRDUWM+popnw@public.gmane.orgforge.net
> https://lists.sourceforge.net/lists/listinfo/sdcc-user
>



------------------------------

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

------------------------------

_______________________________________________
Sdcc-user mailing list
Sdcc-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/sdcc-user


End of Sdcc-user Digest, Vol 74, Issue 1
****************************************


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Sdcc-user mailing list
Sdcc-user@...
https://lists.sourceforge.net/lists/listinfo/sdcc-user
Andy Peters | 1 Jul 2012 20:50

Re: SDCC for 80C85

On Jul 1, 2012, at 10:12 AM, Michael Hawkins wrote:

> I've this once before but got no response. I would like to see if anyone is interested in helping me develop
SDCC for the 80C85. Anyone? Can anyone point me a general direction to begin?

Serious questions:

Does anyone still use the 80C85?

Can you even buy one?

Why bother, when you can buy one of the nifty Silicon Labs 8051s with built-in debug and flash and all of that?

-a
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Dave McGuire | 1 Jul 2012 21:52

Re: SDCC for 80C85

On 07/01/2012 02:50 PM, Andy Peters wrote:
>> I've this once before but got no response. I would like to see if anyone is interested in helping me develop
SDCC for the 80C85. Anyone? Can anyone point me a general direction to begin?
> 
> Serious questions:
> 
> Does anyone still use the 80C85?

  [stepping in as another interested voice]

  I do, and I know two people who regularly build 8085-based systems.
They are primarily noncommercial "hobby" projects, but let's keep in
mind that SDCC is regularly used for both commercial AND hobby projects.
 The hobby projects are every bit as "valid" and important to SDCC's
userbase, and by extension, to the SDCC project itself.

> Can you even buy one?

  New old stock, yes, readily.  Used, even more readily.

> Why bother, when you can buy one of the nifty Silicon Labs 8051s with built-in debug and flash and all of that?

  Umm, because the OP wants to use an 8085?

          -Dave

--

-- 
Dave McGuire, AK4HZ
New Kensington, PA

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Philipp Klaus Krause | 1 Jul 2012 22:05
Picon

Re: SDCC for 80C85

On 01.07.2012 16:12, Michael Hawkins wrote:
> Can
> anyone point me a general direction to begin?

Look at the structure of the existing ports: Is the 8085 similar enough
to one so th eports can share a lot of code (hc08 and s08 similar enough
to each other; z80, z180, gbz80, r2k and r3ka are similar enough to each
other).
If not you need to write a new backend. Look at the exisiting ones
first. The main things you will need are code generation and register
allocation. Other stuff, such as the peephole optimizer rules and
optimized library functions should be done later, once the port is
capable of producing working code and passes the regression tests.
You'll also need an assembler and simulator. Look at sdas and ucsim for
example if you need to write them.

Philipp

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Borut Ražem | 1 Jul 2012 22:28
Picon
Gravatar

Re: SDCC for 80C85

On Sun, Jul 1, 2012 at 10:05 PM, Philipp Klaus Krause <pkk-dH2bkuHepfc@public.gmane.org> wrote:
On 01.07.2012 16:12, Michael Hawkins wrote:
> Can
> anyone point me a general direction to begin?

Look at the structure of the existing ports: Is the 8085 similar enough
to one so th eports can share a lot of code (hc08 and s08 similar enough
to each other; z80, z180, gbz80, r2k and r3ka are similar enough to each
other).
If not you need to write a new backend. Look at the exisiting ones
first. The main things you will need are code generation and register
allocation. Other stuff, such as the peephole optimizer rules and
optimized library functions should be done later, once the port is
capable of producing working code and passes the regression tests.
You'll also need an assembler and simulator. Look at sdas and ucsim for
example if you need to write them.

ASXXXX already includes the 8085 assembler & linker, so it has to be re-merged to sdas & sdld.

Borut
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Sdcc-user mailing list
Sdcc-user@...
https://lists.sourceforge.net/lists/listinfo/sdcc-user
Dave McGuire | 1 Jul 2012 22:29

Re: SDCC for 80C85

On 07/01/2012 04:05 PM, Philipp Klaus Krause wrote:
>> Can
>> anyone point me a general direction to begin?
> 
> Look at the structure of the existing ports: Is the 8085 similar enough
> to one so th eports can share a lot of code (hc08 and s08 similar enough
> to each other; z80, z180, gbz80, r2k and r3ka are similar enough to each
> other).

  The Z80 and the 8085 are both outgrowths of the 8080.

  The Z80's instruction set is a superset of that of the 8080, and it
can run 8080 code unmodified.  The same applies to the 8085 the
exception of two "new" instructions that were added to the 8085 over the
8080 instruction set.

  If the code generation backend can simply be prevented from issuing
certain instructions (namely the ones that the Z80 implements over the
8080) it will generate 8080 code, which will run unmodified on an 8085.

  Later, it may be possible to allow for the use of the 8085's two
additional instructions, perhaps via the peephole optimizer.  I don't
recall what those two additional instructions do, or if they're worth
bothering with.

             -Dave

--

-- 
Dave McGuire, AK4HZ
New Kensington, PA

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Indy Sams | 1 Jul 2012 22:16

Re: SDCC for 80C85

On 01.07.2012 16:12, Michael Hawkins wrote:
> Can
> anyone point me a general direction to begin?

	You could take the Z80 target and strip out anything that wasn't in the 8080.
	From there you would have an 8080 target and could add the extra 8085 instructions.
	According to wikipedia: "Only a few minor instructions were new to the 8085 above the 8080 set."

Best regards,
 Indy Sams

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Philipp Klaus Krause | 3 Jul 2012 00:57
Picon

Re: SDCC for 80C85

On 01.07.2012 22:16, Indy Sams wrote:
> On 01.07.2012 16:12, Michael Hawkins wrote:
>> Can
>> anyone point me a general direction to begin?
> 
> 	You could take the Z80 target and strip out anything that wasn't in the 8080.
> 	From there you would have an 8080 target and could add the extra 8085 instructions.
> 	According to wikipedia: "Only a few minor instructions were new to the 8085 above the 8080 set."

>From a wuick look at the instruction set, gbz80 seems to be closer to
8051 than z80.

Philipp

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Philipp Klaus Krause | 3 Jul 2012 00:57
Picon

Re: SDCC for 80C85

On 01.07.2012 22:16, Indy Sams wrote:
> On 01.07.2012 16:12, Michael Hawkins wrote:
>> Can
>> anyone point me a general direction to begin?
> 
> 	You could take the Z80 target and strip out anything that wasn't in the 8080.
> 	From there you would have an 8080 target and could add the extra 8085 instructions.
> 	According to wikipedia: "Only a few minor instructions were new to the 8085 above the 8080 set."

>From a quick look at the instruction set, gbz80 seems to be closer to
8051 than z80.

Philipp

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Gmane