Jump to content

NEC V60: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
It's Hewlett-Packard, not "Hewlett Packard".
checked some links and URLs. +hyphen(s).
Line 4: Line 4:
| image = NEC V60 die.jpg
| image = NEC V60 die.jpg
| image_size =
| image_size =
| caption = Die shot of NEC V60 microprocessor<br/>Name "V60 D70616" in bottom center
| caption = Die shot of NEC V60 microprocessor<br>Name "V60 D70616" in bottom center
| manuf1 = [[NEC]]
| manuf1 = [[NEC]]
| produced-start = V60: 1986<br/>V70: 1987<br/>V80: 1989<br/>AFPP: 1989
| produced-start = V60: 1986<br>V70: 1987<br>V80: 1989<br>AFPP: 1989
| produced-end =
| produced-end =
| slowest = V60: 16&nbsp;MHz<br/>V70: 20/25&nbsp;MHz<br/>V80: 25/33&nbsp;MHz<br/>AFPP: 20
| slowest = V60: 16&nbsp;MHz<br>V70: 20/25&nbsp;MHz<br>V80: 25/33&nbsp;MHz<br>AFPP: 20
| slow-unit =&nbsp;MHz
| slow-unit =&nbsp;MHz
| size-from = V60: 1.5/1.2 μm<br/>V70: 1.5/1.2 μm<br/>V80: 0.8 μm<br/>AFPP: 1.2 μm
| size-from = V60: 1.5/1.2 μm<br>V70: 1.5/1.2 μm<br>V80: 0.8 μm<br>AFPP: 1.2 μm
| transistors = V60: 375K<br/>V70: 385K<br/>V80: 980K<br/>AFPP: 433K
| transistors = V60: 375K<br>V70: 385K<br>V80: 980K<br>AFPP: 433K
| arch = NEC V60-V80<ref name="V60-Prog-Ref-Man"/>
| arch = NEC V60-V80<ref name=V60-Prog-Ref-Man/>
| microarch = "V60/V70", "V80"
| microarch = "V60/V70", "V80"
| numinstructions = V60/V70:&nbsp;119<br/>V80:&nbsp;123
| numinstructions = V60/V70:&nbsp;119<br>V80:&nbsp;123
| extensions = V80: atomic
| extensions = V80: atomic
| l1cache = V80: 1K/1K
| l1cache = V80: 1K/1K
| data-width = V60: 16 (int. 32)<br/>V70: 32<br/>V80: 32
| data-width = V60: 16 (int. 32)<br>V70: 32<br>V80: 32
| address-width = V60: 24 (int. 32)<br/>V70: 32<br/>V80: 32
| address-width = V60: 24 (int. 32)<br>V70: 32<br>V80: 32
| virtual-width = 32 Linear<ref name="V60-Prog-Ref-Man"/>
| virtual-width = 32 Linear<ref name=V60-Prog-Ref-Man/>
| predecessor = [[NEC V20|V20-V50]]
| predecessor = [[NEC V20|V20-V50]]
| successor = [[V850|V800&nbsp;Series]]
| successor = [[V850|V800&nbsp;Series]]
| co-processor = AFPP&nbsp;(μPD72691)
| co-processor = AFPP&nbsp;(μPD72691)
| application = [[Embedded system|Embedded]],<br/>[[Minicomputer]],<br/>[[Arcade game]]
| application = [[Embedded system|Embedded]],<br>[[Minicomputer]],<br>[[Arcade game]]
| pack1 = V60:&nbsp;68-pin&nbsp;[[Pin grid array|PGA]]<br/>V60:&nbsp;120-pin&nbsp;[[Quad Flat Package|QFP]]
| pack1 = V60:&nbsp;68-pin&nbsp;[[Pin grid array|PGA]]<br>V60:&nbsp;120-pin&nbsp;[[quad flat package|QFP]]
| pack2 = V70:&nbsp;132-pin&nbsp;[[Pin grid array|PGA]]
| pack2 = V70:&nbsp;132-pin&nbsp;[[Pin grid array|PGA]]
| pack3 = V70:&nbsp;208-pin&nbsp;[[Quad Flat Package|QFP]]
| pack3 = V70:&nbsp;208-pin&nbsp;[[Quad flat package|QFP]]
| pack4 = V80:&nbsp;280-pin&nbsp;[[Pin grid array|PGA]]
| pack4 = V80:&nbsp;280-pin&nbsp;[[Pin grid array|PGA]]
| pack5 = AFPP:&nbsp;68-pin&nbsp;[[Pin grid array|PGA]]
| pack5 = AFPP:&nbsp;68-pin&nbsp;[[Pin grid array|PGA]]
Line 39: Line 39:
}}
}}


The '''NEC V60'''<ref name="V60-Prog-Ref-Man"/><ref name="maruzen"/> is a [[Complex instruction set computer|CISC]] [[microprocessor]] manufactured by [[NEC]] starting in 1986. Several improved versions were introduced with the same [[instruction set architecture]] (ISA), the '''V70''' in 1987, and the '''V80''' and '''AFPP''' in 1989. They were succeeded<ref name="IEIEC-1995"/> by the [[Renesas V850|V800]] product families, which is currently produced by [[Renesas]].
The '''NEC V60'''<ref name=V60-Prog-Ref-Man/><ref name=maruzen/> is a [[complex instruction set computer|CISC]] [[microprocessor]] manufactured by [[NEC]] starting in 1986. Several improved versions were introduced with the same [[instruction set architecture]] (ISA), the '''V70''' in 1987, and the '''V80''' and '''AFPP''' in 1989. They were succeeded<ref name=IEIEC-1995/> by the [[Renesas V850|V800]] product families, which is currently produced by [[Renesas Electronics]].


The V60 family includes a [[floating-point unit]]<ref name="coproc"/> (FPU) and [[memory management unit]] (MMU) and [[real-time operating system]] (RTOS) support for both [[Unix]]-based user-application-oriented systems<ref name="RX-UX-832"/> and [[Industrial TRON|I-TRON]]–based hardware-control-oriented [[embedded system]]s. They can be used in a multi-cpu [[lockstep (computing)|lockstep]] [[fault-tolerant computer system|fault-tolerant mechanism]] named FRM. [[Development tool]]s included [[Ada (programming language)|Ada]] certified system [[#MV-4000|MV-4000]], and an [[in-circuit emulator]] (ICE).
The V60 family includes a [[floating-point unit]]<ref name=coproc/> (FPU) and [[memory management unit]] (MMU) and [[real-time operating system]] (RTOS) support for both [[Unix]]-based user-application-oriented systems<ref name=RX-UX-832/> and [[ITRON project|I-TRON]]–based hardware-control-oriented [[embedded system]]s. They can be used in a multi-cpu [[lockstep (computing)|lockstep]] [[fault tolerance|fault-tolerant mechanism]] named FRM. [[Development tool]]s included [[Ada (programming language)|Ada]] certified system [[#MV-4000|MV-4000]], and an [[in-circuit emulator]] (ICE).


The V60/V70/V80's applications covered a wide area, including [[circuit switching]] [[telephone exchange]]s, [[minicomputer]]s, [[aerospace engineering|aerospace]] [[guidance system]]s,<ref name="akatsuki"/> [[word processor]]s, [[Industrial Computers|industrial computer]]s, and various [[arcade game]]s.
The V60/V70/V80's applications covered a wide area, including [[circuit switching]] [[telephone exchange]]s, [[minicomputer]]s, [[aerospace engineering|aerospace]] [[guidance system]]s,<ref name=akatsuki/> [[word processor]]s, [[industrial computer]]s, and various [[arcade game]]s.


== {{anchor}}Introduction ==
=={{anchor}}Introduction==
NEC V60<ref name="maruzen"/><ref name="V60-Prog-Ref-Man"/> is a [[Complex instruction set computer|CISC]]<ref name="pj"/> processor manufactured by [[NEC]] starting in 1986.<ref name="SIG-ARC-043"/> It was the first 32-bit [[microprocessor|general-purpose microprocessor]] commercially available in Japan.<ref name="trend"/>
NEC V60<ref name=maruzen/><ref name=V60-Prog-Ref-Man/> is a [[complex instruction set computer|CISC]]<ref name=pj/> processor manufactured by [[NEC]] starting in 1986.<ref name=SIG-ARC-043/> It was the first 32-bit general-purpose [[microprocessor]] commercially available in Japan.<ref name=trend/>


Based on a relatively traditional design for the period,<ref name="MIPS-1984"/><ref name="RISC-II"/><ref name="R2000"/><ref name="First-SPARC"/><ref name="i860"/> the V60 was a radical departure from NEC's previous, 16-bit V–series processor, the [[NEC V20|V20-V50]],<ref name="V20-V50-progman"/> which were based on the [[Intel 8086]] model,<ref name="pj"/> although the V60 had the ability to emulate the V20/V30.<ref name="V60-Prog-Ref-Man"/>{{rp|§10}}
Based on a relatively traditional design for the period,<ref name=MIPS-1984/><ref name=RISC-II/><ref name=R2000/><ref name=First-SPARC/><ref name=i860/> the V60 was a radical departure from NEC's previous, 16-bit V–series processor, the [[NEC V20|V20-V50]],<ref name=V20-V50-progman/> which were based on the [[Intel 8086]] model,<ref name=pj/> although the V60 had the ability to emulate the V20/V30.<ref name=V60-Prog-Ref-Man/>{{rp|§10}}


According to NEC's documentation, this [[Computer architecture|computer architectural]] change was due to the increasing demands for, and the diversity of, [[high-level programming language]]s. Such trends called for a processor with both improved performance, achieved by doubling the bus width to 32 bits, and with greater flexibility facilitated by having a large number of general-purpose registers.<ref name="maruzen"/><ref name="V60-Prog-Ref-Man"/> These were common features of [[Reduced instruction set computer|RISC]] chips.<ref name="Computer-Architecture-4thEd"/> At the time, a transition from CISC to [[Reduced instruction set computer|RISC]] seemed to bring many benefits for emerging markets.
According to NEC's documentation, this [[computer architecture|computer architectural]] change was due to the increasing demands for, and the diversity of, [[high-level programming language]]s. Such trends called for a processor with both improved performance, achieved by doubling the bus width to 32 bits, and with greater flexibility facilitated by having a large number of general-purpose registers.<ref name=maruzen/><ref name=V60-Prog-Ref-Man/> These were common features of [[reduced instruction set computer|RISC]] chips.<ref name=Computer-Architecture-4thEd/> At the time, a transition from CISC to RISC seemed to bring many benefits for emerging markets.


Today, RISC chips are common, and CISC designs—such as [[x86|Intel's x86]] and the [[Intel 80486|80486]]—which have been mainstream for several decades, internally adopt RISC features in their [[microarchitecture]]s.<ref name="i486-ICCD89"/><ref name="i486-Micro-1990"/> According to [[Pat Gelsinger]], binary backward compatibility for legacy software is more important than changing the ISA.<ref name="CNET-2007"/>
Today, RISC chips are common, and CISC designs—such as [[x86|Intel's x86]] and the [[Intel 80486|80486]]—which have been mainstream for several decades, internally adopt RISC features in their [[microarchitecture]]s.<ref name=i486-ICCD89/><ref name=i486-Micro-1990/> According to [[Pat Gelsinger]], binary backward compatibility for legacy software is more important than changing the ISA.<ref name=CNET-2007/>


== {{anchor|V60|D70616|μPD70616|.mu.PD70616}}Overview ==
=={{anchor|V60|D70616|μPD70616|.mu.PD70616}}Overview==


=== Instruction set ===
===Instruction set===
The V60 ({{aka}} μPD70616) retained a [[Complex instruction set computer|CISC]] architecture.<ref name="Wade, 1996"/> Its manual describes their architecture as having "features of high-end [[Mainframe computer|mainframe]] and [[supercomputer]]s", with a fully [[orthogonal instruction set]] that includes non-uniform-length instructions, memory-to-memory operations that include string manipulation, and complex operand-addressing schemes.<ref name="V60-Prog-Ref-Man"/><ref name="maruzen"/><ref name="Computer-Architecture-4thEd"/>
The V60 ({{aka}} μPD70616) retained a [[complex instruction set computer|CISC]] architecture.<ref name=Wade1996/> Its manual describes their architecture as having "features of high-end [[mainframe computer|mainframe]] and [[supercomputer]]s", with a fully [[orthogonal instruction set]] that includes non-uniform-length instructions, memory-to-memory operations that include string manipulation, and complex operand-addressing schemes.<ref name=V60-Prog-Ref-Man/><ref name=maruzen/><ref name=Computer-Architecture-4thEd/>


=== Family ===
===Family===
The V60 operates as a 32 bit processor internally, whilst externally providing 16-bit data, and 24-bit address, buses. In addition, the V60 has 32 32-bit general-purpose registers.<ref name="V60-Prog-Ref-Man"/>{{rp|§1}}
The V60 operates as a 32-bit processor internally, while externally providing 16-bit data, and 24-bit address, buses. In addition, the V60 has 32 32-bit general-purpose registers.<ref name=V60-Prog-Ref-Man/>{{rp|§1}}
Its basic [[Computer architecture|architecture]] is used in several variants. The V70 (μPD70632), released in 1987, provides 32-bit external buses. Launched in 1989, the V80 (μPD70832)<ref name="overview"/> is the culmination of the series: having on-chip caches, a branch predictor, and less reliance on [[microcode]] for complex operations.<ref name="micro1990"/>
Its basic [[computer architecture|architecture]] is used in several variants. The V70 (μPD70632), released in 1987, provides 32-bit external buses. Launched in 1989, the V80 (μPD70832)<ref name=overview/> is the culmination of the series: having on-chip caches, a branch predictor, and less reliance on [[microcode]] for complex operations.<ref name=micro1990/>


=== Software ===
===Software===
The [[operating system]]s developed for the V60-V80 series are generally oriented toward [[Real-time operating system|real-time operation]]s. Several OSs were ported to the series, including real-time versions of Unix and I‑TRON.<ref name="rtos1997"/><ref name="32b-itron"/>
The [[operating system]]s developed for the V60-V80 series are generally oriented toward [[real-time operating system|real-time operation]]s. Several OSs were ported to the series, including real-time versions of Unix and I-TRON.<ref name=rtos1997/><ref name=32b-itron/>


Because the V60/V70 was used in various Japanese [[arcade game]]s, their [[instruction set architecture]] is emulated in the [[MAME]] [[Emulator#CPU simulator|CPU simulator]].<ref name="v60-cemu"/> The latest [[open-source software|open-source]] [[source code|code]] is available from the [[GitHub]] [[Repository (version control)|repository]].<ref>{{cite web |title=mamedev/mame |url=https://github.com/mamedev/mame/ |website=[[GitHub]] |access-date=17 May 2020}}</ref>
Because the V60/V70 was used in various Japanese [[arcade game]]s, their [[instruction set architecture]] is emulated in the [[MAME]] [[emulator#CPU simulator|CPU simulator]].<ref name=v60-cemu/> The latest [[open-source software|open-source]] [[source code|code]] is available from the [[GitHub]] [[repository (version control)|repository]].<ref>{{cite web |title=mamedev/mame |website=[[GitHub]] |url=https://github.com/mamedev/mame/ |access-date=17 May 2020}}</ref>


=== FRM ===
===FRM===
All three processors have the FRM (Functional Redundancy Monitoring) synchronous multiple modular [[lockstep (computing)|lockstep]] mechanism, which enables [[fault-tolerant computer system]]s. It requires multiple devices of the same model, one of which then operates in "master mode", while the other devices listen to the master device, in "checker mode". If two or more devices simultaneously output different results via their "fault output" pins, a majority-voting decision can be taken by external circuits. In addition, a recovery method for the mismatched instruction—either "roll-back by retry" or "roll-forward by exception"—can be selected via an external pin.<ref name="IEEE-MICRO-FRM"/><ref name="compcon1988"/><ref name="V60-Prog-Ref-Man"/>{{rp|§11}}<ref name="overview"/><ref name="SIG-ARC-069"/><ref name="V60-Datasheet"/>{{rp|§3-229, 266}}
All three processors have the FRM (Functional Redundancy Monitoring) synchronous multiple modular [[lockstep (computing)|lockstep]] mechanism, which enables [[fault tolerance|fault-tolerant computer system]]s. It requires multiple devices of the same model, one of which then operates in "master mode", while the other devices listen to the master device, in "checker mode". If two or more devices simultaneously output different results via their "fault output" pins, a majority-voting decision can be taken by external circuits. In addition, a recovery method for the mismatched instruction—either "roll-back by retry" or "roll-forward by exception"—can be selected via an external pin.<ref name=IEEE-MICRO-FRM/><ref name=compcon1988/><ref name=V60-Prog-Ref-Man/>{{rp|§11}}<ref name=overview/><ref name=SIG-ARC-069/><ref name=V60-Datasheet/>{{rp|§3-229, 266}}


{| class="wikitable"
{| class="wikitable"
Line 77: Line 77:
| BMODE (FRM) || Input || Select the normal bus (master) mode or FRM operating (checker) mode
| BMODE (FRM) || Input || Select the normal bus (master) mode or FRM operating (checker) mode
|-
|-
| {{overline|BLOCK}} ({{overline|MSMAT}}) || Output || Master output requesting bus lock, i.e. freezing bus operation<br/>Checker output indicating a mismatch has been detected
| {{overline|BLOCK}} ({{overline|MSMAT}}) || Output || Master output requesting bus lock, i.e. freezing bus operation<br>Checker output indicating a mismatch has been detected
|-
|-
| BFREZ || Input || Assertion for freezing bus operation
| BFREZ || Input || Assertion for freezing bus operation
Line 84: Line 84:
|}
|}


== {{anchor|μPD70615|.mu.PD70615|D70615|PS98-145-HMW}}V60 ==
=={{anchor|μPD70615|.mu.PD70615|D70615|PS98-145-HMW}}V60==
The work on V60 processor began in 1982 with about 250 engineers under the leadership of Yoichi Yano,<ref name="dev-story"/> and the processor debuted in February 1986.<ref name="Methé1991"/> It had a six-stage pipeline, built-in memory-management unit, and floating-point arithmetic. It was manufactured using a two-layer aluminum metal CMOS process technology, under a 1.5&nbsp;[[μm]] [[Design rule checking|design rule]], to implement 375,000 transistors on a {{nowrap|13.9 × 13.8 mm<sup>2</sup>}} die.<ref name="SIG-ARC-043"/><ref name="dataquest-1986"/> It operates at 5&nbsp;V and was initially packaged in a 68-pin [[pin grid array|PGA]].<ref name="dataquest-1987"/> The first version ran at 16&nbsp;MHz and attained 3.5 [[Instructions per second#MIPS|MIPS]].<ref name="dataquest-1986"/> Its sample price at launch was set at ¥100,000 ($588.23). It entered full-scale production in August 1986.<ref name="dataquest-1986"/>
The work on V60 processor began in 1982 with about 250 engineers under the leadership of Yoichi Yano,<ref name=dev-story/> and the processor debuted in February 1986.<ref name=Methé1991/> It had a six-stage pipeline, built-in memory-management unit, and floating-point arithmetic. It was manufactured using a two-layer aluminum metal CMOS process technology, under a 1.5&nbsp;[[μm]] [[design rule checking|design rule]], to implement 375,000 transistors on a {{nowrap|13.9 × 13.8 mm<sup>2</sup>}} die.<ref name=SIG-ARC-043/><ref name=dataquest-1986/> It operates at 5&nbsp;V and was initially packaged in a 68-pin [[pin grid array|PGA]].<ref name=dataquest-1987/> The first version ran at 16&nbsp;MHz and attained 3.5 [[instructions per second#MIPS|MIPS]].<ref name=dataquest-1986/> Its sample price at launch was set at ¥100,000 ($588.23). It entered full-scale production in August 1986.<ref name=dataquest-1986/>


[[File:VR_Virtua_Racing.jpg|thumb|Sega ''[[Virtua Racing]]'' based on [[List of Sega arcade system boards#Sega Model 1|''Sega Model 1'']]<br/> ([http://www.retroclinic.com/leopardcats/vrtwin/vrtwin.htm External Link])]]
[[File:VR Virtua Racing.jpg|thumb|Sega ''[[Virtua Racing]]'' based on [[list of Sega arcade system boards#Sega Model 1|''Sega Model 1'']]<br>([http://www.retroclinic.com/leopardcats/vrtwin/vrtwin.htm External Link])]]


{{anchor|70615}}[[Sega]] employed this processor for most of its arcade game sets in the 1990s; both the [[List of Sega arcade system boards#Sega System 32|Sega System 32]] and the [[List of Sega arcade system boards#Sega Model 1|Sega Model 1]] architectures used V60 as their main CPU. (The latter used the lower-cost μPD70615 variant,<ref name="mamedev-model1"/> which doesn't implement V20/V30 emulation and FRM.<ref name="cat95"/>) The V60 was also used as the main CPU in the SSV arcade architecture—so named because it was developed jointly by [[SETA Corporation|Seta]], [[Sammy Corporation|Sammy]], and [[Visco Corporation|Visco]].<ref name="mamedev-ssv"/> Sega originally considered using a 16&nbsp;MHz V60 as the basis for its [[Sega Saturn]] console; but after receiving word that the [[PlayStation (console)|PlayStation]] employed a 33.8&nbsp;MHz [[MIPS architecture|MIPS]] [[R3000|R3000A]] processor, instead chose the dual-[[SuperH|SH-2]] design for the production model.<ref name="ric-tan"/>
{{anchor|70615}}[[Sega]] employed this processor for most of its arcade game sets in the 1990s; both the [[list of Sega arcade system boards#Sega System 32|Sega System 32]] and the [[list of Sega arcade system boards#Sega Model 1|Sega Model 1]] architectures used V60 as their main CPU. (The latter used the lower-cost μPD70615 variant,<ref name=mamedev-model1/> which doesn't implement V20/V30 emulation and FRM.<ref name=cat95/>) The V60 was also used as the main CPU in the SSV arcade architecture—so named because it was developed jointly by [[SETA Corporation|Seta]], [[Sammy Corporation|Sammy]], and [[Visco Corporation|Visco]].<ref name=mamedev-ssv/> Sega originally considered using a 16&nbsp;MHz V60 as the basis for its [[Sega Saturn]] console; but after receiving word that the [[PlayStation (console)|PlayStation]] employed a 33.8&nbsp;MHz [[MIPS architecture|MIPS]] [[R3000|R3000A]] processor, instead chose the dual-[[SuperH|SH-2]] design for the production model.<ref name=ric-tan/>


In 1988, NEC released a kit called PS98-145-HMW<ref name="ps98-145-hmw"/> for [[Unix]] enthusiasts. The kit contained a V60 processor board that could be plugged into selected models of the [[PC-9800 series|PC-9800]] computer series and a distribution of their [[UNIX System V]] port, the [[PC-UX|PC-UX/V]] [[UNIX System&nbsp;V#SVR2|Rel 2.0 (V60)]], on 15 [[Floppy_disk#8-inch_floppy_dis|8-inch floppy disks]]. The suggested retail price for this kit was 450,000 Yen.<ref name="ps98-145-hmw"/> NEC-group companies themselves intensively employed the V60 processor. Their [[telephone exchange|telephone circuit switcher]] (exchange), which was one of the first intended targets, used V60. In 1991, they expanded their [[word processor]] products line with [[:ja:文豪|''Bungou Mini'' (文豪ミニ in Japanese)]] series 5SX, 7SX, and 7SD, which used the V60 for fast [[Computer font#Outline fonts|outline font]] processing, while the main system processor was a 16&nbsp;MHz [[NEC V20#Variants and successors|NEC V33]].<ref>{{YouTube|2kTVKjOWu3I|''Bungou Mini 5RX''}} with [[Computer font#Outline fonts|"high speed outline font smoothing"]] TV CM</ref><ref name="ipsj-bungo"/> In addition, V60 [[microcode]] variants were employed in NEC's MS-4100 [[minicomputer]] series, which was the fastest one in Japan at that time.<ref name="nec-tecj-ms4100"/><ref name="ispj-ms4100"/><ref name="nij-ms4100"/>
In 1988, NEC released a kit called PS98-145-HMW<ref name=ps98-145-hmw/> for [[Unix]] enthusiasts. The kit contained a V60 processor board that could be plugged into selected models of the [[PC-9800 series|PC-9800]] computer series and a distribution of their [[UNIX System V]] port, the [[PC-UX|PC-UX/V]] [[UNIX System&nbsp;V#SVR2|Rel 2.0 (V60)]], on 15 [[floppy disk#8-inch floppy disk|8-inch floppy disks]]. The suggested retail price for this kit was 450,000 Yen.<ref name=ps98-145-hmw/> NEC-group companies themselves intensively employed the V60 processor. Their [[telephone exchange|telephone circuit switcher]] (exchange), which was one of the first intended targets, used V60. In 1991, they expanded their [[word processor]] products line with [[:ja:文豪|''Bungou Mini'' (文豪ミニ in Japanese)]] series 5SX, 7SX, and 7SD, which used the V60 for fast [[computer font#Outline fonts|outline font]] processing, while the main system processor was a 16&nbsp;MHz [[NEC V20#Variants and successors|NEC V33]].<ref>{{YouTube|2kTVKjOWu3I|''Bungou Mini 5RX''}} with [[computer font#Outline fonts|"high speed outline font smoothing"]] TV CM</ref><ref name=ipsj-bungo/> In addition, V60 [[microcode]] variants were employed in NEC's MS-4100 [[minicomputer]] series, which was the fastest one in Japan at that time.<ref name=nec-tecj-ms4100/><ref name=ispj-ms4100/><ref name=nij-ms4100/>


== {{anchor|μPD70632|.mu.PD70632|D70632}}V70 ==
=={{anchor|μPD70632|.mu.PD70632|D70632}}V70==
[[File:UPD70632GD-20 V70 01.JPG|thumb|V70 (μPD70632GD-20) in [[Quad Flat Package|QFP]] packaging, mounted on [[Jaleco]] ''[[:ja:メガシステム32|Mega System32]]'' [[Printed wiring board|PWB]] ]]
[[File:UPD70632GD-20 V70 01.JPG|thumb|V70 (μPD70632GD-20) in [[quad flat package|QFP]] packaging, mounted on [[Jaleco]] ''[[:ja:メガシステム32|Mega System32]]'' [[Printed wiring board|PWB]] ]]


The V70 (μPD70632) improved on the V60 by increasing the external buses to 32 bits, equal to the internal buses. It was also manufactured in 1.5&nbsp;μm with a two-metal layer process. Its {{nowrap|14.35 × 14.24 mm<sup>2</sup>}} die had 385,000 transistors and was packaged in a 132-pin ceramic [[Pin grid array|PGA]]. Its [[Memory management unit|MMU]] had support for [[demand paging]]. Its floating-point unit was [[IEEE 754]] compliant.<ref name="SIG-ARC-069"/> The 20&nbsp;MHz version attained a peak performance of 6.6 MIPS and was priced, at launch in August 1987, at ¥100,000 ($719.42). The initial production capacity was 20,000 units per month.<ref name="dataquest-1987-2"/> A later report describes it as [[Semiconductor device fabrication|fabricated]] in 1.2-micrometer CMOS on a {{nowrap|12.23 × 12.32 mm<sup>2</sup>}} die.<ref name="overview"/> The V70 had a two-cycle non-pipeline (T1-T2) external bus system, whereas that of the V60 operated at 3 or 4 cycles (T1-T3/T4).<ref name="overview"/><ref name="maruzen"/> Of course, the internal units were pipelined.
The V70 (μPD70632) improved on the V60 by increasing the external buses to 32 bits, equal to the internal buses. It was also manufactured in 1.5&nbsp;μm with a two-metal layer process. Its {{nowrap|14.35 × 14.24 mm<sup>2</sup>}} die had 385,000 transistors and was packaged in a 132-pin ceramic [[pin grid array|PGA]]. Its [[memory management unit|MMU]] had support for [[demand paging]]. Its floating-point unit was [[IEEE 754]] compliant.<ref name=SIG-ARC-069/> The 20&nbsp;MHz version attained a peak performance of 6.6 MIPS and was priced, at launch in August 1987, at ¥100,000 ($719.42). The initial production capacity was 20,000 units per month.<ref name=dataquest-1987-2/> A later report describes it as [[semiconductor device fabrication|fabricated]] in 1.2-micrometer CMOS on a {{nowrap|12.23 × 12.32 mm<sup>2</sup>}} die.<ref name=overview/> The V70 had a two-cycle non-pipeline (T1-T2) external bus system, whereas that of the V60 operated at 3 or 4 cycles (T1-T3/T4).<ref name=overview/><ref name=maruzen/> Of course, the internal units were pipelined.


The V70 was used by [[Sega]] in its [[List of Sega arcade system boards#System Multi 32 specifications|System Multi 32]]<ref name="mamedev1"/> and by [[Jaleco]] in its [[:ja:メガシステム32|Mega System 32]]. (See the photo of the V70 mounted on the latter system's [[printed circuit board]].)<ref name="mamedev-mc32"/>
The V70 was used by [[Sega]] in its [[list of Sega arcade system boards#System Multi 32 specifications|System Multi 32]]<ref name=mamedev1/> and by [[Jaleco]] in its [[:ja:メガシステム32|Mega System 32]]. (See the photo of the V70 mounted on the latter system's [[printed circuit board]].)<ref name=mamedev-mc32/>


[[File:H-IIA F17 launching AKATSUKI.jpg|thumb|Liftoff of H-IIA Flight&nbsp;17, part of whose payload was the [[Akatsuki (spacecraft)|Akatsuki spacecraft (Venus Climate Orbiter)]] ]]
[[File:H-IIA F17 launching AKATSUKI.jpg|thumb|Liftoff of H-IIA Flight&nbsp;17, part of whose payload was the [[Akatsuki (spacecraft)|Akatsuki spacecraft (Venus Climate Orbiter)]] ]]


[[JAXA]] embedded its variant of the V70, with the [[ITRON project|I-TRON]] [[RX616]] operating system, in the [[Guidance, navigation, and control|Guidance Control Computer]] of the [[H-IIA]] [[carrier rocket]]s, in satellites such as the [[Akatsuki (spacecraft)|Akatsuki (Venus Climate Orbiter)]], and the [[Kibo (ISS module)|Kibo International Space Station (ISS) module]].<ref name="akatsuki"/><ref name="JAXA-Kibo"/><ref name="Kibo-EDEE"/> The [[H-IIA]] launch vehicles were deployed domestically, in Japan, although their payloads included satellites from foreign countries. As described in ''JAXA's LSI (MPU/ASIC) roadmap'', this V70 variant is designated "32bit MPU (H32/V70)", whose development, probably including the testing (QT) phase, was "from the middle of 1980s to early 1990s".<ref name="jaxa-roadmap"/>{{rp|9}}<ref name="jaxa-status-2013"/> This variant was used until its replacement, in 2013, by the HR5000 64-bit, 25MHz [[microprocessor]], which is based on the [[MIPS architecture#MIPS32/MIPS64|MIPS64-5Kf architecture]],<ref name="MIPS64-5Kf-DS"/> [[Semiconductor device fabrication|fabricated]] by HIREC, whose development was completed around 2011.<ref name="nectech-jaxagcc"/><ref name="jaxa-eee-parts"/><ref name="HIREC-HR5000"/>
[[JAXA]] embedded its variant of the V70, with the [[ITRON project|I-TRON]] [[RX616]] operating system, in the [[Guidance, navigation, and control|Guidance Control Computer]] of the [[H-IIA]] [[carrier rocket]]s, in satellites such as the [[Akatsuki (spacecraft)|Akatsuki (Venus Climate Orbiter)]], and the [[Kibo (ISS module)|Kibo International Space Station (ISS) module]].<ref name=akatsuki/><ref name=JAXA-Kibo/><ref name=Kibo-EDEE/> The [[H-IIA]] launch vehicles were deployed domestically, in Japan, although their payloads included satellites from foreign countries. As described in ''JAXA's LSI (MPU/ASIC) roadmap'', this V70 variant is designated "32bit MPU (H32/V70)", whose development, probably including the testing (QT) phase, was "from the middle of 1980s to early 1990s".<ref name=jaxa-roadmap/>{{rp|9}}<ref name=jaxa-status-2013/> This variant was used until its replacement, in 2013, by the HR5000 64-bit, 25MHz [[microprocessor]], which is based on the [[MIPS architecture#MIPS32/MIPS64|MIPS64-5Kf architecture]],<ref name=MIPS64-5Kf-DS/> [[semiconductor device fabrication|fabricated]] by HIREC, whose development was completed around 2011.<ref name=nectech-jaxagcc/><ref name=jaxa-eee-parts/><ref name=HIREC-HR5000/>


"Space Environment Data Acquisition" for the V70 was done at the Kibo-ISS exposed facility.
"Space Environment Data Acquisition" for the V70 was done at the Kibo-ISS exposed facility.
Line 108: Line 108:
{| class="wikitable"
{| class="wikitable"
|-
|-
! Item !! Part No. !! SEE (Single Event Effect)<br/>Monitored Item
! Item !! Part No. !! SEE (Single Event Effect)<br>Monitored Item
! Result<ref name="Kibo-SEE"/>
! Result<ref name=Kibo-SEE/>
|-
|-
| V70-MPU || [[National Space Development Agency of Japan|NASDA]]<br/>38510/92101xz || [[Single event upset|SEU (Single Event Upset)]]<br/>[[Latch-up|SEL (Single Event Latch-up)]] || Not observed<br/>(—2010/9/30)
| V70-MPU || [[National Space Development Agency of Japan|NASDA]]<br>38510/92101xz || [[Single event upset|SEU (Single Event Upset)]]<br>[[Latch-up|SEL (Single Event Latch-up)]] || Not observed<br>(—2010/9/30)
|}
|}


== {{anchor|μPD70832|.mu.PD70832|D70832}}V80 ==
=={{anchor|μPD70832|.mu.PD70832|D70832}}V80==
The V80 (μPD70832)<ref name="overview"/> was launched in the spring of 1989. By incorporating on-chip caches and a [[branch predictor]], it was declared NEC's [[Intel 486|486]] by ''[[Computer Business Review]]''.<ref name="CBR-1"/><ref name="CBR-2"/> The performance of the V80 was two to four times than that of the V70, depending on application. For example, compared with V70, the V80 had a 32-bit hardware multiplier that reduced the number of cycles required to complete an integer-multiplication machine-instruction from 23 to 9. (For more detailed differences, see the hardware architecture section below.) The V80 was manufactured in a 0.8-micrometer CMOS process on a die area of {{nowrap|14.49 × 15.47 mm<sup>2</sup>}}, implementing 980,000 transistors. It was packaged in a 280-pin [[Pin grid array|PGA]], and operated at 25 and 33&nbsp;MHz with claimed peak performances of 12.5 and 16.5 MIPS, respectively. The V80 had separate 1&nbsp;KB on-die caches for both instructions and data. It had a 64-entry [[branch predictor]], a 5% performance gain being attributed to it. The launch prices of the V80 were cited as equivalent to $1200 for the 33&nbsp;MHz model and $960 for the 25&nbsp;MHz model. Supposedly, a 45&nbsp;MHz model was scheduled for 1990,<ref name="CBR-2"/> but it did not materialize.
The V80 (μPD70832)<ref name=overview/> was launched in the spring of 1989. By incorporating on-chip caches and a [[branch predictor]], it was declared NEC's [[Intel 486|486]] by ''[[Computer Business Review]]''.<ref name=CBR-1/><ref name=CBR-2/> The performance of the V80 was two to four times than that of the V70, depending on application. For example, compared with V70, the V80 had a 32-bit hardware multiplier that reduced the number of cycles required to complete an integer-multiplication machine-instruction from 23 to 9. (For more detailed differences, see the hardware architecture section below.) The V80 was manufactured in a 0.8-micrometer CMOS process on a die area of {{nowrap|14.49 × 15.47 mm<sup>2</sup>}}, implementing 980,000 transistors. It was packaged in a 280-pin [[Pin grid array|PGA]], and operated at 25 and 33&nbsp;MHz with claimed peak performances of 12.5 and 16.5 MIPS, respectively. The V80 had separate 1&nbsp;KB on-die caches for both instructions and data. It had a 64-entry [[branch predictor]], a 5% performance gain being attributed to it. The launch prices of the V80 were cited as equivalent to $1200 for the 33&nbsp;MHz model and $960 for the 25&nbsp;MHz model. Supposedly, a 45&nbsp;MHz model was scheduled for 1990,<ref name=CBR-2/> but it did not materialize.


The V80, with μPD72691 co-FPP and μPD71101 simple [[peripheral]] chips, was used for an [[Industrial PC|industrial computer]] running the [[RX-UX832]] real-time UNIX operating system and a [[X Window System|X11-R4]]-based windowing system.<ref name="Meiden-Jiho-Jul92"/><ref name="Meiden-Jiho-May93"/>
The V80, with μPD72691 co-FPP and μPD71101 simple [[peripheral]] chips, was used for an [[industrial PC|industrial computer]] running the [[RX-UX832]] real-time UNIX operating system and a [[X Window System|X11-R4]]-based windowing system.<ref name=Meiden-Jiho-Jul92/><ref name=Meiden-Jiho-May93/>


== {{anchor|μPD72691|.mu.PD72691|D72691|AFPP}}AFPP (co-FPP) ==
=={{anchor|μPD72691|.mu.PD72691|D72691|AFPP}}AFPP (co-FPP)==
The Advanced Floating Point Processor (AFPP) (μPD72691) is a co-processor for floating-point arithmetic operations.<ref name="Majithi, 1987"/> The V60/V70/V80 themselves can perform floating-point arithmetic, but they are very slow because they lack hardware dedicated to such operations. In 1989, to compensate V60/V70/V80 for their fairly weak floating-point performance, NEC launched this 80-bit floating-point co-processor for 32-bit [[Single-precision floating-point format|single precision]], 64-bit [[Double-precision floating-point format|double precision]], and 80-bit [[extended precision]] operations according to [[IEEE 754]] specifications.<ref name="coproc"/><ref name="overview"/> This chip had a performance of 6.7 [[MFLOPS]], doing vector-[[matrix multiplication]] while operating at 20&nbsp;MHz. It was [[Semiconductor device fabrication|fabricated]] using a 1.2-micrometer double-metal layer CMOS process, resulting in 433,000 transistors on an {{nowrap|11.6 × 14.9 mm<sup>2</sup>}} die.<ref name="coproc"/> It was packaged in a 68-pin [[Pin grid array|PGA]]. This co-processor connected to a V80 via a dedicated bus, to a V60 or V70 via a shared main bus, which constrained peak performance.<ref name="overview"/>
The Advanced Floating Point Processor (AFPP) (μPD72691) is a co-processor for floating-point arithmetic operations.<ref name=Majithi1987/> The V60/V70/V80 themselves can perform floating-point arithmetic, but they are very slow because they lack hardware dedicated to such operations. In 1989, to compensate V60/V70/V80 for their fairly weak floating-point performance, NEC launched this 80-bit floating-point co-processor for 32-bit [[Single-precision floating-point format|single precision]], 64-bit [[double-precision floating-point format|double precision]], and 80-bit [[extended precision]] operations according to [[IEEE 754]] specifications.<ref name=coproc/><ref name=overview/> This chip had a performance of 6.7 [[MFLOPS]], doing vector-[[matrix multiplication]] while operating at 20&nbsp;MHz. It was [[semiconductor device fabrication|fabricated]] using a 1.2-micrometer double-metal layer CMOS process, resulting in 433,000 transistors on an {{nowrap|11.6 × 14.9 mm<sup>2</sup>}} die.<ref name=coproc/> It was packaged in a 68-pin [[pin grid array|PGA]]. This co-processor connected to a V80 via a dedicated bus, to a V60 or V70 via a shared main bus, which constrained peak performance.<ref name=overview/>


== {{anchor|arch}}Hardware architecture ==
=={{anchor|arch}}Hardware architecture==
The V60/V70/V80 shared a basic architecture. They had thirty-two 32-bit [[general-purpose register]]s, with the last three of them commonly used as [[stack pointer]], [[frame pointer]], and [[argument pointer]], which well matched [[High-level programming language|high level language]] [[compiler]]s' [[calling convention]]s.<ref name="SIG-ARC-069"/><ref name="GCC-Internal"/> The V60 and V70 have 119 machine instructions,<ref name="SIG-ARC-069"/> with that number being extended slightly to 123 instructions for the V80. The instructions are of [[Complex instruction set computing|non-uniform length]], between one and 22 bytes,<ref name="V60-Prog-Ref-Man"/> and take two operands, both of which can be addresses in main memory.<ref name="overview"/> After studying the V60's reference manual, [[Paul Vixie]] described it as "a very [[VAX]]-ish arch, with a V20/V30 emulation mode (which[...] means it can run Intel 8086/8088 software)".<ref name="google-groups"/>
The V60/V70/V80 shared a basic architecture. They had thirty-two 32-bit [[general-purpose register]]s, with the last three of them commonly used as [[stack pointer]], [[frame pointer]], and [[argument pointer]], which well matched [[high-level programming language|high level language]] [[compiler]]s' [[calling convention]]s.<ref name=SIG-ARC-069/><ref name=GCC-Internal/> The V60 and V70 have 119 machine instructions,<ref name=SIG-ARC-069/> with that number being extended slightly to 123 instructions for the V80. The instructions are of [[complex instruction set computing|non-uniform length]], between one and 22 bytes,<ref name=V60-Prog-Ref-Man/> and take two operands, both of which can be addresses in main memory.<ref name=overview/> After studying the V60's reference manual, [[Paul Vixie]] described it as "a very [[VAX]]-ish arch, with a V20/V30 emulation mode (which[...] means it can run Intel 8086/8088 software)".<ref name=google-groups/>


The V60–V80 has a built-in [[memory management unit]] (MMU)<ref name="SIG-ARC-043"/><ref name="Majithi, 1987"/> that divides a 4-[[gigabyte|GB]] [[Virtual memory|virtual address space]] into four 1-GB sections, each section being further divided into 1,024 1-[[megabyte|MB]] areas, and each area being composed of 256 4-[[kilobyte|KB]] pages. On the V60/V70, four registers (ATBR0 to ATBR3) store section pointers, but the "area tables entries" (ATE) and [[Memory management unit#Page table entries|page tables entries (PTE)]] are stored in off-chip RAM. The V80 merged the ATE and ATBR registers—which are both on-chip, with only the PTE entries stored in external RAM—allowing for faster execution of [[translation lookaside buffer]] (TLB) misses by eliminating one memory read.<ref name="overview"/>
The V60–V80 has a built-in [[memory management unit]] (MMU)<ref name=SIG-ARC-043/><ref name=Majithi1987/> that divides a 4-[[gigabyte|GB]] [[virtual memory|virtual address space]] into four 1-GB sections, each section being further divided into 1,024 1-[[megabyte|MB]] areas, and each area being composed of 256 4-[[kilobyte|KB]] pages. On the V60/V70, four registers (ATBR0 to ATBR3) store section pointers, but the "area tables entries" (ATE) and [[memory management unit#Page table entries|page tables entries (PTE)]] are stored in off-chip RAM. The V80 merged the ATE and ATBR registers—which are both on-chip, with only the PTE entries stored in external RAM—allowing for faster execution of [[translation lookaside buffer]] (TLB) misses by eliminating one memory read.<ref name=overview/>


The translation lookaside buffers on the V60/70 are 16-entry [[CPU cache#Associativity|fully associative]] with replacement done by [[microcode]]. The V80, in contrast, has a 64-entry 2-way [[set associative]] TLB with replacement done in hardware. TLB replacement took 58 cycles in the V70 and disrupted the pipelined execution of other instructions. On the V80, a TLB replacement takes only 6 or 11 cycles depending on whether the page is in the same area; pipeline disruption no longer occurs in the V80 because of the separate TLB replacement hardware unit, which operates in parallel with the rest of the processor.<ref name="overview"/>
The translation lookaside buffers on the V60/70 are 16-entry [[CPU cache#Associativity|fully associative]] with replacement done by [[microcode]]. The V80, in contrast, has a 64-entry 2-way [[set associative]] TLB with replacement done in hardware. TLB replacement took 58 cycles in the V70 and disrupted the pipelined execution of other instructions. On the V80, a TLB replacement takes only 6 or 11 cycles depending on whether the page is in the same area; pipeline disruption no longer occurs in the V80 because of the separate TLB replacement hardware unit, which operates in parallel with the rest of the processor.<ref name=overview/>


All three processors use the same protection mechanism, with 4 [[Protection ring|protection levels]] set via a [[program status word]], Ring 0 being the privileged level that could access a special set of registers on the processors.<ref name="overview"/>
All three processors use the same protection mechanism, with 4 [[protection ring|protection levels]] set via a [[program status word]], Ring 0 being the privileged level that could access a special set of registers on the processors.<ref name=overview/>


All three models support a triple-mode redundancy configuration with three CPUs used in a [[byzantine fault]]–tolerance scheme with bus freeze, instruction retry, and chip replacement signals.<ref name="overview"/><ref name="compcon1988"/> The V80 added parity signals to its data and address buses.<ref name="overview"/>
All three models support a triple-mode redundancy configuration with three CPUs used in a [[byzantine fault]]–tolerance scheme with bus freeze, instruction retry, and chip replacement signals.<ref name=overview/><ref name=compcon1988/> The V80 added parity signals to its data and address buses.<ref name=overview/>


String operations were implemented in [[microcode]] in the V60/V70; but these were aided by a hardware data [[control unit]], running at full bus speed, in the V80. This made string operations about five times faster in the V80 than in the V60/V70.<ref name="overview"/>
String operations were implemented in [[microcode]] in the V60/V70; but these were aided by a hardware data [[control unit]], running at full bus speed, in the V80. This made string operations about five times faster in the V80 than in the V60/V70.<ref name=overview/>


All floating-point operations are largely implemented in microcode across the processor family and are thus fairly slow. On the V60/V70, the 32-bit floating-point operations take 120/116/137 cycles for addition/multiplication/division, while the corresponding 64-bit floating-point operations take 178/270/590 cycles. The V80 has some limited hardware assist for phases of floating-point operations—e.g. decomposition into sign, exponent, and mantissa—thus its floating-point unit was claimed to be up to three times as effective as that of the V70, with 32-bit floating-point operations taking 36/44/74 cycles and 64-bit operations taking 75/110/533 cycles (addition/multiplication/division).<ref name="overview"/>
All floating-point operations are largely implemented in microcode across the processor family and are thus fairly slow. On the V60/V70, the 32-bit floating-point operations take 120/116/137 cycles for addition/multiplication/division, while the corresponding 64-bit floating-point operations take 178/270/590 cycles. The V80 has some limited hardware assist for phases of floating-point operations—e.g. decomposition into sign, exponent, and mantissa—thus its floating-point unit was claimed to be up to three times as effective as that of the V70, with 32-bit floating-point operations taking 36/44/74 cycles and 64-bit operations taking 75/110/533 cycles (addition/multiplication/division).<ref name=overview/>


== {{anchor|PC-UX/V Rel 2.0 (V60)|Real-time UNIX RX-UX 832|RX-UX 832|RX-UX832|MUSTARD|RX616|NEC RX116|RX116|}}Operating systems ==
=={{anchor|PC-UX/V Rel 2.0 (V60)|Real-time UNIX RX-UX 832|RX-UX 832|RX-UX832|MUSTARD|RX616|NEC RX116|RX116|}}Operating systems==


=== Unix (non-real-time and real-time) ===
===Unix (non-real-time and real-time)===
NEC ported several variants of the [[Unix]] operating system to its V60/V70/V80 processors for user-application-oriented systems, including real-time ones. The first flavor of NEC's [[UNIX System V]] port for V60 was called [[PC-UX/V]] [[UNIX System&nbsp;V#SVR2|Rel 2.0]] (V60).<ref name="PC-UX-R2-V60"/> (Also refer to [[#External links|external link]] photos below.) NEC developed a Unix variant with a focus on real-time operation to run on V60/V70/V80. Called Real-time UNIX RX-UX 832, it has a double-layered kernel structure, with all task scheduling handled by the real-time kernel.<ref name="RX-UX-832"/> A multiprocessor version of RX-UX 832 was also developed, named MUSTARD (Multiprocessor Unix for Embedded Real-Time Systems).<ref name="Suzuki1992"/> The MUSTARD-powered computer prototype uses eight V70 processors. It utilizes FRM function, and can configure and change the configuration of master and checker upon request.<ref name="8-V70-Proc"/><ref>{{cite book |editor-last=Suzuki |editor-first=Norihisa |title=Shared Memory Multiprocessing |url=https://books.google.com/books?id=Hyn9Cqf8PZsC&pg=PA195 |date=1992 |pages=195ff |publisher=MIT Press |isbn=978-026219322-1}}</ref>
NEC ported several variants of the [[Unix]] operating system to its V60/V70/V80 processors for user-application-oriented systems, including real-time ones. The first flavor of NEC's [[UNIX System V]] port for V60 was called [[PC-UX/V]] [[UNIX System&nbsp;V#SVR2|Rel 2.0]] (V60).<ref name=PC-UX-R2-V60/> (Also refer to [[#External links|external link]] photos below.) NEC developed a Unix variant with a focus on real-time operation to run on V60/V70/V80. Called Real-time UNIX RX-UX 832, it has a double-layered kernel structure, with all task scheduling handled by the real-time kernel.<ref name=RX-UX-832/> A multiprocessor version of RX-UX 832 was also developed, named MUSTARD (Multiprocessor Unix for Embedded Real-Time Systems).<ref name=Suzuki1992/> The MUSTARD-powered computer prototype uses eight V70 processors. It utilizes FRM function, and can configure and change the configuration of master and checker upon request.<ref name=8-V70-Proc/><ref>{{cite book |editor-last=Suzuki |editor-first=Norihisa |title=Shared Memory Multiprocessing |pages=195ff |publisher=MIT Press |isbn=978-026219322-1 |date=1992 |url=https://books.google.com/books?id=Hyn9Cqf8PZsC&pg=PA195}}</ref>


=== I-TRON (real-time) ===
===I-TRON (real-time)===
For hardware-control-oriented [[embedded systems]], the [[Industrial TRON|I-TRON]]-based real-time operating system, named RX616, was implemented by NEC for the V60/V70.<ref name="IEEE-MICRO-FRM"/><ref name="rtos1997"/> The 32-bit RX616 was a continuous fork from the 16-bit [[NEC RX116|RX116]], which was for the [[NEC V20|V20-V50]].<ref name="dataquest-1987-2"/><ref name="32b-itron"/>
For hardware-control-oriented [[embedded system]]s, the [[ITRON project|I-TRON]]-based real-time operating system, named RX616, was implemented by NEC for the V60/V70.<ref name=IEEE-MICRO-FRM/><ref name=rtos1997/> The 32-bit RX616 was a continuous fork from the 16-bit [[NEC RX116|RX116]], which was for the [[NEC V20|V20-V50]].<ref name=dataquest-1987-2/><ref name=32b-itron/>


=== FlexOS (real-time) ===
===FlexOS (real-time)===
In 1987, [[Digital Research|Digital Research, Inc.]] also announced that they were planning on porting [[FlexOS]] to the V60 and V70.<ref name="FLEXOS"/>
In 1987, [[Digital Research|Digital Research, Inc.]] also announced that they were planning on porting [[FlexOS]] to the V60 and V70.<ref name=FLEXOS/>


=== CP/M and DOS (legacy 16-bit) ===
===CP/M and DOS (legacy 16-bit)===
The V60 could also run [[CP/M]] and [[DOS]] programs (ported from the V20-V50 series) using V20/V30 emulation mode.<ref name="dataquest-1986"/> According to a 1991 article in ''[[InfoWorld]]'', Digital Research was working on a version of [[Concurrent DOS]] for the V60 at some point; but this was never released, as the V60/V70 processors were not imported to the US for use in PC clones.<ref name="Inc.1991"/>
The V60 could also run [[CP/M]] and [[DOS]] programs (ported from the V20-V50 series) using V20/V30 emulation mode.<ref name=dataquest-1986/> According to a 1991 article in ''[[InfoWorld]]'', Digital Research was working on a version of [[Concurrent DOS]] for the V60 at some point; but this was never released, as the V60/V70 processors were not imported to the US for use in PC clones.<ref name=Inc.1991/>


== {{anchor|compiler|cross-compiler}}Development tools ==
=={{anchor|compiler|cross-compiler}}Development tools==


=== {{anchor|PKG70616|MetaWare|MetaWare, Inc.|High C/C++}}C/C++ cross-compilers ===
==={{anchor|PKG70616|MetaWare|MetaWare, Inc.|High C/C++}}C/C++ cross-compilers===
As part of its [[development tool]] kit and [[integrated development environment]] (IDE), NEC had its own [[C (programming language)|C]]-compiler, the PKG70616 "Software Generation tool package for V60/V70".<ref name="cat-fr"/> In addition, GHS ([[Green Hills Software]]) made its native mode C compiler (MULTI), and [[MetaWare, Inc.]] (currently [[Synopsys]], via [[Synopsys#ARC International|ARC International]]) made one, for V20/V30 (Intel 8086), emulation mode, called High C/C++.<ref name="high-c"/><ref name="i486-Micro-1990"/>{{rp|acknowledgement}}
As part of its [[development tool]] kit and [[integrated development environment]] (IDE), NEC had its own [[C (programming language)|C]]-compiler, the PKG70616 "Software Generation tool package for V60/V70".<ref name=cat-fr/> In addition, GHS ([[Green Hills Software]]) made its native mode C compiler (MULTI), and [[MetaWare, Inc.]] (currently [[Synopsys]], via [[Synopsys#ARC International|ARC International]]) made one, for V20/V30 (Intel 8086), emulation mode, called High C/C++.<ref name=high-c/><ref name=i486-Micro-1990/>{{rp|acknowledgement}}
[[Cygnus Solutions]] (currently [[Red Hat]]) also ported [[GNU Compiler Collection|GCC]] as a part of an enhanced GNU compiler system (EGCS) fork,<ref name="egcs"/> but it seems not to be public.<ref name="by-cygnus-1"/><ref name="by-cygnus-2"/>
[[Cygnus Solutions]] (currently [[Red Hat]]) also ported [[GNU Compiler Collection|GCC]] as a part of an enhanced GNU compiler system (EGCS) fork,<ref name=egcs/> but it seems not to be public.<ref name=by-cygnus-1/><ref name=by-cygnus-2/>


{{As of|2018}}, the processor-specific directory necv70 is still kept alive in the [[newlib]] C-language libraries (libc.a and libm.a) by [[RedHat]].<ref name="newlib"/> Recent maintenance seems to be done on Sourceware.org. The latest source code is available from its [[git]] [[Repository (version control)|repository]].<ref>{{cite web |title=Newlib-cygwin.git / history |url=https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;a=history;f=newlib/libc/machine/necv70;hb=HEAD |date=2020 |website=Sourceware.org |access-date=May 22, 2020}}</ref>
{{As of|2018}}, the processor-specific directory necv70 is still kept alive in the [[newlib]] C-language libraries (libc.a and libm.a) by [[RedHat]].<ref name=newlib/> Recent maintenance seems to be done on Sourceware.org. The latest source code is available from its [[git]] [[repository (version control)|repository]].<ref>{{cite web |title=Newlib-cygwin.git / history |website=Sourceware.org |date=2020 |url=https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;a=history;f=newlib/libc/machine/necv70;hb=HEAD |access-date=May 22, 2020}}</ref>


=== {{anchor|MV4000|MV-4000}}MV-4100 Ada 83–certified system ===
==={{anchor|MV4000|MV-4000}}MV-4100 Ada 83–certified system===
The [[Ada (programming language)|Ada 83]]–certified "platform system" was named MV‑4000, certified as "MV4000". This certification was done with a target system, that utilized the real-time UNIX RX-UX 832 OS running on a [[VMEbus]] (IEEE 1014)–based system with a V70 processor board plugged in. The host of the [[cross compiler]] was an NEC Engineering Work Station [[:ja:EWS4800|EWS 4800]], whose host OS, [[EWS-UX|EWS-US/V]], was also [[UNIX System&nbsp;V]]–based.<ref name="ada83cpl"/><ref name="MV-4000"/><ref name="ews-4800"/><ref>{{cite book |editor-last=Ratcliffe |editor-first=Mark |title=Ada Yearbook 1995 |url=https://books.google.com/books?id=M3F-lhug50cC&q=MV4000+V70&pg=PA198 |date=1995 |page=198 |publisher=[[IOS Press]] |isbn=9789051992182 |access-date=22 May 2020}}</ref>
The [[Ada (programming language)|Ada 83]]–certified "platform system" was named MV-4000, certified as "MV4000". This certification was done with a target system, that utilized the real-time UNIX RX-UX 832 OS running on a [[VMEbus]] (IEEE 1014)–based system with a V70 processor board plugged in. The host of the [[cross compiler]] was an NEC Engineering Work Station [[:ja:EWS4800|EWS 4800]], whose host OS, [[EWS-UX|EWS-US/V]], was also [[UNIX System&nbsp;V]]–based.<ref name=ada83cpl/><ref name=MV-4000/><ref name=ews-4800/><ref>{{cite book |editor-last=Ratcliffe |editor-first=Mark |title=Ada Yearbook 1995 |page=198 |publisher=[[IOS Press]] |isbn=9789051992182 |date=1995 |url=https://books.google.com/books?id=M3F-lhug50cC&q=MV4000+V70&pg=PA198 |access-date=22 May 2020}}</ref>


The processor received Ada-83 validation from AETECH, Inc.,<ref name="ada83cpl" /> running the [[Ada Compiler Validation Capability]] tests.<ref>{{cite web |title=Ada Compiler Validation Procedures – Version 5.0 |url=http://archive.adaic.com/compilers/val-proc/1222val.html |date=18 November 1997 |website=Ada Resource Association |access-date=22 May 2020}}</ref>
The processor received Ada-83 validation from AETECH, Inc.,<ref name=ada83cpl/> running the [[Ada Compiler Validation Capability]] tests.<ref>{{cite web |title=Ada Compiler Validation Procedures – Version 5.0 |website=Ada Resource Association |date=18 November 1997 |url=http://archive.adaic.com/compilers/val-proc/1222val.html |access-date=22 May 2020}}</ref>


{| class="wikitable"
{| class="wikitable"
Line 170: Line 170:
| NEC Ada Compiler System for EWS-UX/V to V70/RX-UX832, Version 1.0 || 910918S1.11217 || Base || NEC EWS4800/60 || EWS-UX/V R8.1 || NEC MV4000 || RX-UX832 V1.6
| NEC Ada Compiler System for EWS-UX/V to V70/RX-UX832, Version 1.0 || 910918S1.11217 || Base || NEC EWS4800/60 || EWS-UX/V R8.1 || NEC MV4000 || RX-UX832 V1.6
|-
|-
| NEC Ada Compiler System for EWS-UX/V(Release 4.0) to V70/RX-UX832 Version Release 4.1 (4.6.4) || 910918S1.11217 || Derived || EWS4800 Superstation RISC Series || EWS-UX/V(R4.0) R6.2 || NEC MV4000 || RX-UX832 V1.63
| NEC Ada Compiler System for EWS-UX/V(Release 4.0) to V70/RX-UX832 Version Release 4.1 (4.6.4) || 910918S1.11217 || Derived || EWS4800 Superstation RISC Series || EWS-UX/V(R4.0) R6.2 || NEC MV4000 || RX-UX832 V1.63
|}
|}


{| class="wikitable"
{| class="wikitable"
|-
|-
! MV‑4000 Features<ref name="MV-4000"/>
! MV-4000 Features<ref name=MV-4000/>
|-
|-
| System bus: IEEE1014 D1.2/IEC821 Rev C.1 (8-slot)
| System bus: IEEE1014 D1.2/IEC821 Rev C.1 (8-slot)
Line 190: Line 190:
|}
|}


=== Evaluation board kits ===
===Evaluation board kits===
NEC released some plug-in evaluation board kits for the V60/V70.
NEC released some plug-in evaluation board kits for the V60/V70.


Line 207: Line 207:
|}
|}


== {{anchor|hw-emulator|ICE}}In-circuit emulator ==
=={{anchor|hw-emulator|ICE}}In-circuit emulator==


=== On-chip software debug support with the IE-V60 ===
===On-chip software debug support with the IE-V60===
NEC based its own full (non-[[Read-only memory|ROM]] and non-[[JTAG]]) probe-based [[in-circuit emulator]], the IE-V60, on the V60, because V60/V70 chips themselves had emulator-chip capabilities. The IE-V60 was the first in-circuit emulator for V60 that was manufactured by NEC. It also had a PROM programmer function.<sup>Section 9.4, p.&nbsp;205</sup><ref name="maruzen"/> NEC described it as a "user friendly software debug function". The chips have various trapping exceptions, such as data read (or write) to the user specified address, and 2 break-points simultaneously.<sup>Section 9</sup><ref name="V60-Prog-Ref-Man"/>
NEC based its own full (non-[[read-only memory|ROM]] and non-[[JTAG]]) probe-based [[in-circuit emulator]], the IE-V60, on the V60, because V60/V70 chips themselves had emulator-chip capabilities. The IE-V60 was the first in-circuit emulator for V60 that was manufactured by NEC. It also had a PROM programmer function.<sup>Section 9.4, p.&nbsp;205</sup><ref name=maruzen/> NEC described it as a "user friendly software debug function". The chips have various trapping exceptions, such as data read (or write) to the user specified address, and 2 break-points simultaneously.<sup>Section 9</sup><ref name=V60-Prog-Ref-Man/>


=== External bus status pins ===
===External bus status pins===
The external bus system indicates its bus status using 3 status pins, which provide three bits to signal such conditions as first [[instruction fetch]] after branch, continuous [[instruction fetch]], [[Translation lookaside buffer|TLB]] [[data access]], single [[data access]], and [[Sequential access|sequential data access]]. <sup>Section 6.1, p.&nbsp;114</sup>
The external bus system indicates its bus status using 3 status pins, which provide three bits to signal such conditions as first [[instruction fetch]] after branch, continuous [[instruction fetch]], [[translation lookaside buffer|TLB]] [[data access]], single [[data access]], and [[sequential access|sequential data access]]. <sup>Section 6.1, p.&nbsp;114</sup>
<ref name="maruzen"/>
<ref name=maruzen/>


{| class="wikitable"
{| class="wikitable"
Line 236: Line 236:
|}
|}


=== Debugging with V80 ===
===Debugging with V80===
These software and hardware debugging functions were also built into the V80. However, the V80 did not have an [[In-circuit emulation|in-circuit emulator]], possibly because the presence of such software as [[Real-time operating system|real-time]] [[UNIX System&nbsp;V|UNIX]] RX-UX 832 and [[Real-time operating system|real-time]] [[Industrial TRON|I-TRON]] RX616 rendered such a function unnecessary. Once [[Unix]] boots up, there is no need for an in-circuit emulator for developing either [[device driver]]s or [[application software]]. What is needed is a [[C (programming language)|C]] [[compiler]], a [[cross compiler]], and a [[Debugger#Debugger front-ends|screen debugger]]—such as [[GNU Debugger#Graphical user interface|GDB-Tk]]—that works with the target device,.
These software and hardware debugging functions were also built into the V80. However, the V80 did not have an [[in-circuit emulation|in-circuit emulator]], possibly because the presence of such software as [[real-time operating system|real-time]] [[UNIX System&nbsp;V|UNIX]] RX-UX 832 and [[real-time operating system|real-time]] [[ITRON project|I-TRON]] RX616 rendered such a function unnecessary. Once [[Unix]] boots up, there is no need for an in-circuit emulator for developing either [[device driver]]s or [[application software]]. What is needed is a [[C (programming language)|C]] [[compiler]], a [[cross compiler]], and a [[Debugger#Debugger front-ends|screen debugger]]—such as [[GNU Debugger#Graphical user interface|GDB-Tk]]—that works with the target device,.


=== {{anchor|HP 64758}}HP 64758 ===
==={{anchor|HP 64758}}HP 64758===
[[Hewlett-Packard]] (currently [[Keysight]]) offered probing-pod-based [[in-circuit emulation]] hardware for the V70, built on their [[HP 64700]] Series systems,<ref name="HP-Vseries"/><ref name="HP64700"/> the successor to the [[HP 64000]] Series, specifically the HP 64758.<ref name="HP64758G"/><ref name="HP-discon"/><ref name="HP-Vseries"/> It enables trace function like a [[logic analyzer]]. This [[Electronic test equipment|test equipment]] also displays [[Disassembler|disassembled]] [[source code]] automatically, with trace data display and without an [[object file]],<ref name="HP-Vseries"/> and displays [[high-level language]] [[source code]] when the source code and the [[object file]]s are provided and they were [[compile]]d in [[DWARF]] format. An interface for the V60 (10339G) was also in the catalog,<ref name="HP-discon"/> but the long probing-pod cable required "special grade qualified" devices, i.e. the high-speed grade V70.
[[Hewlett-Packard]] (currently [[Keysight]]) offered probing-pod-based [[in-circuit emulation]] hardware for the V70, built on their [[HP 64700]] Series systems,<ref name=HP-Vseries/><ref name=HP64700/> the successor to the [[HP 64000]] Series, specifically the HP 64758.<ref name=HP64758G/><ref name=HP-discon/><ref name=HP-Vseries/> It enables trace function like a [[logic analyzer]]. This [[electronic test equipment|test equipment]] also displays [[disassembler|disassembled]] [[source code]] automatically, with trace data display and without an [[object file]],<ref name=HP-Vseries/> and displays [[high-level language]] [[source code]] when the source code and the [[object file]]s are provided and they were [[compile]]d in [[DWARF]] format. An interface for the V60 (10339G) was also in the catalog,<ref name=HP-discon/> but the long probing-pod cable required "special grade qualified" devices, i.e. the high-speed grade V70.


HP 64758: Main units, sub-units, and hosted interface
HP 64758: Main units, sub-units, and hosted interface
Line 249: Line 249:
| 64758A || V70 20&nbsp;MHz Emulator with 512KB of emulation memory
| 64758A || V70 20&nbsp;MHz Emulator with 512KB of emulation memory
|-
|-
| 64758AX || One-Time-Update
| 64758AX || One-Time-Update
|-
|-
| 64758B || V70 20MHZ Emulator with 1MB of emulation memory
| 64758B || V70 20MHZ Emulator with 1MB of emulation memory
Line 284: Line 284:
|}
|}


== {{anchor|fading}}Failings ==
=={{anchor|fading}}Failings==


=== Strategic failure of the V80 [[microarchitecture]] ===
===Strategic failure of the V80 [[microarchitecture]]===
In its development phase, the V80 was thought to have the same performance as the [[Intel 80486]],<ref name=" V80-rumor"/> but they ended up having many different features. The internal execution for each instruction of the V80 needed at least two cycles, while that of i486 required one. The internal pipeline of the V80 seemed [[Pipeline (computing)#Buffered, asynchronous pipelines|buffered asynchronous]], but that of i486 was [[Pipeline (computing)#Buffered, synchronous pipelines|synchronous]]. In other words, the internal [[microarchitecture]] of V80 was [[Complex instruction set computer|CISC]], but that of i486 was [[Reduced instruction set computer|RISC]]. Both of their [[Instruction set architecture|ISA]]s allowed long non-uniform [[Complex instruction set computer|CISC]] instructions, but the i486 had a wider, 128-bit internal [[cache memory]] bus, while that of V80 had a 32-bit width. This difference can be seen on their die photos.<ref name="overview"/><ref name="i486-Micro-1990"/><ref name="micro1990"/><ref name="i486-ICCD89"/> The design was fatal from the performance point of view, but NEC did not change it. NEC might have been able to redesign the [[Physical design (electronics)|physical design]], with the same [[register-transfer level]], but it did not.
In its development phase, the V80 was thought to have the same performance as the [[Intel 80486]],<ref name= V80-rumor/> but they ended up having many different features. The internal execution for each instruction of the V80 needed at least two cycles, while that of i486 required one. The internal pipeline of the V80 seemed [[pipeline (computing)#Buffered, asynchronous pipelines|buffered asynchronous]], but that of i486 was [[pipeline (computing)#Buffered, synchronous pipelines|synchronous]]. In other words, the internal [[microarchitecture]] of V80 was [[complex instruction set computer|CISC]], but that of i486 was [[reduced instruction set computer|RISC]]. Both of their [[Instruction set architecture|ISA]]s allowed long non-uniform [[Complex instruction set computer|CISC]] instructions, but the i486 had a wider, 128-bit internal [[cache memory]] bus, while that of V80 had a 32-bit width. This difference can be seen on their die photos.<ref name=overview/><ref name=i486-Micro-1990/><ref name=micro1990/><ref name=i486-ICCD89/> The design was fatal from the performance point of view, but NEC did not change it. NEC might have been able to redesign the [[physical design (electronics)|physical design]], with the same [[register-transfer level]], but it did not.


=== Lack of commercial success ===
===Lack of commercial success===
The V60-V80 architecture did not enjoy much commercial success.<ref name="Methé1991"/>
The V60-V80 architecture did not enjoy much commercial success.<ref name=Methé1991/>


The V60, V70, and V80 were listed in the 1989 and 1990 NEC catalogs in their [[Pin grid array|PGA]] packaging.<ref name="cat89"/><ref name="cat90"/> A NEC catalog from 1995 still listed the V60 and V70 (not only in their [[Pin grid array|PGA]] version but also in a [[Quad Flat Package|QFP]] packaging, and also included a low-cost variant of the V60 named μPD70615, which eliminated V20/V30 emulation and FRM function), alongside their assorted chipsets; but the V80 was not offered in this catalog.<ref name="cat95"/> The 1999 edition of the same catalog no longer had any V60-V80 products.<ref name="cat99"/>
The V60, V70, and V80 were listed in the 1989 and 1990 NEC catalogs in their [[pin grid array|PGA]] packaging.<ref name=cat89/><ref name=cat90/> A NEC catalog from 1995 still listed the V60 and V70 (not only in their PGA version but also in a [[quad flat package|QFP]] packaging, and also included a low-cost variant of the V60 named μPD70615, which eliminated V20/V30 emulation and FRM function), alongside their assorted chipsets; but the V80 was not offered in this catalog.<ref name=cat95/> The 1999 edition of the same catalog no longer had any V60-V80 products.<ref name=cat99/>


== Successors ==
==Successors==


=== {{anchor|NEC V810|NEC V820|NEC V830|μPD70732|μPD70742}}The V800&nbsp;series ===
==={{anchor|NEC V810|NEC V820|NEC V830|μPD70732|μPD70742}}The V800&nbsp;series===
In 1992, NEC launched a new model, the V800&nbsp;Series 32-bit [[microcontroller]]; but it did not have a [[memory management unit]] (MMU).<ref name="1992-ARC-06"/> It had a [[Reduced instruction set computer|RISC]]-based architecture, inspired by the [[Intel i960]] and [[MIPS architecture|MIPS]] architectures, and other RISC processor instructions, such as JARL (Jump and Register Link) and [[load/store architecture]].
In 1992, NEC launched a new model, the V800&nbsp;Series 32-bit [[microcontroller]]; but it did not have a [[memory management unit]] (MMU).<ref name=1992-ARC-06/> It had a [[reduced instruction set computer|RISC]]-based architecture, inspired by the [[Intel i960]] and [[MIPS architecture|MIPS]] architectures, and other RISC processor instructions, such as JARL (Jump and Register Link) and [[load–store architecture]].


At this time, the enormous software assets of the V60/V70, such as real-time Unix, were abandoned and never returned to their successors, a scenario Intel avoided.
At this time, the enormous software assets of the V60/V70, such as real-time Unix, were abandoned and never returned to their successors, a scenario Intel avoided.


The V800&nbsp;Series had 3 major variants, the V810, V830, and [[V850]] families.<ref name="EDN"/><ref name="IEIEC-1995"/><ref name="IEEE-1998"/>
The V800&nbsp;Series had 3 major variants, the V810, V830, and [[V850]] families.<ref name=EDN/><ref name=IEIEC-1995/><ref name=IEEE-1998/>


The V820 (μPD70742) was a simple variant of the V810 (μPD70732), but with peripherals.
The V820 (μPD70742) was a simple variant of the V810 (μPD70732), but with peripherals.


The [[:ja:シバンムシ|designation V840]] may have been skipped as a designation because of Japanese [[tetraphobia]] (see page 58<ref name="cat95"/>). One [[Japanese pronunciation]] of "4" means "death", thus avoid names evoking such as [[Deathwatch beetle|Death-watch]] Shi-ban (the number 4 – Shi-ban) [[Software bug|Bug]] ({{nihongo2|[[:ja:シバンムシ|死番虫]]}}, precisely "[[deathwatch beetle]]").
The [[:ja:シバンムシ|designation V840]] may have been skipped as a designation because of Japanese [[tetraphobia]] (see page 58<ref name=cat95/>). One [[Japanese pronunciation]] of "4" means "death", thus avoid names evoking such as [[Deathwatch beetle|Death-watch]] Shi-ban (the number 4 – Shi-ban) [[Software bug|Bug]] ({{nihongo2|[[:ja:シバンムシ|死番虫]]}}, precisely "[[deathwatch beetle]]").


As of 2005, it was already the [[V850]] era, and the [[V850]]&nbsp;family has been enjoying great success.<ref name="cat05"/> As of 2018, it is called the Renesas V850&nbsp;family and the RH850&nbsp;family, with V850/V850E1/V850E2 and V850E2/V850E3 CPU cores, respectively. Those CPU cores have extended the [[Instruction set architecture|ISA]] of the original V810 core;<ref name="V810-GCC"/> running with the V850 compiler.<ref name="GHS-V850"/>
As of 2005, it was already the [[V850]] era, and the [[V850]]&nbsp;family has been enjoying great success.<ref name=cat05/> As of 2018, it is called the Renesas V850&nbsp;family and the RH850&nbsp;family, with V850/V850E1/V850E2 and V850E2/V850E3 CPU cores, respectively. Those CPU cores have extended the [[instruction set architecture|ISA]] of the original V810 core;<ref name=V810-GCC/> running with the V850 compiler.<ref name=GHS-V850/>


== {{anchor|sw-emulator|ISS|MAME}}Modern software-based simulation ==
=={{anchor|sw-emulator|ISS|MAME}}Modern software-based simulation==


=== MAME ===
===MAME===
Because the V60/V70 had been used for many Japanese [[Amusement arcade|arcade games]], [[MAME]] (for "Multiple Arcade Machine Emulator"), which emulates multiple old arcade games for enthusiasts, includes an [[Emulator#CPU simulator|CPU simulator]] for their [[instruction set architecture]].<ref name="v60-cemu"/> It is a kind of an [[instruction set simulator]], not for developers but for users.
Because the V60/V70 had been used for many Japanese [[amusement arcade|arcade games]], [[MAME]] (for "Multiple Arcade Machine Emulator"), which emulates multiple old arcade games for enthusiasts, includes an [[emulator#CPU simulator|CPU simulator]] for their [[instruction set architecture]].<ref name=v60-cemu/> It is a kind of an [[instruction set simulator]], not for developers but for users.


It has been maintained by the [http://www.mamedev.org/ ''MAME development team'']. The latest [[open-source software|open-source]] [[source code|code]], written in [[C++]], is available from the [[GitHub]] [[Repository (version control)|repository]].<ref>{{cite web |title=MAMEdev – V60 |website=[[GitHub]] |url=https://github.com/mamedev/mame/tree/master/src/devices/cpu/v60/ |access-date=26 May 2020}}</ref> The ''[[operation code]]s'' in the file [https://github.com/mamedev/mame/blob/master/src/devices/cpu/v60/optable.hxx optable.hxx] are exactly the same as those of the V60.<ref name="V60-Prog-Ref-Man"/>
It has been maintained by the [http://www.mamedev.org/ ''MAME development team'']. The latest [[open-source software|open-source]] [[source code|code]], written in [[C++]], is available from the [[GitHub]] [[repository (version control)|repository]].<ref>{{cite web |title=MAMEdev – V60 |website=[[GitHub]] |url=https://github.com/mamedev/mame/tree/master/src/devices/cpu/v60/ |access-date=26 May 2020}}</ref> The ''[[operation code]]s'' in the file [https://github.com/mamedev/mame/blob/master/src/devices/cpu/v60/optable.hxx optable.hxx] are exactly the same as those of the V60.<ref name=V60-Prog-Ref-Man/>


== See also ==
==See also==
* [[NEC V20]]
* [[NEC V20]]
* [[V850]]
* [[V850]]
* [[R4200]]
* [[R4200]]


== References ==
==References==
{{Reflist|refs=

{{reflist|refs=


<!----------------->
<!----------------->
Line 331: Line 330:
<!----- BOOKS, AUTHOR=NEC ----->
<!----- BOOKS, AUTHOR=NEC ----->


<ref name="V60-Prog-Ref-Man">
<ref name=V60-Prog-Ref-Man>
{{cite book|author1=NEC|title=μPD70616 Programmer's Reference Manual|date=November 1986|publisher=The Internet Archive, a 501(c)(3) non-profit|edition=PRELIMINARY|url=https://archive.org/details/NEC_V60pgmRef|quote=<br/>EPUB, KINDLE, PDF, PDF w/text, FULL TEXT, etc, are available}}
{{cite book |author1=NEC |title=μPD70616 Programmer's Reference Manual |publisher=The Internet Archive, a 501(c)(3) non-profit |edition=PRELIMINARY |date=November 1986 |url=https://archive.org/details/NEC_V60pgmRef |quote=<br>EPUB, KINDLE, PDF, PDF w/text, FULL TEXT, etc, are available}}
</ref>
</ref>


<ref name="V60-Datasheet">
<ref name=V60-Datasheet>
{{cite book|title=1987 Microcomputer Data Book: Vol. 2|date=August 1986|publisher=NEC|pages=3-229–3-232|url=http://bitsavers.org/components/nec/_dataBooks/1987_Microcomputer_Products_Vol_2.pdf}}
{{cite book |title=1987 Microcomputer Data Book: Vol. 2 |publisher=NEC |pages=3-229–3-232 |date=August 1986 |url=http://bitsavers.org/components/nec/_dataBooks/1987_Microcomputer_Products_Vol_2.pdf}}
</ref>
</ref>


<ref name="V20-V50-progman">
<ref name=V20-V50-progman>
{{cite book|author1=NEC|title=16-BIT V SERIES; INSTRUCTIONS|date=June 1997|publisher=The Internet Archive, a 501(c)(3) non-profit|edition=5|url=https://archive.org/details/bitsavers_necdatabooBITVSeriesJun97_693718|quote=<br/>EPUB, KINDLE, PDF, FULL TEXT, etc, are available.}}
{{cite book |author1=NEC |title=16-BIT V SERIES; INSTRUCTIONS |publisher=The Internet Archive, a 501(c)(3) non-profit |edition=5 |date=June 1997 |url=https://archive.org/details/bitsavers_necdatabooBITVSeriesJun97_693718 |quote=<br>EPUB, KINDLE, PDF, FULL TEXT, etc, are available.}}
</ref>
</ref>


<ref name="Computer-Architecture-4thEd">
<ref name=Computer-Architecture-4thEd>
{{cite book|last1=Hennessy: Stanford University|first1=John L|last2=Patterson: University of California at Berkeley|first2=David A.|title=Computer Architecture: A Quantitative Approach|date=2007|publisher=MORGAN KAUFMANN PUBLISHERA|url=https://archive.org/details/2007ComputerArchitectureAQuantitativeApproach|isbn=978-0-12-370490-0|edition=Fourth|quote=<br/>Open Access: EPUB, KINDLE, PDF, FULL TEXT, etc, are available.}}
{{cite book |last1=Hennessy: Stanford University |first1=John L |last2=Patterson: University of California at Berkeley |first2=David A. |title=Computer Architecture: A Quantitative Approach |publisher=Morgan Kaufmann Publishers |isbn=978-0-12-370490-0 |edition=Fourth |date=2007 |url=https://archive.org/details/2007ComputerArchitectureAQuantitativeApproach |quote=<br>Open Access: EPUB, KINDLE, PDF, FULL TEXT, etc, are available.}}
</ref>
</ref>


<!----- BOOKS, JAPANESE ----->
<!----- BOOKS, JAPANESE ----->


<ref name="maruzen">
<ref name=maruzen>
{{Cite book |last=Kani |first=Dr. Kenji |date=April 1987 |trans-title=V-Series Microcomputer 2|title=Vシリーズマイクロコンピュータ 2|publisher=Maruzen | isbn=978-4621031575 |language=ja|quote=<br/>本書は日本電気(株)が、わが国ではじめて開発した32ビットマイクロプロセッサV60について解説したものである。[This book explains the V60, Japanese first developed 32-bit microprocessor by NEC.]}}
{{cite book |last=Kani |first=Dr. Kenji |trans-title=V-Series Microcomputer 2 |title=Vシリーズマイクロコンピュータ 2 |publisher=Maruzen |isbn=978-4621031575 |language=ja |date=April 1987 |quote=<br>本書は日本電気(株)が、わが国ではじめて開発した32ビットマイクロプロセッサV60について解説したものである。[This book explains the V60, Japanese first developed 32-bit microprocessor by NEC.]}}
</ref>
</ref>


<!----- BOOKS, AUTHOR NOT NEC ----->
<!----- BOOKS, AUTHOR NOT NEC ----->


<ref name="Methé1991">
<ref name=Methé1991>
{{cite book|author=David T. Methé|title=Technological Competition in Global Industries: Marketing and Planning Strategies for American Industry|url=https://books.google.com/books?id=_wHx9wlDVlcC&pg=PA128|year=1991|publisher=Greenwood Publishing Group|isbn=978-0-89930-480-9|page=128}}
{{cite book |author=David T. Methé |title=Technological Competition in Global Industries: Marketing and Planning Strategies for American Industry |year=1991 |publisher=Greenwood Publishing Group |isbn=978-0-89930-480-9 |page=128 |url=https://books.google.com/books?id=_wHx9wlDVlcC&pg=PA128}}
</ref>
</ref>


Line 365: Line 364:
<!----- JOURNAL, AUTHOR==NEC ----->
<!----- JOURNAL, AUTHOR==NEC ----->


<ref name="IEEE-MICRO-FRM">
<ref name=IEEE-MICRO-FRM>
{{Cite journal | doi = 10.1109/40.527 | title = Implementation of the V60/V70 and its FRM function| journal = IEEE Micro| volume = 8| issue = 2| pages = 22–36| date =April 1988| last1 = Kimura | first1 = S.| last2 = Komoto | first2 = Y.| last3 = Yano | first3 = Y.| s2cid = 9507994|quote=<br/>Abstract:<br/>A description is given of the V60/V70, the first commercially based, general-purpose 32-bit microprocessor in Japan. Its functions include on-chip floating-point operations, a high-level-language-oriented architecture, software debugging support, and support functions to promote a high level of system reliability. Because high reliability is so important, the V60/V70 contains functional redundancy monitoring (FRM) support functions. The discussion covers the overall design considerations, architecture, implementation, hazard detection and control, and FRM functions. The V60/V70 uses a TRON real-time operating system specification.}}
{{cite journal |title=Implementation of the V60/V70 and its FRM function |journal=IEEE Micro |volume=8 |issue=2 |pages=22–36 |last1=Kimura |first1=S. |last2=Komoto |first2=Y. |last3=Yano |first3=Y. |s2cid=9507994 |doi=10.1109/40.527 |date=April 1988 |quote=<br>Abstract:<br>A description is given of the V60/V70, the first commercially based, general-purpose 32-bit microprocessor in Japan. Its functions include on-chip floating-point operations, a high-level-language-oriented architecture, software debugging support, and support functions to promote a high level of system reliability. Because high reliability is so important, the V60/V70 contains functional redundancy monitoring (FRM) support functions. The discussion covers the overall design considerations, architecture, implementation, hazard detection and control, and FRM functions. The V60/V70 uses a TRON real-time operating system specification.}}
</ref>
</ref>


<ref name="compcon1988">
<ref name=compcon1988>
{{Cite book | doi = 10.1109/CMPCON.1988.4824 | isbn = 0-8186-0828-5 | title = V60/V70 microprocessor and its systems support functions | publisher = Digest of Papers. COMPCON Spring 88 Thirty-Third IEEE Computer Society International Conference | pages = [https://archive.org/details/compconspring8830000ieee/page/36 36–42] | date = Spring 1988 | last1 = Yano | first1 = Y. | last2 = Koumoto | first2 = Y. | last3 = Sato | first3 = Y. | s2cid = 9186701 | quote = <br/>Abstract:<br/>Two advanced 32-bit microprocessors, the V60 and V70 ( mu PD70616 and mu PD70632, respectively), and their support functions for operating systems and high-reliability systems are described. Three operating system functions, namely, the virtual memory support functions, context-switch functions, and asynchronous trap functions are examined. A basic mechanism for high-reliability-system implementation, called FRM (functional redundancy monitoring), is discussed. FRM allows a system to be designed in which multiple V60s (or V70s) form a configuration in which one processor in the system acts as a master while the others act as monitors. An FRM board that uses three V60s in its redundant core is introduced. | url = https://archive.org/details/compconspring8830000ieee/page/36 }}
{{cite book |title=V60/V70 microprocessor and its systems support functions |isbn=0-8186-0828-5 |publisher=Digest of Papers. COMPCON Spring 88 Thirty-Third IEEE Computer Society International Conference |pages=[https://archive.org/details/compconspring8830000ieee/page/36 36–42] |last1=Yano |first1=Y. |last2=Koumoto |first2=Y. |last3=Sato |first3=Y. |s2cid=9186701 |doi=10.1109/CMPCON.1988.4824 |date=Spring 1988 |url=https://archive.org/details/compconspring8830000ieee/page/36 |quote=<br>Abstract:<br>Two advanced 32-bit microprocessors, the V60 and V70 (mu PD70616 and mu PD70632, respectively), and their support functions for operating systems and high-reliability systems are described. Three operating system functions, namely, the virtual memory support functions, context-switch functions, and asynchronous trap functions are examined. A basic mechanism for high-reliability-system implementation, called FRM (functional redundancy monitoring), is discussed. FRM allows a system to be designed in which multiple V60s (or V70s) form a configuration in which one processor in the system acts as a master while the others act as monitors. An FRM board that uses three V60s in its redundant core is introduced.}}
</ref>
</ref>


<ref name="micro1990">
<ref name=micro1990>
{{cite journal|last1=Kaneko|first1=Hiroaki|last2=Suzuki|first2=Nariko|last3=Wabuka|first3=Hhiroaki|last4=Maemura|first4=Koji|title=Realizing the V80 and its system support functions|journal=IEEE Micro|date=April 1990|volume=10|issue=2|pages=56–69|doi=10.1109/40.52947|s2cid=2634866|issn=0272-1732|quote=<br/>Abstract:<br/>An overview is given of the architecture of an overall design considerations for the 11-unit, 32-b V80 microprocessor, which includes two 1-kB cache memories and a branch prediction mechanism that is a new feature for microprocessors. The V80's pipeline processing and system support functions for multiprocessor and high-reliability systems are discussed. Using V80 support functions, multiprocessor and high-reliability systems were realized without any performance drop. Cache memories and a branch prediction mechanism were used to improve pipeline processing. Various hardware facilities replaced the usual microprogram to ensure high performance.}}
{{cite journal |last1=Kaneko |first1=Hiroaki |last2=Suzuki |first2=Nariko |last3=Wabuka |first3=Hhiroaki |last4=Maemura |first4=Koji |title=Realizing the V80 and its system support functions |journal=IEEE Micro |volume=10 |issue=2 |pages=56–69 |s2cid=2634866 |issn=0272-1732 |doi=10.1109/40.52947 |date=April 1990 |quote=<br>Abstract:<br>An overview is given of the architecture of an overall design considerations for the 11-unit, 32-b V80 microprocessor, which includes two 1-kB cache memories and a branch prediction mechanism that is a new feature for microprocessors. The V80's pipeline processing and system support functions for multiprocessor and high-reliability systems are discussed. Using V80 support functions, multiprocessor and high-reliability systems were realized without any performance drop. Cache memories and a branch prediction mechanism were used to improve pipeline processing. Various hardware facilities replaced the usual microprogram to ensure high performance.}}<br>
<br/>{{Cite journal|title=ditto|journal=IEEE Micro|volume=10|issue=2|pages=56–69|publisher=ACM|url-access=subscription|url=https://dl.acm.org/citation.cfm?id=623503|doi=10.1109/40.52947|date=March 1990|last1=Kaneko|first1=Hiraoki|last2=Suzuki|first2=Nariko|last3=Wabuka|first3=Hiroshi|last4=Maemura|first4=Koji|s2cid=2634866}}</ref>
{{cite journal |title=ditto |journal=IEEE Micro |volume=10 |issue=2 |pages=56–69 |publisher=ACM |last1=Kaneko |first1=Hiraoki |last2=Suzuki |first2=Nariko |last3=Wabuka |first3=Hiroshi |last4=Maemura |first4=Koji |s2cid=2634866 |doi=10.1109/40.52947 |date=March 1990 |url=https://dl.acm.org/citation.cfm?id=623503}} |url-access=subscription</ref>


<ref name="coproc">
<ref name=coproc>
{{Cite journal | doi = 10.1109/JSSC.1989.572608|issn=1558-173X| title = A 6.7-MFLOPS floating-point coprocessor with vector/matrix instructions| journal = IEEE Journal of Solid-State Circuits| volume = 24| issue = 5| pages = 1324–1330| date =Oct 1989| last1 = Nakayama | first1 = T.| last2 = Harigai | first2 = H.| last3 = Kojima | first3 = S.| last4 = Kaneko | first4 = H.| last5 = Igarashi | first5 = H.| last6 = Toba | first6 = T.| last7 = Yamagami | first7 = Y.| last8 = Yano | first8 = Y.|quote=<br/>Abstract:<br/>An 80-bit floating-point coprocessor which implements 24 vector/matrix instructions and 22 mathematical functions is described. This processor can execute floating-point addition/rounding and pipelined multiplication concurrently, under the control of horizontal-type microinstructions. The SRT division method and CORDIC trigonometrical algorithm are used for a favorable cost/performance implementation. The performance of 6.7 MFLOPS in the vector-matrix multiplication at 20&nbsp;MHz has been attained by the use of parallel operations. The vector/matrix instruction is about three times faster than conventional add and multiply instructions. The chip has been fabricated in 1.2- mu m double-metal layer CMOS process containing 433000 transistors on an 11.6*14.9-mm/sup 2/ die size.| bibcode=1989IJSSC..24.1324N }}
{{cite journal |issn=1558-173X |title=A 6.7-MFLOPS floating-point coprocessor with vector/matrix instructions |journal=IEEE Journal of Solid-State Circuits |volume=24 |issue=5 |pages=1324–1330 |last1=Nakayama |first1=T. |last2=Harigai |first2=H. |last3=Kojima |first3=S. |last4=Kaneko |first4=H. |last5=Igarashi |first5=H. |last6=Toba |first6=T. |last7=Yamagami |first7=Y. |last8=Yano |first8=Y. |bibcode=1989IJSSC..24.1324N |doi=10.1109/JSSC.1989.572608 |date=Oct 1989 |quote=<br>Abstract:<br>An 80-bit floating-point coprocessor which implements 24 vector/matrix instructions and 22 mathematical functions is described. This processor can execute floating-point addition/rounding and pipelined multiplication concurrently, under the control of horizontal-type microinstructions. The SRT division method and CORDIC trigonometrical algorithm are used for a favorable cost/performance implementation. The performance of 6.7 MFLOPS in the vector-matrix multiplication at 20&nbsp;MHz has been attained by the use of parallel operations. The vector/matrix instruction is about three times faster than conventional add and multiply instructions. The chip has been fabricated in 1.2- mu m double-metal layer CMOS process containing 433000 transistors on an 11.6*14.9-mm/sup 2/ die size.}}
</ref>
</ref>


<ref name="overview">
<ref name=overview>
{{cite journal |last1=Komoto |first1=Yasuhiko |last2=Saito |first2=Tatsuya|last3=Mine|first3=Kazumasa |date=1990-08-25 |title=Overview of 32-bit V-Series Microprocessor |format=pdf | url= https://ipsj.ixsq.nii.ac.jp/ej/index.php?action=pages_view_main&active_action=repository_action_common_download&item_id=59745&item_no=1&attribute_id=1&file_no=1&page_id=13&block_id=8 |journal=Journal of Information Processing |volume=13 |issue=2 |pages=110–122 |issn=1882-6652 |language=en|access-date=2018-01-08|quote=Open Access<br/>Abstract:<br />The advances in semiconductor manufacturing technology make it possible to integrate a floating-point unit and a memory management unit noto one microprocessor chip. They also permit the designers of a microprocessor to implement techniques used in the design of mainframe computers especially with regard to pipeline structures. The architecture of the V60 V70 and V80 was made possible by there advances. The V60 and V70 are NEC's first 32-bit microprocessors and include almost all the functions required by applied systems in a chip. The instruction set provides a high-level-language-oriented structure operating system sup-port functions and support functions for highly reliable systems. The V80 also employs the same architecture and achieves higher performance by means of cache memories and branch prediction mechanisms. The V80achieved a performance from two to four times higher than that of the V70.}}
{{cite journal |last1=Komoto |first1=Yasuhiko |last2=Saito |first2=Tatsuya |last3=Mine |first3=Kazumasa |title=Overview of 32-bit V-Series Microprocessor |format=pdf |journal=Journal of Information Processing |volume=13 |issue=2 |pages=110–122 |issn=1882-6652 |language=en |date=1990-08-25 |url=https://ipsj.ixsq.nii.ac.jp/ej/index.php?action=pages_view_main&active_action=repository_action_common_download&item_id=59745&item_no=1&attribute_id=1&file_no=1&page_id=13&block_id=8 |access-date=2018-01-08 |quote=Open Access<br>Abstract:<br>The advances in semiconductor manufacturing technology make it possible to integrate a floating-point unit and a memory management unit noto one microprocessor chip. They also permit the designers of a microprocessor to implement techniques used in the design of mainframe computers especially with regard to pipeline structures. The architecture of the V60 V70 and V80 was made possible by there advances. The V60 and V70 are NEC's first 32-bit microprocessors and include almost all the functions required by applied systems in a chip. The instruction set provides a high-level-language-oriented structure operating system sup-port functions and support functions for highly reliable systems. The V80 also employs the same architecture and achieves higher performance by means of cache memories and branch prediction mechanisms. The V80achieved a performance from two to four times higher than that of the V70.}}
</ref>
</ref>


<!----- JOURNAL, SOFTWARE ----->
<!----- JOURNAL, SOFTWARE ----->


<ref name="PC-UX-R2-V60">
<ref name=PC-UX-R2-V60>
{{cite journal|url=http://id.nii.ac.jp/1001/00113909/|format=pdf|publisher=Information Society of Japan|title=PORTING UNIX System&nbsp;V TO THE V60 SYSTEMS|journal=全国大会講演論文集|volume=第33回|issue=アーキテクチャおよびハードウェア|pages=163–164|language=ja|access-date=2018-01-07|date=October 1986|last1=雅則|first1=寺本|last2=健治|first2=赤羽|last3=良彦|first3=和田|last4=由紀子|first4=水橋|last5=滋|first5=川又}}
{{cite journal |title=PORTING UNIX System&nbsp;V TO THE V60 SYSTEMS |publisher=Information Society of Japan |journal=全国大会講演論文集 |volume=第33回 |issue=アーキテクチャおよびハードウェア |pages=163–164 |language=ja |last1=雅則 |first1=寺本 |last2=健治 |first2=赤羽 |last3=良彦 |first3=和田 |last4=由紀子 |first4=水橋 |last5=滋 |first5=川又 |format=pdf |date=October 1986 |url=http://id.nii.ac.jp/1001/00113909/ |access-date=2018-01-07}}
</ref>
</ref>


<ref name="RX-UX-832">
<ref name=RX-UX-832>
{{Cite journal | doi = 10.1016/0165-6074(89)90105-1| title = Real-time UNIX operating system: RX-UX 832| journal = Microprocessing and Microprogramming| volume = 27| issue = 1–5| pages = 533–538| date = August 1989| last1 = Mizuhashi | first1 = Yukiko | last2 = Teramoto | first2 = Msanoro |quote= <br/>Abstract:<br/>This paper describes requirements for real-time UNIX operating systems, design concept and the implementation of RX-UX 832 real-time UNIX operating system for v60/v70 microprocessor which are NEC's 32-bit microprocessors. RX-UX 832 is implemented adopting the building block structure, composed of three modules, real-time kernel, file-server and Unix supervisor. To guarantee a real-time responsibility, several enhancements were introduced such as, fixed priority task scheduling scheme, contiguous block file system and fault tolerant functions.<br/>Thus, RX-UX 832 allows system designers to use standard Unix as its man-machine interface to build fault tolerant systems with sophisticated operability and provides high-quality software applications on the high performance microchips. }}
{{cite journal |title=Real-time UNIX operating system: RX-UX 832 |journal=Microprocessing and Microprogramming |volume=27 |issue=1–5 |pages=533–538 |last1=Mizuhashi |first1=Yukiko |last2=Teramoto |first2=Msanoro |doi=10.1016/0165-6074(89)90105-1 |date=August 1989 |quote=<br>Abstract:<br>This paper describes requirements for real-time UNIX operating systems, design concept and the implementation of RX-UX 832 real-time UNIX operating system for v60/v70 microprocessor which are NEC's 32-bit microprocessors. RX-UX 832 is implemented adopting the building block structure, composed of three modules, real-time kernel, file-server and Unix supervisor. To guarantee a real-time responsibility, several enhancements were introduced such as, fixed priority task scheduling scheme, contiguous block file system and fault tolerant functions.<br>Thus, RX-UX 832 allows system designers to use standard Unix as its man-machine interface to build fault tolerant systems with sophisticated operability and provides high-quality software applications on the high performance microchips.}}
</ref>
</ref>


<ref name="Suzuki1992">
<ref name=Suzuki1992>
{{cite book|author=Norihisa Suzuki|title=Shared Memory Multiprocessing|url=https://books.google.com/books?id=Hyn9Cqf8PZsC&pg=PA195|date=January 1992|publisher=MIT Press|isbn=978-0-262-19322-1|page=195}}
{{cite book |author=Norihisa Suzuki |title=Shared Memory Multiprocessing |publisher=MIT Press |isbn=978-0-262-19322-1 |page=195 |date=January 1992 |url=https://books.google.com/books?id=Hyn9Cqf8PZsC&pg=PA195}}
</ref>
</ref>


<ref name="8-V70-Proc">
<ref name=8-V70-Proc>
{{cite magazine|url=https://apps.dtic.mil/dtic/tr/fulltext/u2/a240438.pdf|title=The International Symposium on Shared Memory Multiprocessing (ISSMM)|publisher=Office of Naval Research Asian Office|magazine=Scientific Information Bulletin|volume=16|number=3|date=July–September 1991|pages=2–3|archive-url=https://web.archive.org/web/20210301082631/https://apps.dtic.mil/dtic/tr/fulltext/u2/a240438.pdf|archive-date=March 1, 2021|url-status=live}}
{{cite magazine |title=The International Symposium on Shared Memory Multiprocessing (ISSMM) |publisher=Office of Naval Research Asian Office |magazine=Scientific Information Bulletin |volume=16 |number=3 |pages=2–3 |date=July–September 1991 |url=https://apps.dtic.mil/dtic/tr/fulltext/u2/a240438.pdf |url-status=live |archive-url=https://web.archive.org/web/20210301082631/https://apps.dtic.mil/dtic/tr/fulltext/u2/a240438.pdf |archive-date=March 1, 2021}}
</ref>
</ref>


<ref name="Inc.1991">
<ref name=Inc.1991>
{{cite journal|author=Brett Glass|title=Answer Line|url=https://books.google.com/books?id=VlAEAAAAMBAJ&pg=PA72|date=6 May 1991|journal=InfoWorld|page=72|issn=0199-6649}}
{{cite journal |title=Answer Line |author=Brett Glass |journal=InfoWorld |page=72 |issn=0199-6649 |date=6 May 1991 |url=https://books.google.com/books?id=VlAEAAAAMBAJ&pg=PA72}}
</ref>
</ref>


<ref name="FLEXOS">
<ref name=FLEXOS>
{{cite journal |title=Digital Research launches FlexOS 286 Real-Time Manufacturing Operating System |editor=CBR |journal=Computer Business Review |date=1987-01-15 |url=http://www.cbronline.com/news/digital_research_launches_flexos_286_real_time_manufacturing_operating_system |access-date=2018-09-15 |url-status=live |archive-url=https://archive.today/20130118190950/http://www.cbronline.com/news/digital_research_launches_flexos_286_real_time_manufacturing_operating_system |archive-date=2013-01-18}}</ref>
{{cite journal |title=Digital Research launches FlexOS 286 Real-Time Manufacturing Operating System |journal=techmonitor.ai, formerly Computer Business Review |date=1987-01-15 |url=https://techmonitor.ai/technology/digital_research_launches_flexos_286_real_time_manufacturing_operating_system |access-date=2018-09-15 |url-status=live |archive-url=https://archive.today/20130118190950/http://www.cbronline.com/news/digital_research_launches_flexos_286_real_time_manufacturing_operating_system |archive-date=2013-01-18}}</ref>
<ref name=rtos1997>
<ref name=rtos1997>
{{cite journal |last1=Shimojima |first1=Takehiko |last2=Teramoto |first2=Masanori|year=1987 |title=V60 real-time operating system |journal=Microprocessing and Microprogramming|volume=21 |issue=1–5 |pages=197–204 |doi=10.1016/0165-6074(87)90038-X|issn=0165-6074|quote=<br/>Abstract:<br/>This paper describes the requirements for 32-bit microprocessor real-time operating systems, design objectives and the implementation of the V60/V70 Real-Time Operating System (RTOS) and its programming supports.}}
{{cite journal |last1=Shimojima |first1=Takehiko |last2=Teramoto |first2=Masanori |year=1987 |title=V60 real-time operating system |journal=Microprocessing and Microprogramming |volume=21 |issue=1–5 |pages=197–204 |issn=0165-6074 |doi=10.1016/0165-6074(87)90038-X |quote=<br>Abstract:<br>This paper describes the requirements for 32-bit microprocessor real-time operating systems, design objectives and the implementation of the V60/V70 Real-Time Operating System (RTOS) and its programming supports.}}
</ref>
</ref>


<!----- JOURNAL, V800 ----->
<!----- JOURNAL, V800 ----->


<ref name="1992-ARC-06">
<ref name=1992-ARC-06>
{{cite journal|last1=Harigai|first1=Hisao|last2=Kusuda|first2=Masaori|last3=Kojima|first3=Shingo|last4=Moriyama|first4=Masatoshi|last5=Ienaga|first5=Takashi|last6=Yano|first6=Yoichi|title=低消費電力・低電圧動作の32ビットマイクロプロセッサV810|journal=SIG Technical Reports, Information Processing Society of Japan|date=1992-10-22|volume=1992|issue=82 (1992-ARC-096)|pages=41–48|url=https://ci.nii.ac.jp/naid/170000021173|trans-title=A low power consumption and low voltage operation 32-bit RISC Microprocessor|quote=<br/>Abstract:<br/>An advanced 32-bit RISC microprocessor for embedded control; V810 is introduced in this paper. The V810 has high performance and application specified functions. V810 dissipates less power than any other RISC chips. The V810 is the first 32-bit RISC microprocessor that operates at 2.2V.<br/>The V810 chip is fabricated by using 0.8μm CMOS double metal layer process technology to integrate 240,000 transistors on a 7.7×7.7mm<sup>2</sup> die.}}
{{cite journal |last1=Harigai |first1=Hisao |last2=Kusuda |first2=Masaori |last3=Kojima |first3=Shingo |last4=Moriyama |first4=Masatoshi |last5=Ienaga |first5=Takashi |last6=Yano |first6=Yoichi |title=低消費電力・低電圧動作の32ビットマイクロプロセッサV810 |journal=SIG Technical Reports, Information Processing Society of Japan |volume=1992 |issue=82 (1992-ARC-096) |pages=41–48 |trans-title=A low power consumption and low voltage operation 32-bit RISC Microprocessor |date=1992-10-22 |url=https://ci.nii.ac.jp/naid/170000021173 |quote=<br>Abstract:<br>An advanced 32-bit RISC microprocessor for embedded control; V810 is introduced in this paper. The V810 has high performance and application specified functions. V810 dissipates less power than any other RISC chips. The V810 is the first 32-bit RISC microprocessor that operates at 2.2V.<br>The V810 chip is fabricated by using 0.8μm CMOS double metal layer process technology to integrate 240,000 transistors on a 7.7×7.7mm<sup>2</sup> die.}}
</ref>
</ref>


<ref name="IEIEC-1995">
<ref name=IEIEC-1995>
{{cite journal|last1=Suzuki|first1=Hiroaki|last2=Sakai|first2=Toshichika|last3=Harigai|first3=Hisao|last4=Yano|first4=Yoichi|title=A 0.9-V, 2.5&nbsp;MHz CMOS 32-bit Microprocessor|journal=IEICE TRANSACTIONS on Electronics|date=1995-04-25|volume=E78-C|issue=4|pages=389–393|url-access=subscription|url=http://search.ieice.org/bin/summary.php?id=e78-c_4_389&category=C&year=1995&lang=E|access-date=2018-01-09|issn=0916-8516|quote=<br/>Summary:<br/>A 32-bit RISC microprocessor "V810" that has 5-stage pipeline structure and a 1 Kbyte, direct-mapped instruction cache realizes 2.5&nbsp;MHz operation at 0.9 V with 2.0 mW power consumption. The supply voltage can be reduced to 0.75 V. To overcome narrow noise margin, all the signals are set to have rail-to-rail swing by pseudo-static circuit technique. The chip is fabricated by a 0.8 μm double metal-layer CMOS process technology to integrate 240,000 transistors on a 7.4 mm7.1 mm die.}}
{{cite journal |last1=Suzuki |first1=Hiroaki |last2=Sakai |first2=Toshichika |last3=Harigai |first3=Hisao |last4=Yano |first4=Yoichi |title=A 0.9-V, 2.5&nbsp;MHz CMOS 32-bit Microprocessor |journal=IEICE TRANSACTIONS on Electronics |volume=E78-C |issue=4 |pages=389–393 |url-access=subscription |issn=0916-8516 |date=1995-04-25 |url=https://search.ieice.org/bin/summary.php?id=e78-c_4_389&category=C&year=1995&lang=E |access-date=2018-01-09 |quote=<br>Summary:<br>A 32-bit RISC microprocessor "V810" that has 5-stage pipeline structure and a 1 Kbyte, direct-mapped instruction cache realizes 2.5&nbsp;MHz operation at 0.9 V with 2.0 mW power consumption. The supply voltage can be reduced to 0.75 V. To overcome narrow noise margin, all the signals are set to have rail-to-rail swing by pseudo-static circuit technique. The chip is fabricated by a 0.8 μm double metal-layer CMOS process technology to integrate 240,000 transistors on a 7.4 mm7.1 mm die.}}
</ref>
</ref>


<ref name="IEEE-1998">
<ref name=IEEE-1998>
{{cite journal |last1=Suzuki |first1=K. |last2=Arai |first2=T. |last3=Nadehara|first3=K.| last4=Kuroda|first4=I.|year=1998 |title=V830R/AV: embedded multimedia superscalar RISC processor |journal=IEEE Micro |volume=18 |issue=2 |pages=36–47 |issn=0272-1732|doi=10.1109/40.671401 |quote=<br/>Abstract:<br/>The V830R/AV's real-time decoding of MPEG-2 video and audio data enables practical embedded-processor-based multimedia systems.}}
{{cite journal |last1=Suzuki |first1=K. |last2=Arai |first2=T. |last3=Nadehara |first3=K. |last4=Kuroda |first4=I. |year=1998 |title=V830R/AV: embedded multimedia superscalar RISC processor |journal=IEEE Micro |volume=18 |issue=2 |pages=36–47 |issn=0272-1732 |doi=10.1109/40.671401 |quote=<br>Abstract:<br>The V830R/AV's real-time decoding of MPEG-2 video and audio data enables practical embedded-processor-based multimedia systems.}}
</ref>
</ref>


<!----- JOURNAL, JAPANESE ----->
<!----- JOURNAL, JAPANESE ----->


<ref name="SIG-ARC-043">
<ref name=SIG-ARC-043>
{{cite journal|last1=Yamahata|first1=Hitoshi|last2=Suzuki|first2=Nariko|last3=Koumoto|first3=Yasuhiko|last4=Shiiba|first4=Tadaaki|title=マイクロプロセッサV60のアーキテクチャ|journal=SIG Technical Reports; Microcomputer 43-2|date=1987-02-06|volume=1987|issue=8(1986-ARC-043)|pages=1–8|url=https://ipsj.ixsq.nii.ac.jp/ej/?action=repository_uri&item_id=24887&file_id=1&file_no=1|trans-title=Architecture of the microprocessor V60|publisher=Information Processing Society of Japan|language=ja|format=PDF|id=AN10096105|quote=<br/>This report will describe a single chip 32-bit CMOS VLSI microprocessor V60. It has been implemented by using a double metal-layer CMOS process technology with 1.5 um design rule to integrate 375,000 transistors. It integrates the virtual memory management unit for demand paging and the floating-point operations that conform to the IEEE-754 Floating-Point Standard. By using V20/V30 emulation mode, it can directly execute object programs of 16-bit CPU (V30). Instruction formats are suited to code-generation phase of compilers. 237 instructions are provided for high-level language and operating system. It can execute 3.5 MIPS (Million Instructions per Second) at 16-MHz operation with 16-bit data bus.}}
{{cite journal |last1=Yamahata |first1=Hitoshi |last2=Suzuki |first2=Nariko |last3=Koumoto |first3=Yasuhiko |last4=Shiiba |first4=Tadaaki |title=マイクロプロセッサV60のアーキテクチャ |journal=SIG Technical Reports; Microcomputer 43-2 |volume=1987 |issue=8(1986-ARC-043) |pages=1–8 |trans-title=Architecture of the microprocessor V60 |publisher=Information Processing Society of Japan |language=ja |format=PDF |id=AN10096105 |date=1987-02-06 |url=https://ipsj.ixsq.nii.ac.jp/ej/?action=repository_uri&item_id=24887&file_id=1&file_no=1 |quote=<br>This report will describe a single chip 32-bit CMOS VLSI microprocessor V60. It has been implemented by using a double metal-layer CMOS process technology with 1.5 um design rule to integrate 375,000 transistors. It integrates the virtual memory management unit for demand paging and the floating-point operations that conform to the IEEE-754 Floating-Point Standard. By using V20/V30 emulation mode, it can directly execute object programs of 16-bit CPU (V30). Instruction formats are suited to code-generation phase of compilers. 237 instructions are provided for high-level language and operating system. It can execute 3.5 MIPS (Million Instructions per Second) at 16-MHz operation with 16-bit data bus.}}
</ref>
</ref>


<ref name="SIG-ARC-069">
<ref name=SIG-ARC-069>
{{cite journal|last1=Takahashi|first1=Toshiya|last2=Yano|first2=Yoichi|title=V60/V70アーキテクチャ|journal=SIG Technical Reports|date=1988-01-21|volume=1988|issue=4(1987-ARC-069)|pages=57–64|url=https://ipsj.ixsq.nii.ac.jp/ej/?action=repository_uri&item_id=24816&file_id=1&file_no=1|trans-title=The Architecture of V60/V70 Microprocessors|publisher=Information Processing Society of Japan|language=ja|format=PDF|id=AN10096105|quote=<br/>This report describes the architecture of V60/V70 32-bit microprocessors. The architecture integrates various features into a single silicon die, such as a rich set of general purpose registers, high level language oriented instruction set, floating-point data handling which is suitable for scientific applications, and the FRM (Functionality Redundancy Monitoring) operation mode which supports highly-reliable systems configuration. These features will be introduced.}}
{{cite journal |last1=Takahashi |first1=Toshiya |last2=Yano |first2=Yoichi |title=V60/V70アーキテクチャ |journal=SIG Technical Reports |volume=1988 |issue=4(1987-ARC-069) |pages=57–64 |trans-title=The Architecture of V60/V70 Microprocessors |publisher=Information Processing Society of Japan |language=ja |format=PDF |id=AN10096105 |date=1988-01-21 |url=https://ipsj.ixsq.nii.ac.jp/ej/?action=repository_uri&item_id=24816&file_id=1&file_no=1 |quote=<br>This report describes the architecture of V60/V70 32-bit microprocessors. The architecture integrates various features into a single silicon die, such as a rich set of general-purpose registers, high level language oriented instruction set, floating-point data handling which is suitable for scientific applications, and the FRM (Functionality Redundancy Monitoring) operation mode which supports highly-reliable systems configuration. These features will be introduced.}}
</ref>
</ref>


<ref name="dev-story">
<ref name=dev-story>
{{Cite web|url=http://www.shmj.or.jp/dev_story/pdf/develop46.pdf|first1=Yoichi|last1=Yano|date=April 2012|publisher=Semiconductor History Museum of Japan|language=ja|access-date=2018-01-08|title=32ビット・マイコン「V60」開発物語|trans-title=Development story of the 32-bit microcomputer V60}}<br/>
{{cite web |first1=Yoichi |last1=Yano |trans-title=Development story of the 32-bit microcomputer V60 |title=32ビット・マイコン「V60」開発物語 |language=ja |publisher=Semiconductor History Museum of Japan |date=April 2012 |url=https://www.shmj.or.jp/dev_story/pdf/develop46.pdf |access-date=2018-01-08}}<br>
{{Cite journal|format=pdf|url=http://www.ssis.or.jp/encore/encore2012.html#no75|journal=Bulletin "Encore"|date=April 2012|volume=75|pages=17–20|publisher=Society of Semiconductor Industry Specialists|title=ditto|language=ja|access-date=2018-01-08}}
{{cite journal |title=Encore 2012 |format=pdf |journal=Bulletin "Encore" |volume=75 |pages=17–20 |publisher=Society of Semiconductor Industry Specialists |title=ditto |language=ja |date=April 2012 |url=https://www.ssis.or.jp/encore/encore2012.html#no75 |access-date=2018-01-08}}
</ref>
</ref>


<ref name="32b-itron">
<ref name=32b-itron>
{{cite journal|last1=Monden|first1=Hiroshi|last2=Teramoto|first2=Takashi|last3=Koga|first3=Masanori|title=V60用アルタイムOSの検討 -32ビットI-TRONに向けて-|journal=SIG (ARC) Technical Reports|date=1986-03-14|volume=1986|issue=19(1985-ARC-061)|pages=1–8|url=https://ipsj.ixsq.nii.ac.jp/ej/?action=repository_action_common_download&item_id=24938&item_no=1&attribute_id=1&file_no=1|trans-title=Feasibility study of real-time OS for the V60 - toward for the 32-bit I-TRON -|publisher=Information Processing Society of Japan|language=ja|format=PDF|id=AN10096105|quote=Open Access}}</ref>
{{cite journal |last1=Monden |first1=Hiroshi |last2=Teramoto |first2=Takashi |last3=Koga |first3=Masanori |trans-title=Feasibility study of real-time OS for the V60 - toward for the 32-bit I-TRON - |title=V60用アルタイムOSの検討 -32ビットI-TRONに向けて- |language=ja |journal=SIG (ARC) Technical Reports |volume=1986 |issue=19(1985-ARC-061) |pages=1–8 |publisher=Information Processing Society of Japan |format=PDF |id=AN10096105 |date=1986-03-14 |url=https://ipsj.ixsq.nii.ac.jp/ej/?action=repository_action_common_download&item_id=24938&item_no=1&attribute_id=1&file_no=1 |quote=Open Access}}</ref>


<!----- JOURNAL, NEC-TECHNICAL ----->
<!----- JOURNAL, NEC-TECHNICAL ----->


<ref name="nectech-jaxagcc">
<ref name=nectech-jaxagcc>
HAYASHI, N. [http://www.nec.com/en/global/techrep/journal/g11/n01/pdf/110130.pdf Guidance Control Computer for Launch Vehicle], NEC Technical Journal, Vol. 6, No. 1/2001, pp. 145-148
HAYASHI, N. [https://www.nec.com/en/global/techrep/journal/g11/n01/pdf/110130.pdf Guidance Control Computer for Launch Vehicle], NEC Technical Journal, Vol. 6, No. 1/2001, pp. 145-148
</ref>
</ref>


<ref name="nec-tecj-ms4100">
<ref name=nec-tecj-ms4100>
{{Cite journal|url=http://jglobal.jst.go.jp/en/public/20090422/200902041619492749|title=The outline of NEC super minicomputer MS4100 Series, NEC Technical Journal |journal=Nec技報 |volume=39 |issue=11 |pages=113–124 |publisher=NEC Technical Journal, Vol.39 Iss.11 p.p.113-124, Nov. 1986|language=ja|year=1986 |last1=Takeo |first1=Sakurai |last2=Osamu |first2=Oizumi }}
{{cite journal |title=The outline of NEC super minicomputer MS4100 Series, NEC Technical Journal |journal=Nec技報 |volume=39 |issue=11 |pages=113–124 |publisher=NEC Technical Journal, Vol.39 Iss.11 p.p.113-124, Nov. 1986 |language=ja |year=1986 |last1=Takeo |first1=Sakurai |last2=Osamu |first2=Oizumi |url=https://jglobal.jst.go.jp/en/detail?JGLOBAL_ID=200902041619492749}}
</ref>
</ref>


<!----- JOURNAL, Meidensha Corp ----->
<!----- JOURNAL, Meidensha Corp ----->


<ref name="Meiden-Jiho-Jul92">
<ref name=Meiden-Jiho-Jul92>
{{cite journal|last1=OSAMU|first1=TSUJI|last2=SATORU|first2=KOMIYAMA|last3=TOSHIYUKI|first3=DOI|last4=TETSUYA|first4=IWAKI|title=情報機器 工業用コンピュータμPORT-III|journal=明電時報 [Meiden Jiho]|date=July 1992|issue=225|pages=24–32|url=http://jglobal.jst.go.jp/en/public/20090422/200902079033599746|trans-title=Information-processing equipment.Industrial computer .MU.PORT-III.|language=ja|issn=0386-1570}}
{{cite journal |last1=OSAMU |first1=TSUJI |last2=SATORU |first2=KOMIYAMA |last3=TOSHIYUKI |first3=DOI |last4=TETSUYA |first4=IWAKI |title=情報機器 工業用コンピュータμPORT-III |journal=明電時報 [Meiden Jiho] |issue=225 |pages=24–32 |trans-title=Information-processing equipment.Industrial computer .MU.PORT-III. |language=ja |issn=0386-1570 |date=July 1992 |url=https://jglobal.jst.go.jp/en/detail?JGLOBAL_ID=200902079033599746}}
</ref>
</ref>


<ref name="Meiden-Jiho-May93">
<ref name=Meiden-Jiho-May93>
{{cite journal|last1=HISAO|first1=SASAKI|last2=AKIRA|first2=SATO|last3=TOSHIO|first3=KARAKAMA|title=工業用コンピュータμPORT-IIIと適用事例|journal=明電時報 [Meiden Jiho]|date=May 1993|issue=230|pages=41–44|url=http://jglobal.jst.go.jp/en/public/20090422/200902104337850113|trans-title=Applications of industrial computer .MU.PORT-III.|language=ja|issn=0386-1570}}
{{cite journal |last1=HISAO |first1=SASAKI |last2=AKIRA |first2=SATO |last3=TOSHIO |first3=KARAKAMA |title=工業用コンピュータμPORT-IIIと適用事例 |journal=明電時報 [Meiden Jiho] |issue=230 |pages=41–44 |trans-title=Applications of industrial computer .MU.PORT-III. |language=ja |issn=0386-1570 |date=May 1993 |url=https://jglobal.jst.go.jp/en/detail?JGLOBAL_ID=200902104337850113}}
</ref>
</ref>


<!----- JOURNAL, AUTHOR==OTHERS ----->
<!----- JOURNAL, AUTHOR==OTHERS ----->


<ref name="MIPS-1984">
<ref name=MIPS-1984>
{{cite journal|last1=Rowen|first1=C.|last2=Przbylski|first2=S.|author-link3=Norman Jouppi|last3=Jouppi|first3=N.|last4=Gross|first4=T.|last5=Shott|first5=J.|last6=Hennessy|first6=J.|title=A pipelined 32b NMOS microprocessor|journal=1984 IEEE International Solid-State Circuits Conference. Digest of Technical Papers|date=1984|volume=XXVII|pages=180–181|doi=10.1109/ISSCC.1984.1156607|s2cid=42147153|quote=<br/>Stanford MIPS}}
{{cite journal |last1=Rowen |first1=C. |last2=Przbylski |first2=S. |author-link3=Norman Jouppi |last3=Jouppi |first3=N. |last4=Gross |first4=T. |last5=Shott |first5=J. |last6=Hennessy |first6=J. |title=A pipelined 32b NMOS microprocessor |journal=1984 IEEE International Solid-State Circuits Conference. Digest of Technical Papers |volume=XXVII |pages=180–181 |s2cid=42147153 |doi=10.1109/ISSCC.1984.1156607 |date=1984 |quote=<br>Stanford MIPS}}
</ref>
</ref>


<ref name="RISC-II">
<ref name=RISC-II>
{{cite journal|last1=Sherburne|first1=R. W.|last2=Katevenis|first2=M. G. H.|last3=Patterson|first3=D. A.|last4=Sequin|first4=C. H.|title=A 32-bit NMOS microprocessor with a large register file|journal=IEEE Journal of Solid-State Circuits|date=1984|volume=19|issue=5|pages=682–689|doi=10.1109/JSSC.1984.1052208|issn=0018-9200|quote=<br/>UCB RISC-II|bibcode=1984IJSSC..19..682S|s2cid=23195124}}
{{cite journal |last1=Sherburne |first1=R. W. |last2=Katevenis |first2=M. G. H. |last3=Patterson |first3=D. A. |last4=Sequin |first4=C. H. |title=A 32-bit NMOS microprocessor with a large register file |journal=IEEE Journal of Solid-State Circuits |volume=19 |issue=5 |pages=682–689 |issn=0018-9200 |bibcode=1984IJSSC..19..682S |s2cid=23195124 |doi=10.1109/JSSC.1984.1052208 |date=1984 |quote=<br>UCB RISC-II}}
</ref>
</ref>


<ref name="R2000">
<ref name=R2000>
{{cite conference|last1=Riordan|first1=T.|last2=Grewal|first2=G. P.|last3=Hsu|first3=S.|last4=Kinsel|first4=J.|last5=Libby|first5=J.|last6=March|first6=R.|last7=Mills|first7=M.|last8=Ries|first8=P.|last9=Scofield|first9=R.|title=The MIPS M2000 system|book-title=Proceedings 1988 IEEE International Conference on Computer Design: VLSI|date=1988|pages=366–369|doi=10.1109/ICCD.1988.25724|quote=<br/>MIPS M2000 (R2000)|isbn=0-8186-0872-2|s2cid=60801545}}
{{cite conference |last1=Riordan |first1=T. |last2=Grewal |first2=G. P. |last3=Hsu |first3=S. |last4=Kinsel |first4=J. |last5=Libby |first5=J. |last6=March |first6=R. |last7=Mills |first7=M. |last8=Ries |first8=P. |last9=Scofield |first9=R. |title=The MIPS M2000 system |book-title=Proceedings 1988 IEEE International Conference on Computer Design: VLSI |pages=366–369 |isbn=0-8186-0872-2 |s2cid=60801545 |doi=10.1109/ICCD.1988.25724 |date=1988 |quote=<br>MIPS M2000 (R2000)}}
</ref>
</ref>


<ref name="First-SPARC">
<ref name=First-SPARC>
{{cite conference|last1=Namjoo|first1=M.|last2=Agrawal|first2=A.|last3=Jackson|first3=D. C.|last4=Quach|first4=L.|title=CMOS gate array implementation of the SPARC architecture|book-title=Digest of Papers. COMPCON Spring 88 Thirty-Third IEEE Computer Society International Conference|date=1988|pages=[https://archive.org/details/compconspring8830000ieee/page/10 10–13]|doi=10.1109/CMPCON.1988.4818|url=https://archive.org/details/compconspring8830000ieee/page/10|quote=<br/>SPARC, 1st Gen.|isbn=0-8186-0828-5|s2cid=21078114}}
{{cite conference |last1=Namjoo |first1=M. |last2=Agrawal |first2=A. |last3=Jackson |first3=D. C. |last4=Quach |first4=L. |title=CMOS gate array implementation of the SPARC architecture |book-title=Digest of Papers. COMPCON Spring 88 Thirty-Third IEEE Computer Society International Conference |pages=[https://archive.org/details/compconspring8830000ieee/page/10 10–13] |isbn=0-8186-0828-5 |s2cid=21078114 |doi=10.1109/CMPCON.1988.4818 |date=1988 |url=https://archive.org/details/compconspring8830000ieee/page/10 |quote=<br>SPARC, 1st Gen.}}
</ref>
</ref>


<ref name="i860">
<ref name=i860>
{{cite conference|last1=Kohn|first1=L.|last2=Fu|first2=S. W.|title=A 1,000,000 transistor microprocessor|book-title=IEEE International Solid-State Circuits Conference, 1989 ISSCC. Digest of Technical Papers|date=1989|pages=54–55|doi=10.1109/ISSCC.1989.48231|s2cid=58413700|quote=<br/>Intel 860}}
{{cite conference |last1=Kohn |first1=L. |last2=Fu |first2=S. W. |title=A 1,000,000 transistor microprocessor |book-title=IEEE International Solid-State Circuits Conference, 1989 ISSCC. Digest of Technical Papers |pages=54–55 |s2cid=58413700 |doi=10.1109/ISSCC.1989.48231 |date=1989 |quote=<br>Intel 860}}
</ref>
</ref>


<ref name="i486-ICCD89">
<ref name=i486-ICCD89>
{{cite conference|last1=Fu|first1=B.|last2=Saini|first2=A.|last3=Gelsinger|first3=P. P.|title=Performance and microarchitecture of the i486 processor|book-title=Proceedings 1989 IEEE International Conference on Computer Design: VLSI in Computers and Processors|date=1989|pages=182–187|doi=10.1109/ICCD.1989.63352|isbn=0-8186-1971-6|s2cid=62082864|quote=<br/>Intel 80486<br/>Abstract:<br/>The i486 microprocessor includes a carefully tuned, five-stage pipeline with an integrated 8-kB cache. A variety of techniques previously associated only with RISC (reduced-instruction-set computer) processors are used to execute the average instruction in 1.8 clocks. This represents a 2.5* reduction from its predecessor, the 386 microprocessor. The pipeline and clock count comparisons are described in detail. In addition, an onchip floating-point unit is included which yields a 4* clock count reduction from the 387 numeric coprocessor. The microarchitecture enhancements and optimizations used to achieve this goal, most of which are non-silicon-intensive, are discussed. All instructions of the 386 microprocessor and the 387 numeric coprocessor are implemented in a completely compatible fashion.}}
{{cite conference |last1=Fu |first1=B. |last2=Saini |first2=A. |last3=Gelsinger |first3=P. P. |title=Performance and microarchitecture of the i486 processor |book-title=Proceedings 1989 IEEE International Conference on Computer Design: VLSI in Computers and Processors |pages=182–187 |isbn=0-8186-1971-6 |s2cid=62082864 |doi=10.1109/ICCD.1989.63352 |date=1989 |quote=<br>Intel 80486<br>Abstract:<br>The i486 microprocessor includes a carefully tuned, five-stage pipeline with an integrated 8-kB cache. A variety of techniques previously associated only with RISC (reduced-instruction-set computer) processors are used to execute the average instruction in 1.8 clocks. This represents a 2.5* reduction from its predecessor, the 386 microprocessor. The pipeline and clock count comparisons are described in detail. In addition, an onchip floating-point unit is included which yields a 4* clock count reduction from the 387 numeric coprocessor. The microarchitecture enhancements and optimizations used to achieve this goal, most of which are non-silicon-intensive, are discussed. All instructions of the 386 microprocessor and the 387 numeric coprocessor are implemented in a completely compatible fashion.}}
</ref>
</ref>


<ref name="i486-Micro-1990">
<ref name=i486-Micro-1990>
{{cite journal|last1=Crawford|first1=J.H.|title=The i486 CPU: executing instructions in one clock cycle|journal=IEEE Micro|date=February 1990|volume=10|issue=1|pages=27–36|doi=10.1109/40.46766|issn=0272-1732|citeseerx=10.1.1.126.4216}}
{{cite journal |last1=Crawford |first1=J.H. |title=The i486 CPU: executing instructions in one clock cycle |journal=IEEE Micro |volume=10 |issue=1 |pages=27–36 |issn=0272-1732 |citeseerx=10.1.1.126.4216 |doi=10.1109/40.46766 |date=February 1990}}
</ref>
</ref>


<ref name="pj">
<ref name=pj>
{{cite journal|last1=Hardenbergh |first1=Hal W | title=RISCs CISCs and Fabs|journal=Programmer's Journal|year=1988|publisher=Avant-Garde Creations|volume=6|issue=2|page=15|quote=<br/>So far we haven't mentioned two 32-bit CISC chips, the NEC V60/70 and the AT&T WE32 family. Unlike the NEC V20/25/30/50, the V60/70 is ''not'' based on the Intel architecture. NEC is targeting the V60/70 at embedded applications, ... }}
{{cite journal |last1=Hardenbergh |first1=Hal W |title=RISCs CISCs and Fabs |journal=Programmer's Journal |year=1988 |publisher=Avant-Garde Creations |volume=6 |issue=2 |page=15 |quote=<br>So far we haven't mentioned two 32-bit CISC chips, the NEC V60/70 and the AT&T WE32 family. Unlike the NEC V20/25/30/50, the V60/70 is ''not'' based on the Intel architecture. NEC is targeting the V60/70 at embedded applications, ...}}
[https://books.google.com/books?id=iX8qAAAAMAAJ&q=V60/70 Google Books]
[https://books.google.com/books?id=iX8qAAAAMAAJ&q=V60/70 Google Books]
</ref>
</ref>


<ref name="trend">
<ref name=trend>
{{cite journal |last1=Sakamura|first1=Ken|date=April 1988 |title=Recent Trends |url=http://www.computer.org/csdl/mags/mi/1988/02/m2010.pdf |journal=IEEE Micro |volume=8 |issue=2 |pages=10–11 |issn=0272-1732|access-date=2018-01-08 |quote=<br/>The V60/V70, NEC's proprietary CPU, is the first commercial-base, general-purpose, 32-bit microprocessor in Japan.}}
{{cite journal |last1=Sakamura |first1=Ken |title=Recent Trends |journal=IEEE Micro |volume=8 |issue=2 |pages=10–11 |issn=0272-1732 |date=April 1988 |url=http://www.computer.org/csdl/mags/mi/1988/02/m2010.pdf |access-date=2018-01-08 |quote=<br>The V60/V70, NEC's proprietary CPU, is the first commercial-base, general-purpose, 32-bit microprocessor in Japan.}}
</ref>
</ref>


<ref name="Wade, 1996">
<ref name=Wade1996>
{{cite journal|last1=Wade|first1=James|title=A Community-Level Analysis of Sources and Rates of Technological Variation in the Microprocessor Market|journal=Academy of Management Journal|date=1 October 1996|volume=39|issue=5|pages=1218–1244|doi=10.2307/256997|url=https://journals.aom.org/doi/abs/10.5465/256997?journalCode=amj|language=en|issn=0001-4273|quote=The sponsors that did not use RISC technology were NEC, AT&T, and Followers of the TRON standard. All three of these microprocessors were specialized for users for whom performance was the highest priority. The Hitachi microprocessor followed the TRON standard, a high-performance CISC technology that, Japanese developers suggested, would be a viable alternative to RISC. The AT&T chip was portrayed as a chip suitable for building top-of-the-line, minicomputer-like computing systems. Similarly, NEC's V60 and V70 were patterned after one of NEC's 36-bit mainframe computers.|jstor=256997}}
{{cite journal |last1=Wade |first1=James |title=A Community-Level Analysis of Sources and Rates of Technological Variation in the Microprocessor Market |journal=Academy of Management Journal |volume=39 |issue=5 |pages=1218–1244 |language=en |issn=0001-4273 |jstor=256997 |doi=10.2307/256997 |date=1 October 1996 |url=https://journals.aom.org/doi/abs/10.5465/256997?journalCode=amj |quote=The sponsors that did not use RISC technology were NEC, AT&T, and Followers of the TRON standard. All three of these microprocessors were specialized for users for whom performance was the highest priority. The Hitachi microprocessor followed the TRON standard, a high-performance CISC technology that, Japanese developers suggested, would be a viable alternative to RISC. The AT&T chip was portrayed as a chip suitable for building top-of-the-line, minicomputer-like computing systems. Similarly, NEC's V60 and V70 were patterned after one of NEC's 36-bit mainframe computers.}}
</ref>
</ref>


<ref name="Majithi, 1987">
<ref name=Majithi1987>
{{cite journal|last1=Majithi|first1=Kenneth|title=The New Generation of Microprocessors|journal=IEEE Micro|date=1987|volume=7|issue=4|pages=4–5|doi=10.1109/MM.1987.304873|issn=0272-1732|quote=<br/>The Japanese have been equally aggressive in their new designs of high-performance microprocessors. NEC's V60 and V70 microprocessors use architectures that include not only the MMU but also an arithmetic floating-point unit on chip. Hitachi and Fujitsu have collaborated to produce a family of microprocessors adapted to the TRON operating system. These processors incorporate instruction pipelines as well as instruction and stack caches. However, unlike NEC, their FPU function is off chip.}}
{{cite journal |last1=Majithi |first1=Kenneth |title=The New Generation of Microprocessors |journal=IEEE Micro |volume=7 |issue=4 |pages=4–5 |issn=0272-1732 |doi=10.1109/MM.1987.304873 |date=1987 |quote=<br>The Japanese have been equally aggressive in their new designs of high-performance microprocessors. NEC's V60 and V70 microprocessors use architectures that include not only the MMU but also an arithmetic floating-point unit on chip. Hitachi and Fujitsu have collaborated to produce a family of microprocessors adapted to the TRON operating system. These processors incorporate instruction pipelines as well as instruction and stack caches. However, unlike NEC, their FPU function is off chip.}}
</ref>
</ref>


Line 516: Line 515:
<!------------------->
<!------------------->


<ref name="cat-fr">
<ref name=cat-fr>
{{cite web|author1=NEC|title=Microprocessors and Peripherals Data Book|url=http://matthieu.benoit.free.fr/cross/data_sheets/NEC_Microprocessors-and-Peripherals_Data_Book.htm}}
{{cite web |author1=NEC |title=Microprocessors and Peripherals Data Book |url=http://matthieu.benoit.free.fr/cross/data_sheets/NEC_Microprocessors-and-Peripherals_Data_Book.htm}}
</ref>
</ref>


<ref name="cat89">
<ref name=cat89>
{{cite book|author1=NEC|title=Intelligent Peripheral Devices Data Book|url=https://archive.org/details/bitsavers_necdataBootPeripheralDevicesDataBook_33483764|publisher=The Internet Archive, a 501(c)(3) non-profit|page=18|date=June 1989}}
{{cite book |author1=NEC |title=Intelligent Peripheral Devices Data Book |publisher=The Internet Archive, a 501(c)(3) non-profit |page=18 |date=June 1989 |url=https://archive.org/details/bitsavers_necdataBootPeripheralDevicesDataBook_33483764}}
</ref>
</ref>


<ref name="cat90">
<ref name=cat90>
{{cite book|author1=NEC|title=Single-Chip Microcontroller Data Book|url=https://archive.org/details/bitsavers_necdatabooMicrocontrollerDataBook_57118308|publisher=The Internet Archive, a 501(c)(3) non-profit|page=30|date=May 1990}}
{{cite book |author1=NEC |title=Single-Chip Microcontroller Data Book |publisher=The Internet Archive, a 501(c)(3) non-profit |page=30 |date=May 1990 |url=https://archive.org/details/bitsavers_necdatabooMicrocontrollerDataBook_57118308}}
</ref>
</ref>


<ref name="cat95">
<ref name=cat95>
{{cite web|author1=NEC|title=SEMICONDUCTOR SELECTION GUIDE|edition=10th|date=Oct 1995|url=http://icbank.com/data/ICBShop/board/D72611GF.pdf|archive-url=https://web.archive.org/web/20160304043332/http://icbank.com/data/ICBShop/board/D72611GF.pdf|archive-date=2016-03-04|url-status=dead}}
{{cite web |author1=NEC |title=SEMICONDUCTOR SELECTION GUIDE |edition=10th |date=Oct 1995 |url=http://icbank.com/data/ICBShop/board/D72611GF.pdf |url-status=dead |archive-url=https://web.archive.org/web/20160304043332/http://icbank.com/data/ICBShop/board/D72611GF.pdf |archive-date=2016-03-04}}
</ref>
</ref>


<ref name="cat99">
<ref name=cat99>
{{cite web|author1=NEC|title=SEMICONDUCTORS SELECTION GUIDE|edition=17th|url=http://www.littlediode.com/datasheets/pdf/Datasheets-NEC/NEC-SHORTFORM.PDF|date=April 1999|archive-url=https://web.archive.org/web/20180108174757/http://www.littlediode.com/datasheets/pdf/Datasheets-NEC/NEC-SHORTFORM.PDF|archive-date=2018-01-08|url-status=dead}}
{{cite web |author1=NEC |title=SEMICONDUCTORS SELECTION GUIDE |edition=17th |date=April 1999 |url=http://www.littlediode.com/datasheets/pdf/Datasheets-NEC/NEC-SHORTFORM.PDF |url-status=dead |archive-url=https://web.archive.org/web/20180108174757/http://www.littlediode.com/datasheets/pdf/Datasheets-NEC/NEC-SHORTFORM.PDF |archive-date=2018-01-08}}
</ref>
</ref>


<ref name="cat05">
<ref name=cat05>
{{cite web|title=Microcontrollers and Development Tools Selection Guide|url=http://www1.futureelectronics.com/doc/RENESAS%20ELECTRONICS/NECMicrocontrollerGuide%5B1%5D.pdf|author=NEC|date=May 2005}}
{{cite web |title=Microcontrollers and Development Tools Selection Guide |author=NEC |date=May 2005 |url=http://www1.futureelectronics.com/doc/RENESAS%20ELECTRONICS/NECMicrocontrollerGuide%5B1%5D.pdf}}
</ref>
</ref>


Line 547: Line 546:


<ref name=ric-tan>
<ref name=ric-tan>
{{cite web|url=http://www.stanford.edu/group/htgg/sts145papers/rtan_2001_2.pdf|author=Richard Tan|title=STS 145 Case Study Sega: The effect of corporate conflict on game design| quote=<br/>"The Saturn originally ran on a NEC V60 chip at 16MHz. Compare this to the PlayStation CPU ([[MIPS architecture|MIPS]] R3000A 32bit [[Reduced instruction set computer|RISC]] chip) which runs are 33.8MHz, almost double the speed. According to one Sega staff member, when Nakayama first received design specifications for the PlayStation, he was 'the maddest I have ever seen him', calling up the entire R&D division to his office to shout at them. An effort was made to compensate by adding another CPU for dual operation; however, this solution made the system so hard to develop for that, according to Yu Suzuki himself, "only 1 out of 100 programmers could use the Saturn to its full potential.""|archive-url=https://web.archive.org/web/20140222140345/http://www.stanford.edu/group/htgg/sts145papers/rtan_2001_2.pdf|archive-date=2014-02-22|url-status=dead}}
{{cite web |author=Richard Tan |title=STS 145 Case Study Sega: The effect of corporate conflict on game design |url=http://www.stanford.edu/group/htgg/sts145papers/rtan_2001_2.pdf |url-status=dead |archive-url=https://web.archive.org/web/20140222140345/http://www.stanford.edu/group/htgg/sts145papers/rtan_2001_2.pdf |archive-date=2014-02-22 |quote=<br>"The Saturn originally ran on a NEC V60 chip at 16MHz. Compare this to the PlayStation CPU ([[MIPS architecture|MIPS]] R3000A 32bit [[reduced instruction set computer|RISC]] chip) which runs are 33.8MHz, almost double the speed. According to one Sega staff member, when Nakayama first received design specifications for the PlayStation, he was 'the maddest I have ever seen him', calling up the entire R&D division to his office to shout at them. An effort was made to compensate by adding another CPU for dual operation; however, this solution made the system so hard to develop for that, according to Yu Suzuki himself, "only 1 out of 100 programmers could use the Saturn to its full potential.""}}
</ref>
</ref>


<!----- WEB, NEC ----->
<!----- WEB, NEC ----->


<ref name="ps98-145-hmw">
<ref name=ps98-145-hmw>
{{Cite web|url=http://121ware.com/support/product/data/spec/sft/sw225d-1.html |title=Model Number: PS98-145-HMW, Item Name: PC-UX/V(Rel2.0)(V60) |publisher=NEC product sheet}}
{{cite web |title=Model Number: PS98-145-HMW, Item Name: PC-UX/V(Rel2.0)(V60) |publisher=NEC product sheet |url=http://121ware.com/support/product/data/spec/sft/sw225d-1.html}}
</ref>
</ref>


<!----- WEB, GHS ----->
<!----- WEB, GHS ----->


<ref name="GHS-V850">
<ref name=GHS-V850>
{{cite web|title=V850 and RH850 Embedded Software Solutions|url=https://www.ghs.com/products/v850_development.html|website=www.ghs.com|publisher=Green Hills Software}}
{{cite web |title=V850 and RH850 Embedded Software Solutions |website=ghs.com |publisher=Green Hills Software |url=https://www.ghs.com/products/v850_development.html}}
</ref>
</ref>


<!----- WEB, MIPS ----->
<!----- WEB, MIPS ----->


<ref name="HIREC-HR5000">
<ref name=HIREC-HR5000>
{{cite web|last1=Voica|first1=Alex|title=Back to the future: 64-bit MIPS CPU explores the origins of the solar system – MIPS|url=https://www.mips.com/blog/back-to-the-future-64-bit-mips-cpu-explores-rare-asteroid/|website=www.mips.com|publisher=MIPS|language=en|date=2015-07-29|archive-url=https://web.archive.org/web/20180220033122/https://www.mips.com/blog/back-to-the-future-64-bit-mips-cpu-explores-rare-asteroid/|archive-date=2018-02-20|url-status=dead}}
{{cite web |last1=Voica |first1=Alex |title=Back to the future: 64-bit MIPS CPU explores the origins of the solar system – MIPS |website=mips.com |publisher=MIPS |language=en |date=2015-07-29 |url=https://www.mips.com/blog/back-to-the-future-64-bit-mips-cpu-explores-rare-asteroid/ |url-status=dead |archive-url=https://web.archive.org/web/20180220033122/https://www.mips.com/blog/back-to-the-future-64-bit-mips-cpu-explores-rare-asteroid/ |archive-date=2018-02-20}}
</ref>
</ref>


<ref name="MIPS64-5Kf-DS">
<ref name=MIPS64-5Kf-DS>
{{cite book|title=MIPS64 5Kf Processor Core Datasheet|date=2005-01-31|publisher=MIPS Technologies Inc.|edition=01.04|url=http://wiki.prplfoundation.org/enwiki/w/images/f/f1/MD00111-2B-4KEC-DTS-02.03.pdf|language=en|archive-url=https://web.archive.org/web/20180220033333/http://wiki.prplfoundation.org/enwiki/w/images/f/f1/MD00111-2B-4KEC-DTS-02.03.pdf|archive-date=2018-02-20|url-status=dead}}
{{cite book |title=MIPS64 5Kf Processor Core Datasheet |publisher=MIPS Technologies Inc. |edition=01.04 |language=en |date=2005-01-31 |url=http://wiki.prplfoundation.org/enwiki/w/images/f/f1/MD00111-2B-4KEC-DTS-02.03.pdf |url-status=dead |archive-url=https://web.archive.org/web/20180220033333/http://wiki.prplfoundation.org/enwiki/w/images/f/f1/MD00111-2B-4KEC-DTS-02.03.pdf |archive-date=2018-02-20}}
</ref>
</ref>


<!----- WEB, MAME DEV ----->
<!----- WEB, MAME DEV ----->


<ref name="v60-cemu">
<ref name=v60-cemu>
{{cite web|url=http://mamedev.org/source/src/emu/cpu/v60/v60.c.html |title=MAME:/src/emu/cpu/v60/v60.c |publisher=Mamedev.org |access-date=2014-02-15 |archive-url=https://web.archive.org/web/20140222070653/http://mamedev.org/source/src/emu/cpu/v60/v60.c.html |archive-date=2014-02-22 |url-status=dead}}
{{cite web |title=MAME:/src/emu/cpu/v60/v60.c |publisher=Mamedev.org |url=http://mamedev.org/source/src/emu/cpu/v60/v60.c.html |access-date=2014-02-15 |url-status=dead |archive-url=https://web.archive.org/web/20140222070653/http://mamedev.org/source/src/emu/cpu/v60/v60.c.html |archive-date=2014-02-22}}
</ref>
</ref>


<ref name="mamedev1">
<ref name=mamedev1>
{{cite web|url=http://mamedev.org/source/src/mame/drivers/segas32.c.html |title=MAME:/src/mame/drivers/segas32.c |publisher=Mamedev.org |access-date=2014-02-15 |archive-url=https://web.archive.org/web/20140403190647/http://mamedev.org/source/src/mame/drivers/segas32.c.html |archive-date=2014-04-03 |url-status=dead}}
{{cite web |title=MAME:/src/mame/drivers/segas32.c |publisher=Mamedev.org |url=http://mamedev.org/source/src/mame/drivers/segas32.c.html |access-date=2014-02-15 |url-status=dead |archive-url=https://web.archive.org/web/20140403190647/http://mamedev.org/source/src/mame/drivers/segas32.c.html |archive-date=2014-04-03}}
</ref>
</ref>


<ref name="mamedev-model1">
<ref name=mamedev-model1>
{{cite web|url=http://mamedev.org/source/src/mame/drivers/model1.c.html |title=MAME:/src/mame/drivers/model1.c |publisher=Mamedev.org |access-date=2014-02-15 |archive-url=https://web.archive.org/web/20140403180645/http://mamedev.org/source/src/mame/drivers/model1.c.html |archive-date=2014-04-03 |url-status=dead}}
{{cite web |title=MAME:/src/mame/drivers/model1.c |publisher=Mamedev.org |url=http://mamedev.org/source/src/mame/drivers/model1.c.html |access-date=2014-02-15 |url-status=dead |archive-url=https://web.archive.org/web/20140403180645/http://mamedev.org/source/src/mame/drivers/model1.c.html |archive-date=2014-04-03}}
</ref>
</ref>


<ref name="mamedev-ssv">
<ref name=mamedev-ssv>
{{cite web|url=http://mamedev.org/source/src/mame/drivers/ssv.c.html |title=MAME:/src/mame/drivers/ssv.c |publisher=Mamedev.org |access-date=2014-02-15 |archive-url=https://web.archive.org/web/20140403215238/http://mamedev.org/source/src/mame/drivers/ssv.c.html |archive-date=2014-04-03 |url-status=dead}}
{{cite web |title=MAME:/src/mame/drivers/ssv.c |publisher=Mamedev.org |url=http://mamedev.org/source/src/mame/drivers/ssv.c.html |access-date=2014-02-15 |url-status=dead |archive-url=https://web.archive.org/web/20140403215238/http://mamedev.org/source/src/mame/drivers/ssv.c.html |archive-date=2014-04-03}}
</ref>
</ref>


<ref name="mamedev-mc32">
<ref name=mamedev-mc32>
{{cite web|url=http://mamedev.org/source/src/mame/drivers/ms32.c.html |title=MAME:/src/mame/drivers/ms32.c |publisher=Mamedev.org |access-date=2014-02-15 |archive-url=https://web.archive.org/web/20140403182226/http://mamedev.org/source/src/mame/drivers/ms32.c.html |archive-date=2014-04-03 |url-status=dead}}
{{cite web |title=MAME:/src/mame/drivers/ms32.c |publisher=Mamedev.org |url=http://mamedev.org/source/src/mame/drivers/ms32.c.html |access-date=2014-02-15 |url-status=dead |archive-url=https://web.archive.org/web/20140403182226/http://mamedev.org/source/src/mame/drivers/ms32.c.html |archive-date=2014-04-03}}
</ref>
</ref>


<!----- WEB, PLANET VIRTUAL BOY ----->
<!----- WEB, PLANET VIRTUAL BOY ----->


<ref name="V810-GCC">
<ref name=V810-GCC>
{{cite web|title=A newer GCC compiler. « Virtual Boy Development Board « Forum « Planet Virtual Boy|url=http://www.planetvb.com/modules/newbb/viewtopic.php?topic_id=6456|website=www.planetvb.com|language=en|archive-url=https://web.archive.org/web/20190530010045/http://www.planetvb.com/modules/newbb/viewtopic.php?topic_id=6456|archive-date=2019-05-30|url-status=dead}}
{{cite web |title=A newer GCC compiler. « Virtual Boy Development Board « Forum « Planet Virtual Boy |website=planetvb.com |language=en |url=http://www.planetvb.com/modules/newbb/viewtopic.php?topic_id=6456 |url-status=dead |archive-url=https://web.archive.org/web/20190530010045/http://www.planetvb.com/modules/newbb/viewtopic.php?topic_id=6456 |archive-date=2019-05-30}}
</ref>
</ref>


<!----- WEB, DATAQUEST ----->
<!----- WEB, DATAQUEST ----->


<ref name="dataquest-1986">
<ref name=dataquest-1986>
[[Dataquest]], "Japanese Semiconductor Industry Service", 1st Quarter 1986, p. 18 (pdf p. 44 in [http://archive.computerhistory.org/resources/access/text/2013/04/102723432-05-01-acc.pdf this multi-volume archive])
[[Dataquest]], "Japanese Semiconductor Industry Service", 1st Quarter 1986, p. 18 (pdf p. 44 in [http://archive.computerhistory.org/resources/access/text/2013/04/102723432-05-01-acc.pdf this multi-volume archive])
</ref>
</ref>


<ref name="dataquest-1987">
<ref name=dataquest-1987>
[[Dataquest]], "Japanese Semiconductor Industry Service", 1st Quarter 1987, p. 18 (pdf p. 182 in [http://archive.computerhistory.org/resources/access/text/2013/04/102723432-05-01-acc.pdf this multi-volume archive])</ref>
[[Dataquest]], "Japanese Semiconductor Industry Service", 1st Quarter 1987, p. 18 (pdf p. 182 in [http://archive.computerhistory.org/resources/access/text/2013/04/102723432-05-01-acc.pdf this multi-volume archive])</ref>


<ref name="dataquest-1987-2">
<ref name=dataquest-1987-2>
[[Dataquest]], "Japanese Semiconductor Industry Service", 2nd Quarter 1987, p. 21 (pdf p. 223 in [http://archive.computerhistory.org/resources/access/text/2013/04/102723432-05-01-acc.pdf this multi-volume archive])</ref>
[[Dataquest]], "Japanese Semiconductor Industry Service", 2nd Quarter 1987, p. 21 (pdf p. 223 in [http://archive.computerhistory.org/resources/access/text/2013/04/102723432-05-01-acc.pdf this multi-volume archive])</ref>


<!----- WEB, COMPUTER BUSINESS REVIEW ----->
<!----- WEB, COMPUTER BUSINESS REVIEW ----->


<ref name="CBR-1">
<ref name=CBR-1>
NEC LAUNCHES V80 ANSWER TO INTEL's 80486 - Computer Business Review, 1989-03-15
NEC LAUNCHES V80 ANSWER TO INTEL's 80486 - Computer Business Review, 1989-03-15
Balcklist:www.cbronline.com/news/nec_launches_v80_answer_to_intels_80486
Balcklist:www.cbronline.com/news/nec_launches_v80_answer_to_intels_80486
</ref>
</ref>


<ref name="CBR-2">
<ref name=CBR-2>
NEC MAY HAVE THE EDGE WITH ITS 930,000 TRANSISTOR V80 ANSWER TO INTEL'S 80486 - Computer Business Review, 1989-04-06
NEC MAY HAVE THE EDGE WITH ITS 930,000 TRANSISTOR V80 ANSWER TO INTEL'S 80486 - Computer Business Review, 1989-04-06
Balcklist:www.cbronline.com/news/nec_may_have_the_edge_with_its_930000_transistor_v80_answer_to_intels_80486
Balcklist:www.cbronline.com/news/nec_may_have_the_edge_with_its_930000_transistor_v80_answer_to_intels_80486
Line 626: Line 625:
<!----- WEB, MUSEUM ----->
<!----- WEB, MUSEUM ----->


<ref name="ipsj-bungo">
<ref name=ipsj-bungo>
{{cite web|url=http://museum.ipsj.or.jp/en/computer/word/0058.html|publisher=museum.ipsj.or.jp|title=Bungo mini 5SX,Bungo mini 7SX,Bungo mini 7SD – Computer Museum |access-date=2017-04-22}}
{{cite web |title=Bungo mini 5SX,Bungo mini 7SX,Bungo mini 7SD – Computer Museum |website=museum.ipsj.or.jp |url=http://museum.ipsj.or.jp/en/computer/word/0058.html |access-date=2017-04-22}}
</ref>
</ref>


<ref name="ispj-ms4100">
<ref name=ispj-ms4100>
{{Cite web |url=http://museum.ipsj.or.jp/en/computer/mini/0027.html |publisher=museum.ipsj.or.jp | title=MS-4100 Series - Computer Museum|language=en|access-date=2018-01-07}}
{{cite web |title=MS-4100 Series - Computer Museum |language=en |website=museum.ipsj.or.jp |url=http://museum.ipsj.or.jp/en/computer/mini/0027.html |access-date=2018-01-07}}
</ref>
</ref>


<ref name="nij-ms4100">
<ref name=nij-ms4100>
{{Cite web|url=https://dbnst.nii.ac.jp/pro/detail/282|title=MS4100 Series|publisher=dbnst.nii.ac.jp|language=ja|access-date=2018-01-08}}
{{cite web |title=MS4100 Series |language=ja |website=dbnst.nii.ac.jp |url=https://dbnst.nii.ac.jp/pro/detail/282 |access-date=2018-01-08}}
</ref>
</ref>


<ref name="HP64700">
<ref name=HP64700>
{{Cite web|url=http://www.hpmuseum.net/display_item.php?hw=1086|title=HP Computer Museum|language=en|access-date=2018-01-07}}
{{cite web |title=HP Computer Museum |language=en |url=http://www.hpmuseum.net/display_item.php?hw=1086 |access-date=2018-01-07}}
</ref>
</ref>


<!----- WEB, JAXA ----->
<!----- WEB, JAXA ----->


<ref name="JAXA-Kibo">
<ref name=JAXA-Kibo>
{{cite web|title=Kibo HANDBOOK|url=http://iss.jaxa.jp/kibo/library/fact/data/kibo-handbook_en.pdf|publisher=JAXA|page=101|date=September 2007}}
{{cite web |title=Kibo HANDBOOK |publisher=JAXA |page=101 |date=September 2007 |url=http://iss.jaxa.jp/kibo/library/fact/data/kibo-handbook_en.pdf}}
</ref>
</ref>


<ref name="Kibo-EDEE">
<ref name=Kibo-EDEE>
{{cite web|title=Space Environment Data Acquisition equipment-Attached Payload (SEDA/AP)|url=http://iss.jaxa.jp/en/kiboexp/ef/seda-ap/|website=iss.jaxa.jp|publisher=JAXA|language=en|date=2007-03-30}}
{{cite web |title=Space Environment Data Acquisition equipment-Attached Payload (SEDA/AP) |website=iss.jaxa.jp |publisher=JAXA |language=en |date=2007-03-30 |url=http://iss.jaxa.jp/en/kiboexp/ef/seda-ap/}}
</ref>
</ref>


<ref name="jaxa-roadmap">
<ref name=jaxa-roadmap>
{{cite web|title=JAXA's LSI (MPU/ASIC) roadmap, p. 9; excl. front|url=https://eeepitnl.tksc.jaxa.jp/mews/en/21st/data/2-1.pdf |website=Development Status for JAXA Critical Parts, 2008|publisher=JAXA}}
{{cite web |title=JAXA's LSI (MPU/ASIC) roadmap, p. 9; excl. front |website=Development Status for JAXA Critical Parts, 2008 |publisher=JAXA |url=https://eeepitnl.tksc.jaxa.jp/mews/en/21st/data/2-1.pdf}}
</ref>
</ref>


<ref name="jaxa-status-2013">
<ref name=jaxa-status-2013>
{{cite web|title=Development Status of JAXA EEE Parts |url=https://eeepitnl.tksc.jaxa.jp/mews/jp/26th/data/2_12_1.pdf |website=Development Status for JAXA Critical Parts, 2008|publisher=JAXA}}
{{cite web |title=Development Status of JAXA EEE Parts |website=Development Status for JAXA Critical Parts, 2008 |publisher=JAXA |url=https://eeepitnl.tksc.jaxa.jp/mews/jp/26th/data/2_12_1.pdf}}
</ref>
</ref>


<ref name="jaxa-eee-parts">
<ref name=jaxa-eee-parts>
{{Cite web|url=https://eeepitnl.tksc.jaxa.jp/en/Critical_P/completed/index_e.html|title=Database of JAXA Qualified EEE Parts and Material: Critical Parts|publisher=JAXA|language=en|access-date=2018-01-07}}
{{cite web |title=Database of JAXA Qualified EEE Parts and Material: Critical Parts |language=en |publisher=JAXA |url=https://eeepitnl.tksc.jaxa.jp/en/Critical_P/completed/index_e.html |access-date=2018-01-07}}
</ref>
</ref>


<ref name="Kibo-SEE">
<ref name=Kibo-SEE>
{{cite web|title=国際宇宙ステーション「きぼう」船外プラットフォーム搭載 宇宙環境計測ミッション装置(SEDA-AP)|url=http://www.icrr.u-tokyo.ac.jp/~hmiya/5th_sympo/Goka_Chimon2010.pdf|pages=52–53|language=ja|trans-title=Space Environment Data Acquisition Equipment – Attached Payload (SEDA-AP) on the ISS - "Kibo" Exposed Facility|archive-url=https://web.archive.org/web/20180126125736/http://www.icrr.u-tokyo.ac.jp/~hmiya/5th_sympo/Goka_Chimon2010.pdf|archive-date=2018-01-26|url-status=dead}}
{{cite web |title=国際宇宙ステーション「きぼう」船外プラットフォーム搭載 宇宙環境計測ミッション装置(SEDA-AP) |pages=52–53 |language=ja |trans-title=Space Environment Data Acquisition Equipment – Attached Payload (SEDA-AP) on the ISS - "Kibo" Exposed Facility |url=http://www.icrr.u-tokyo.ac.jp/~hmiya/5th_sympo/Goka_Chimon2010.pdf |url-status=dead |archive-url=https://web.archive.org/web/20180126125736/http://www.icrr.u-tokyo.ac.jp/~hmiya/5th_sympo/Goka_Chimon2010.pdf |archive-date=2018-01-26}}
</ref>
</ref>


<!----- WEB, CODE ----->
<!----- WEB, CODE ----->


<ref name="GCC-Internal">
<ref name=GCC-Internal>
{{Cite web|url=https://gcc.gnu.org/onlinedocs/gccint/Frame-Registers.html|title=GNU Compiler Internals}}
{{cite web |title=GNU Compiler Internals |url=https://gcc.gnu.org/onlinedocs/gccint/Frame-Registers.html}}
</ref>
</ref>


<ref name="by-cygnus-1">
<ref name=by-cygnus-1>
{{cite mailing list |url=https://gcc.gnu.org/ml/gcc-patches/1999-02n/msg00703.html |title=Patch to replace CYGNUS LOCAL with EGCS LOCAL in config.sub |date=1999-02-25 |mailing-list=gcc-patches |author=[[Cygnus Solutions]] |quote=<br/>Hi Guys,<br/>I would like to submit the following patch. It renames all occurrences of CYGNUS LOCAL to EGCS LOCAL, which seems slightly more accurate! :-)<br/>Cheers<br/>Nick}}
{{cite mailing list |title=Patch to replace CYGNUS LOCAL with EGCS LOCAL in config.sub |mailing-list=gcc-patches |author=[[Cygnus Solutions]] |date=1999-02-25 |url=https://gcc.gnu.org/ml/gcc-patches/1999-02n/msg00703.html |quote=<br>Hi Guys,<br>I would like to submit the following patch. It renames all occurrences of CYGNUS LOCAL to EGCS LOCAL, which seems slightly more accurate! :-)<br>Cheers<br>Nick}}
</ref>
</ref>


<ref name="by-cygnus-2">
<ref name=by-cygnus-2>
{{cite mailing list |url=https://gcc.gnu.org/ml/gcc-patches/1999-02n/msg00704.html |title=Re: Patch to replace CYGNUS LOCAL with EGCS LOCAL in config.sub |date=1999-02-25 |mailing-list=gcc-patches |author=[[Cygnus Solutions]] |quote=<br/>Seems like a misguided exercise to me.<br/>If the changes are truly Cygnus-specific, they should not be in Egcs. Otherwise, they should be merged into the config.sub master copy (whose maintainer, by the way, in Ben!).}}
{{cite mailing list |title=Re: Patch to replace CYGNUS LOCAL with EGCS LOCAL in config.sub |mailing-list=gcc-patches |author=[[Cygnus Solutions]] |date=1999-02-25 |url=https://gcc.gnu.org/ml/gcc-patches/1999-02n/msg00704.html |quote=<br>Seems like a misguided exercise to me.<br>If the changes are truly Cygnus-specific, they should not be in Egcs. Otherwise, they should be merged into the config.sub master copy (whose maintainer, by the way, in Ben!).}}
</ref>
</ref>


<ref name="egcs">
<ref name=egcs>
{{Cite web|url=https://opensource.apple.com/source/gcc/gcc-926/config.sub.auto.html|title=gcc/gcc-926/config.sub|author=Cygnus Solutions|publisher=Apple Inc.|access-date=2018-01-07}}</ref>
{{cite web |title=gcc/gcc-926/config.sub |author=Cygnus Solutions |publisher=Apple Inc. |url=https://opensource.apple.com/source/gcc/gcc-926/config.sub.auto.html |access-date=2018-01-07}}</ref>


<ref name="newlib">
<ref name=newlib>
{{cite web|url=http://www.embedded.com/design/prototyping-and-development/4024867/Embedding-with-GNU-Newlib |title=Embedding with GNU: Newlib |publisher=Embedded |date=2001-12-28 |access-date=2014-02-15}}
{{cite web |title=Embedding with GNU: Newlib |publisher=Embedded |date=2001-12-28 |url=http://www.embedded.com/design/prototyping-and-development/4024867/Embedding-with-GNU-Newlib |access-date=2014-02-15}}
</ref>
</ref>


<ref name="Inc.1991">
<ref name=Inc.1991>
{{cite journal|author=Brett Glass|title=Answer Line|url=https://books.google.com/books?id=VlAEAAAAMBAJ&pg=PA72|date=6 May 1991|journal=InfoWorld|page=72|issn=0199-6649}}
{{cite journal |title=Answer Line |author=Brett Glass |journal=InfoWorld |page=72 |issn=0199-6649 |date=6 May 1991 |url=https://books.google.com/books?id=VlAEAAAAMBAJ&pg=PA72}}
</ref>
</ref>


<ref name="ada83cpl">
<ref name=ada83cpl>
{{cite web|url=http://archive.adaic.com/compilers/ada83cpl.html |title=Ada 83 Certified Processor List |publisher=Archive.adaic.com |date=1998-03-31 |access-date=2014-02-15}}
{{cite web |title=Ada 83 Certified Processor List |publisher=Archive.adaic.com |date=1998-03-31 |url=http://archive.adaic.com/compilers/ada83cpl.html |access-date=2014-02-15}}
</ref>
</ref>


<ref name="MV-4000">{{cite web |url=http://www.chipcatalog.com/NEC/MV-4000.htm |title=MV-4000 |publisher=Chipcatalog.com |access-date=2014-02-15 |archive-date=2018-01-07 |archive-url=https://web.archive.org/web/20180107233010/http://www.chipcatalog.com/NEC/MV-4000.htm |url-status=dead }}</ref>
<ref name=MV-4000>{{cite web |title=MV-4000 |publisher=Chipcatalog.com |url=http://www.chipcatalog.com/NEC/MV-4000.htm |access-date=2014-02-15 |url-status=dead |archive-url=https://web.archive.org/web/20180107233010/http://www.chipcatalog.com/NEC/MV-4000.htm |archive-date=2018-01-07}}</ref>
</ref>
</ref>


<ref name="ews-4800">
<ref name=ews-4800>
[http://www006.upp.so-net.ne.jp/tati/docs/48summary.txt History-of-48series] (refers to the [[:ja:EWS4800|''EWS 4800'']] NEC computers)
[http://www006.upp.so-net.ne.jp/tati/docs/48summary.txt History-of-48series] (refers to the [[:ja:EWS4800|''EWS 4800'']] NEC computers)
</ref>
</ref>
Line 706: Line 705:
<!----- WEB, KEYSIGHT ----->
<!----- WEB, KEYSIGHT ----->


<ref name="HP64758G">
<ref name=HP64758G>
{{Cite web|url=https://www.keysight.com/en/pd-64758G%3Aepsg%3Apro-pn-64758G/v70-20mhz-emulation-subsystem-512kb?lc=eng&cc=US|title=64758G V70 20MHz emulation subsystem 512KB|publisher=Keysight|language=en|access-date=2018-01-08|archive-url=https://web.archive.org/web/20180108175334/https://www.keysight.com/en/pd-64758G%3Aepsg%3Apro-pn-64758G/v70-20mhz-emulation-subsystem-512kb?lc=eng&cc=US|archive-date=2018-01-08|url-status=dead}}
{{cite web |title=64758G V70 20MHz emulation subsystem 512KB |publisher=Keysight |language=en |url=https://www.keysight.com/en/pd-64758G%3Aepsg%3Apro-pn-64758G/v70-20mhz-emulation-subsystem-512kb?lc=eng&cc=US |access-date=2018-01-08 |url-status=dead |archive-url=https://web.archive.org/web/20180108175334/https://www.keysight.com/en/pd-64758G%3Aepsg%3Apro-pn-64758G/v70-20mhz-emulation-subsystem-512kb?lc=eng&cc=US |archive-date=2018-01-08}}
</ref>
</ref>


<ref name="HP-discon">
<ref name=HP-discon>
{{Cite web|url=https://www.keysight.com/upload/cmc_upload/All/Disco_Products_not_on_site.pdf|page=97|title=Agilent Test & Measurement Discontinued Products|publisher=Keysight|access-date=2018-01-08}}
{{cite web |page=97 |title=Agilent Test & Measurement Discontinued Products |publisher=Keysight |url=https://www.keysight.com/upload/cmc_upload/All/Disco_Products_not_on_site.pdf |access-date=2018-01-08}}
</ref>
</ref>


<ref name="HP-Vseries">
<ref name=HP-Vseries>
{{Cite web|url=http://literature.cdn.keysight.com/litweb/pdf/5091-2705E.pdf |title=HP Emulators and Development Solutions for NEC V Series Microprocessors|page=13|publisher=Keysight|language=en|access-date=2018-01-07}}
{{cite web |title=HP Emulators and Development Solutions for NEC V Series Microprocessors |page=13 |publisher=Keysight |language=en |url=http://literature.cdn.keysight.com/litweb/pdf/5091-2705E.pdf |access-date=2018-01-07}}
</ref>
</ref>


<!----- WEB, GENERAL ----->
<!----- WEB, GENERAL ----->


<ref name="google-groups">
<ref name=google-groups>
{{cite web|url=https://groups.google.com/d/msg/comp.arch/o99tLF7STeE/OjX1y09VggwJ|title=Google Groups – Some comments on the NEC V60/V70 |access-date=2017-04-22}}
{{cite web |title=Google Groups – Some comments on the NEC V60/V70 |url=https://groups.google.com/d/msg/comp.arch/o99tLF7STeE/OjX1y09VggwJ |access-date=2017-04-22}}
</ref>
</ref>


<ref name="V80-rumor">
<ref name=V80-rumor>
{{cite web|title=NEC V80|url=https://groups.google.com/forum/#!topic/comp.arch/NMTvNkMzef0|website=groups.google.com|publisher=Google Groups}}</ref>
{{cite web |title=NEC V80 |website=groups.google.com |publisher=Google Groups |url=https://groups.google.com/forum/#!topic/comp.arch/NMTvNkMzef0}}</ref>


<ref name="akatsuki">
<ref name=akatsuki>
{{Cite web|url=http://www.cpushack.com/2015/12/11/akatsuki-dawn-rises-again-at-venus/|title=Akatsuki: Dawn rises again at Venus|date=11 December 2015 |language=en|access-date=2018-01-07}}
{{cite web |title=Akatsuki: Dawn rises again at Venus |language=en |date=11 December 2015 |url=https://www.cpushack.com/2015/12/11/akatsuki-dawn-rises-again-at-venus/ |access-date=2018-01-07}}
</ref>
</ref>


<ref name="EDN">
<ref name=EDN>
{{cite web|url=http://www.edn.com/electronics-news/4347599/NEC-Wraps-ARM-into-Gate-Arrays-4347599|publisher=edn.com|title=NEC Wraps ARM into Gate Arrays {{pipe}} EDN|access-date=2017-04-22}}
{{cite web |title=NEC Wraps ARM into Gate Arrays |publisher=[[EDN (magazine)|EDN]] |url=https://www.edn.com/nec-wraps-arm-into-gate-arrays/ |access-date=2017-04-22}}
</ref>
</ref>


<ref name="high-c">
<ref name=high-c>
{{cite web|title=MetaWare High C/C++|url=http://www.edm2.com/index.php/MetaWare_High_C/C%2B%2B|publisher=EDM/2}}
{{cite web |title=MetaWare High C/C++ |publisher=EDM/2 |url=http://www.edm2.com/index.php/MetaWare_High_C/C%2B%2B}}
</ref>
</ref>


<ref name="CNET-2007">
<ref name=CNET-2007>
{{cite web|title=Despite its aging design, the x86 is still in charge|url=https://www.cnet.com/news/despite-its-aging-design-the-x86-is-still-in-charge/|website=CNET|language=en}}
{{cite web |title=Despite its aging design, the x86 is still in charge |website=CNET |language=en |url=https://www.cnet.com/news/despite-its-aging-design-the-x86-is-still-in-charge/}}
</ref>
</ref>


}}
}}


== Further reading ==
==Further reading==
* <!-- ref name="isscc1986" -->{{cite conference |last1=Yano |first1=Y |last2=Iwasaki |first2=J |last3=Sato |first3=Y |last4=Iwata |first4=T |last5=Nakagawa |first5=K |last6=Ueda |first6=M |title=A 32b CMOS VLSI microprocessor with on-chip virtual memory management |conference=Solid-State Circuits Conference. Digest of Technical Papers. 1986 IEEE International |volume=XXIX |date=Feb 1986 |pages=36–37 |publisher=IEEE |s2cid=57668899 |doi=10.1109/ISSCC.1986.1156924 |quote=<br/>The execution unit (EXU) is a microprogrammed 32b data path processor which has thirty-two 32b general-purpose registers, sixteen 32b scratch-pad registers, a 64b barrel shifter, a 32b arithmetic logic unit (ALU); and a couple of control registers. Three data-buses that are running}}
* <!-- ref name="isscc1986" -->{{cite conference |last1=Yano |first1=Y |last2=Iwasaki |first2=J |last3=Sato |first3=Y |last4=Iwata |first4=T |last5=Nakagawa |first5=K |last6=Ueda |first6=M |title=A 32b CMOS VLSI microprocessor with on-chip virtual memory management |conference=Solid-State Circuits Conference. Digest of Technical Papers. 1986 IEEE International |volume=XXIX |pages=36–37 |publisher=IEEE |s2cid=57668899 |doi=10.1109/ISSCC.1986.1156924 |date=Feb 1986 |quote=<br>The execution unit (EXU) is a microprogrammed 32b data path processor which has thirty-two 32b general-purpose registers, sixteen 32b scratch-pad registers, a 64b barrel shifter, a 32b arithmetic logic unit (ALU); and a couple of control registers. Three data-buses that are running}}


* <!-- ref name="acm86" -->{{cite conference |last1=Kaneko |first1=H |last2=Miki |first2=Y |last3=Koya |first3=K |last4=Araki |first4=M |title=A 32-bit CMOS microprocessor with six-stage pipeline structure |url=https://scholar.google.com/scholar?q=%22A+32-Bit+CMOS+Microprocessor+with+Six-Stage+Pipeline+Structure%22 |url-access=subscription |conference=Proceedings of 1986 ACM Fall Joint Computer Conference |date=November 1986 |pages=1000–1007 |publisher=IEEE Computer Society Press |quote=<br/>Abstract: 32-bit microprocessors are the key devices which carry high data processing capability, that was obtained by earlier general purpose computer systems and mini-computer systems, in much lower cost. Earlier 32-bit microprocessors were limited to adopt excellent architecture and design using appropriate hardware by number of devices could be fabricated on a chip. Complex functions such as Virtual Memory management and ...
* <!-- ref name="acm86" -->{{cite conference |last1=Kaneko |first1=H |last2=Miki |first2=Y |last3=Koya |first3=K |last4=Araki |first4=M |title=A 32-bit CMOS microprocessor with six-stage pipeline structure |url=https://scholar.google.com/scholar?q=%22A+32-Bit+CMOS+Microprocessor+with+Six-Stage+Pipeline+Structure%22 |url-access=subscription |conference=Proceedings of 1986 ACM Fall Joint Computer Conference |date=November 1986 |pages=1000–1007 |publisher=IEEE Computer Society Press |quote=<br>Abstract: 32-bit microprocessors are the key devices which carry high data processing capability, that was obtained by earlier general-purpose computer systems and mini-computer systems, in much lower cost. Earlier 32-bit microprocessors were limited to adopt excellent architecture and design using appropriate hardware by number of devices could be fabricated on a chip. Complex functions such as Virtual Memory management and ...
}}
}}


* <!----- JOURNAL, CAD ----- ref name="cad" -->{{cite journal |last1=Kurosawa |first1=A. |last2=Yamada |first2=K. |last3=Kishimoto |first3=A. |last4=Mori |first4=K. |last5=Nishiguchi |first5=N. |title=A Practical CAD System Application for Full Custom VLSI Microcomputer Chips |journal=IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems |date=May 1987 |volume=6 |issue=3 |pages=364–373 |doi=10.1109/TCAD.1987.1270281 |s2cid=7394658 |issn=1937-4151 |quote=<br/>Abstract: This paper presents a practical CAD system application for layout and verification, resulting in producible full-cutom VLSI microcomputer chips. The CAD system supports three design methodologies--symbolic layout mixed with mask level layout, compaction as an optimizer, and fully automated verification. For the area optimization, the symbolic layout and compactor subsystem supports a flexible description of orthogonal layout patterns with arbitrary dimensions in a loose placement manner. The layout patterns include path data, polygonal data, and symbolic cells. For power and delay optimization, the compactor compacts layout data, decreasing both resistance and capacitance for wires and ion-implanted layers. This feature is pioneering the new generation compactor. Emphasis should be put on the fact that it can compact layout data to a format 10-15 percent smaller than that accomplished manually. The verification subsystem can detect all kinds of errors, more than 30 items. A novel feature of the electrical rule check is that it investigates complementary logic errors for CMOS circuits. The synergy of those three design methodologies has brought about several significant advantages. One is manpower reduction by more than half, in the most complicated design process for unique random logic. The other is a 1600-transistors compaction output, smaller by 365 mils/sup 2/ than that manually compacted. The circuit implementation on a chip works at more than a 15&nbsp;MHz clock rate. Another is the first silicon success. It has been accomplished in a full-custom VLSI microcomputer chip consisting of more than 100 000 transistors.}}
* <!----- JOURNAL, CAD ----- ref name="cad" -->{{cite journal |last1=Kurosawa |first1=A. |last2=Yamada |first2=K. |last3=Kishimoto |first3=A. |last4=Mori |first4=K. |last5=Nishiguchi |first5=N. |title=A Practical CAD System Application for Full Custom VLSI Microcomputer Chips |journal=IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems |volume=6 |issue=3 |pages=364–373 |s2cid=7394658 |issn=1937-4151 |doi=10.1109/TCAD.1987.1270281 |date=May 1987 |quote=<br>Abstract: This paper presents a practical CAD system application for layout and verification, resulting in producible full-cutom VLSI microcomputer chips. The CAD system supports three design methodologies--symbolic layout mixed with mask level layout, compaction as an optimizer, and fully automated verification. For the area optimization, the symbolic layout and compactor subsystem supports a flexible description of orthogonal layout patterns with arbitrary dimensions in a loose placement manner. The layout patterns include path data, polygonal data, and symbolic cells. For power and delay optimization, the compactor compacts layout data, decreasing both resistance and capacitance for wires and ion-implanted layers. This feature is pioneering the new generation compactor. Emphasis should be put on the fact that it can compact layout data to a format 10-15 percent smaller than that accomplished manually. The verification subsystem can detect all kinds of errors, more than 30 items. A novel feature of the electrical rule check is that it investigates complementary logic errors for CMOS circuits. The synergy of those three design methodologies has brought about several significant advantages. One is manpower reduction by more than half, in the most complicated design process for unique random logic. The other is a 1600-transistors compaction output, smaller by 365 mils/sup 2/ than that manually compacted. The circuit implementation on a chip works at more than a 15&nbsp;MHz clock rate. Another is the first silicon success. It has been accomplished in a full-custom VLSI microcomputer chip consisting of more than 100 000 transistors.}}


== External links ==
==External links==
* [http://itpro.nikkeibp.co.jp/article/COLUMN/20051201/225552/?SS=imgview&FD=-791347235&ST=system Die photo of the V60; at Nikkei BP (in Japanese)]
* [http://itpro.nikkeibp.co.jp/article/COLUMN/20051201/225552/?SS=imgview&FD=-791347235&ST=system Die photo of the V60; at Nikkei BP (in Japanese)]
* [http://www.shmj.or.jp/shimura/ssis_shimura2_19.htm Die photo of the V60]; at Semiconductor History Museum of Japan (in Japanese)
* [https://www.shmj.or.jp/shimura/ssis_shimura2_19.htm Die photo of the V60]; at Semiconductor History Museum of Japan (in Japanese)
* [https://cn.freeimages.com/photo/silicon-chip-1564335 Die photo of the V60], mounted on [[Pin grid array|PGA]] package (much clear, in Chinese)
* [https://www.freeimages.com/cn/photo/silicon-chip-1564335 Die photo of the V60], mounted on [[pin grid array|PGA]] package (much clear, in Chinese)
* [https://cn.freeimages.com/photo/silicon-chip-with-die-1564477 Die photo of the V60] with [[Pin grid array|PGA]] packaging, removed ceramic cap (in Chinese)
* [https://www.freeimages.com/cn/photo/silicon-chip-with-die-1564477 Die photo of the V60] with [[pin grid array|PGA]] packaging, removed ceramic cap (in Chinese)
* [http://canoro.altervista.org/cpu/fotogallery2.php?idcpu=necd70616r-16mio Photo of the V60] in [[Pin grid array|PGA]] packaging w/ ceramic cap shield; glass shield
* [http://canoro.altervista.org/cpu/fotogallery2.php?idcpu=necd70616r-16mio Photo of the V60] in [[pin grid array|PGA]] packaging w/ ceramic cap shield; glass shield
* [http://ozuma.o.oo7.jp/unix/ux-v/ Blog: PS98-145-HMW kit: "PC-UX/V" w/ 15 disks & "V60 Sub board"] for [[NEC PC-9801]] slot (in Japanese)
* [http://ozuma.o.oo7.jp/unix/ux-v/ Blog: PS98-145-HMW kit: "PC-UX/V" w/ 15 disks & "V60 Sub board"] for [[NEC PC-9801]] slot (in Japanese)
* [http://www.cpushack.com/2015/12/11/akatsuki-dawn-rises-again-at-venus/ Article: V70 in PGA packaging] and the [[H-IIA|H-IIA rocket]] (in English)
* [https://www.cpushack.com/2015/12/11/akatsuki-dawn-rises-again-at-venus/ Article: V70 in PGA packaging] and the [[H-IIA|H-IIA rocket]] (in English)
* [http://www.retroclinic.com/leopardcats/vrtwin/vrtwin.htm Photo of NEC V60 CPU board] of the [[Virtua Racing|Sega Virtua Racing]] (in English)
* [http://www.retroclinic.com/leopardcats/vrtwin/vrtwin.htm Photo of NEC V60 CPU board] of the [[Virtua Racing|Sega Virtua Racing]] (in English)
* [http://www.system16.com/hardware.php?id=709 Site: "System 16"] - [[List of Sega arcade system boards#Sega System 32|Sega System 32]] Hardware (in English)
* [http://www.system16.com/hardware.php?id=709 Site: "System 16"] - [[List of Sega arcade system boards#Sega System 32|Sega System 32]] Hardware (in English)
Line 767: Line 766:
* Original documents for the V60 (μPD70616) & V70 (μPD70632) is available from [http://mess.redump.net/datasheets/nec/ here].
* Original documents for the V60 (μPD70616) & V70 (μPD70632) is available from [http://mess.redump.net/datasheets/nec/ here].
* Datasheets for the AFPP (μPD72691) is available from [http://www.datasheetarchive.com/uPD72691-datasheet.html here].
* Datasheets for the AFPP (μPD72691) is available from [http://www.datasheetarchive.com/uPD72691-datasheet.html here].
* [https://www.renesas.com/en-us/products/microcontrollers-microprocessors/v850.html Renesas V850 Family web site]
* [https://www.renesas.com/us/en/products/microcontrollers-microprocessors/other-mcus-mpus/v850-family-mcus Renesas V850 Family web site]
* [https://www.renesas.com/en-us/products/microcontrollers-microprocessors/rh850.html Renesas RH850 Family web site]
* [https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rh850-automotive-mcus Renesas RH850 Family web site]

<!-- * [https://www.cpu-world.com/forum/viewtopic.php?t=19572 Photos of the V60 and V70 in their packaging] -->
<!-- * [https://www.cpu-world.com/forum/viewtopic.php?t=19572 Photos of the V60 and V70 in their packaging] -->

{{NEC Corporation}}
{{NEC Corporation}}
[[Category:NEC microprocessors|V60|V70|V80|AFPP|NEC V60|NEC V70|NEC V80|NEC AFPP]]
[[Category:NEC microprocessors|V60|V70|V80|AFPP|NEC V60|NEC V70|NEC V80|NEC AFPP]]

Revision as of 23:43, 13 June 2023

NEC V60 / V70 / V80 / AFPP
Die shot of NEC V60 microprocessor
Name "V60 D70616" in bottom center
General information
LaunchedV60: 1986
V70: 1987
V80: 1989
AFPP: 1989
Common manufacturer
Performance
Max. CPU clock rateV60: 16 MHz
V70: 20/25 MHz
V80: 25/33 MHz
AFPP: 20  MHz
Data widthV60: 16 (int. 32)
V70: 32
V80: 32
Address widthV60: 24 (int. 32)
V70: 32
V80: 32
Virtual address width32 Linear[1]
Cache
L1 cacheV80: 1K/1K
Architecture and classification
ApplicationEmbedded,
Minicomputer,
Arcade game
Technology nodeV60: 1.5/1.2 μm
V70: 1.5/1.2 μm
V80: 0.8 μm
AFPP: 1.2 μm
Microarchitecture"V60/V70", "V80"
Instruction setNEC V60-V80[1]
Extensions
  • V80: atomic
Number of instructionsV60/V70: 119
V80: 123
Physical specifications
Transistors
  • V60: 375K
    V70: 385K
    V80: 980K
    AFPP: 433K
Co-processorAFPP (μPD72691)
Packages
  • V60: 68-pin PGA
    V60: 120-pin QFP
  • V70: 132-pin PGA
  • V70: 208-pin QFP
  • V80: 280-pin PGA
  • AFPP: 68-pin PGA
Products, models, variants
Product code names
  • μPD70616R-16
  • μPD70615GD-16
  • μPD70632R-20
  • μPD70632R-25
  • μPD70632GD-20
  • μPD70832R-25
  • μPD70832R-33
  • μPD72691R-20
History
PredecessorV20-V50
SuccessorV800 Series

The NEC V60[1][2] is a CISC microprocessor manufactured by NEC starting in 1986. Several improved versions were introduced with the same instruction set architecture (ISA), the V70 in 1987, and the V80 and AFPP in 1989. They were succeeded[3] by the V800 product families, which is currently produced by Renesas Electronics.

The V60 family includes a floating-point unit[4] (FPU) and memory management unit (MMU) and real-time operating system (RTOS) support for both Unix-based user-application-oriented systems[5] and I-TRON–based hardware-control-oriented embedded systems. They can be used in a multi-cpu lockstep fault-tolerant mechanism named FRM. Development tools included Ada certified system MV-4000, and an in-circuit emulator (ICE).

The V60/V70/V80's applications covered a wide area, including circuit switching telephone exchanges, minicomputers, aerospace guidance systems,[6] word processors, industrial computers, and various arcade games.

Introduction

NEC V60[2][1] is a CISC[7] processor manufactured by NEC starting in 1986.[8] It was the first 32-bit general-purpose microprocessor commercially available in Japan.[9]

Based on a relatively traditional design for the period,[10][11][12][13][14] the V60 was a radical departure from NEC's previous, 16-bit V–series processor, the V20-V50,[15] which were based on the Intel 8086 model,[7] although the V60 had the ability to emulate the V20/V30.[1]: §10 

According to NEC's documentation, this computer architectural change was due to the increasing demands for, and the diversity of, high-level programming languages. Such trends called for a processor with both improved performance, achieved by doubling the bus width to 32 bits, and with greater flexibility facilitated by having a large number of general-purpose registers.[2][1] These were common features of RISC chips.[16] At the time, a transition from CISC to RISC seemed to bring many benefits for emerging markets.

Today, RISC chips are common, and CISC designs—such as Intel's x86 and the 80486—which have been mainstream for several decades, internally adopt RISC features in their microarchitectures.[17][18] According to Pat Gelsinger, binary backward compatibility for legacy software is more important than changing the ISA.[19]

Overview

Instruction set

The V60 (a.k.a. μPD70616) retained a CISC architecture.[20] Its manual describes their architecture as having "features of high-end mainframe and supercomputers", with a fully orthogonal instruction set that includes non-uniform-length instructions, memory-to-memory operations that include string manipulation, and complex operand-addressing schemes.[1][2][16]

Family

The V60 operates as a 32-bit processor internally, while externally providing 16-bit data, and 24-bit address, buses. In addition, the V60 has 32 32-bit general-purpose registers.[1]: §1  Its basic architecture is used in several variants. The V70 (μPD70632), released in 1987, provides 32-bit external buses. Launched in 1989, the V80 (μPD70832)[21] is the culmination of the series: having on-chip caches, a branch predictor, and less reliance on microcode for complex operations.[22]

Software

The operating systems developed for the V60-V80 series are generally oriented toward real-time operations. Several OSs were ported to the series, including real-time versions of Unix and I-TRON.[23][24]

Because the V60/V70 was used in various Japanese arcade games, their instruction set architecture is emulated in the MAME CPU simulator.[25] The latest open-source code is available from the GitHub repository.[26]

FRM

All three processors have the FRM (Functional Redundancy Monitoring) synchronous multiple modular lockstep mechanism, which enables fault-tolerant computer systems. It requires multiple devices of the same model, one of which then operates in "master mode", while the other devices listen to the master device, in "checker mode". If two or more devices simultaneously output different results via their "fault output" pins, a majority-voting decision can be taken by external circuits. In addition, a recovery method for the mismatched instruction—either "roll-back by retry" or "roll-forward by exception"—can be selected via an external pin.[27][28][1]: §11 [21][29][30]: §3-229, 266 

Pin Name I/O Function
BMODE (FRM) Input Select the normal bus (master) mode or FRM operating (checker) mode
BLOCK (MSMAT) Output Master output requesting bus lock, i.e. freezing bus operation
Checker output indicating a mismatch has been detected
BFREZ Input Assertion for freezing bus operation
RT/EP Input Selecting input for "roll-back by retry" or "roll-forward by exception"

V60

The work on V60 processor began in 1982 with about 250 engineers under the leadership of Yoichi Yano,[31] and the processor debuted in February 1986.[32] It had a six-stage pipeline, built-in memory-management unit, and floating-point arithmetic. It was manufactured using a two-layer aluminum metal CMOS process technology, under a 1.5 μm design rule, to implement 375,000 transistors on a 13.9 × 13.8 mm2 die.[8][33] It operates at 5 V and was initially packaged in a 68-pin PGA.[34] The first version ran at 16 MHz and attained 3.5 MIPS.[33] Its sample price at launch was set at ¥100,000 ($588.23). It entered full-scale production in August 1986.[33]

Sega Virtua Racing based on Sega Model 1
(External Link)

Sega employed this processor for most of its arcade game sets in the 1990s; both the Sega System 32 and the Sega Model 1 architectures used V60 as their main CPU. (The latter used the lower-cost μPD70615 variant,[35] which doesn't implement V20/V30 emulation and FRM.[36]) The V60 was also used as the main CPU in the SSV arcade architecture—so named because it was developed jointly by Seta, Sammy, and Visco.[37] Sega originally considered using a 16 MHz V60 as the basis for its Sega Saturn console; but after receiving word that the PlayStation employed a 33.8 MHz MIPS R3000A processor, instead chose the dual-SH-2 design for the production model.[38]

In 1988, NEC released a kit called PS98-145-HMW[39] for Unix enthusiasts. The kit contained a V60 processor board that could be plugged into selected models of the PC-9800 computer series and a distribution of their UNIX System V port, the PC-UX/V Rel 2.0 (V60), on 15 8-inch floppy disks. The suggested retail price for this kit was 450,000 Yen.[39] NEC-group companies themselves intensively employed the V60 processor. Their telephone circuit switcher (exchange), which was one of the first intended targets, used V60. In 1991, they expanded their word processor products line with Bungou Mini (文豪ミニ in Japanese) series 5SX, 7SX, and 7SD, which used the V60 for fast outline font processing, while the main system processor was a 16 MHz NEC V33.[40][41] In addition, V60 microcode variants were employed in NEC's MS-4100 minicomputer series, which was the fastest one in Japan at that time.[42][43][44]

V70

V70 (μPD70632GD-20) in QFP packaging, mounted on Jaleco Mega System32 PWB

The V70 (μPD70632) improved on the V60 by increasing the external buses to 32 bits, equal to the internal buses. It was also manufactured in 1.5 μm with a two-metal layer process. Its 14.35 × 14.24 mm2 die had 385,000 transistors and was packaged in a 132-pin ceramic PGA. Its MMU had support for demand paging. Its floating-point unit was IEEE 754 compliant.[29] The 20 MHz version attained a peak performance of 6.6 MIPS and was priced, at launch in August 1987, at ¥100,000 ($719.42). The initial production capacity was 20,000 units per month.[45] A later report describes it as fabricated in 1.2-micrometer CMOS on a 12.23 × 12.32 mm2 die.[21] The V70 had a two-cycle non-pipeline (T1-T2) external bus system, whereas that of the V60 operated at 3 or 4 cycles (T1-T3/T4).[21][2] Of course, the internal units were pipelined.

The V70 was used by Sega in its System Multi 32[46] and by Jaleco in its Mega System 32. (See the photo of the V70 mounted on the latter system's printed circuit board.)[47]

Liftoff of H-IIA Flight 17, part of whose payload was the Akatsuki spacecraft (Venus Climate Orbiter)

JAXA embedded its variant of the V70, with the I-TRON RX616 operating system, in the Guidance Control Computer of the H-IIA carrier rockets, in satellites such as the Akatsuki (Venus Climate Orbiter), and the Kibo International Space Station (ISS) module.[6][48][49] The H-IIA launch vehicles were deployed domestically, in Japan, although their payloads included satellites from foreign countries. As described in JAXA's LSI (MPU/ASIC) roadmap, this V70 variant is designated "32bit MPU (H32/V70)", whose development, probably including the testing (QT) phase, was "from the middle of 1980s to early 1990s".[50]: 9 [51] This variant was used until its replacement, in 2013, by the HR5000 64-bit, 25MHz microprocessor, which is based on the MIPS64-5Kf architecture,[52] fabricated by HIREC, whose development was completed around 2011.[53][54][55]

"Space Environment Data Acquisition" for the V70 was done at the Kibo-ISS exposed facility.

Item Part No. SEE (Single Event Effect)
Monitored Item
Result[56]
V70-MPU NASDA
38510/92101xz
SEU (Single Event Upset)
SEL (Single Event Latch-up)
Not observed
(—2010/9/30)

V80

The V80 (μPD70832)[21] was launched in the spring of 1989. By incorporating on-chip caches and a branch predictor, it was declared NEC's 486 by Computer Business Review.[57][58] The performance of the V80 was two to four times than that of the V70, depending on application. For example, compared with V70, the V80 had a 32-bit hardware multiplier that reduced the number of cycles required to complete an integer-multiplication machine-instruction from 23 to 9. (For more detailed differences, see the hardware architecture section below.) The V80 was manufactured in a 0.8-micrometer CMOS process on a die area of 14.49 × 15.47 mm2, implementing 980,000 transistors. It was packaged in a 280-pin PGA, and operated at 25 and 33 MHz with claimed peak performances of 12.5 and 16.5 MIPS, respectively. The V80 had separate 1 KB on-die caches for both instructions and data. It had a 64-entry branch predictor, a 5% performance gain being attributed to it. The launch prices of the V80 were cited as equivalent to $1200 for the 33 MHz model and $960 for the 25 MHz model. Supposedly, a 45 MHz model was scheduled for 1990,[58] but it did not materialize.

The V80, with μPD72691 co-FPP and μPD71101 simple peripheral chips, was used for an industrial computer running the RX-UX832 real-time UNIX operating system and a X11-R4-based windowing system.[59][60]

AFPP (co-FPP)

The Advanced Floating Point Processor (AFPP) (μPD72691) is a co-processor for floating-point arithmetic operations.[61] The V60/V70/V80 themselves can perform floating-point arithmetic, but they are very slow because they lack hardware dedicated to such operations. In 1989, to compensate V60/V70/V80 for their fairly weak floating-point performance, NEC launched this 80-bit floating-point co-processor for 32-bit single precision, 64-bit double precision, and 80-bit extended precision operations according to IEEE 754 specifications.[4][21] This chip had a performance of 6.7 MFLOPS, doing vector-matrix multiplication while operating at 20 MHz. It was fabricated using a 1.2-micrometer double-metal layer CMOS process, resulting in 433,000 transistors on an 11.6 × 14.9 mm2 die.[4] It was packaged in a 68-pin PGA. This co-processor connected to a V80 via a dedicated bus, to a V60 or V70 via a shared main bus, which constrained peak performance.[21]

Hardware architecture

The V60/V70/V80 shared a basic architecture. They had thirty-two 32-bit general-purpose registers, with the last three of them commonly used as stack pointer, frame pointer, and argument pointer, which well matched high level language compilers' calling conventions.[29][62] The V60 and V70 have 119 machine instructions,[29] with that number being extended slightly to 123 instructions for the V80. The instructions are of non-uniform length, between one and 22 bytes,[1] and take two operands, both of which can be addresses in main memory.[21] After studying the V60's reference manual, Paul Vixie described it as "a very VAX-ish arch, with a V20/V30 emulation mode (which[...] means it can run Intel 8086/8088 software)".[63]

The V60–V80 has a built-in memory management unit (MMU)[8][61] that divides a 4-GB virtual address space into four 1-GB sections, each section being further divided into 1,024 1-MB areas, and each area being composed of 256 4-KB pages. On the V60/V70, four registers (ATBR0 to ATBR3) store section pointers, but the "area tables entries" (ATE) and page tables entries (PTE) are stored in off-chip RAM. The V80 merged the ATE and ATBR registers—which are both on-chip, with only the PTE entries stored in external RAM—allowing for faster execution of translation lookaside buffer (TLB) misses by eliminating one memory read.[21]

The translation lookaside buffers on the V60/70 are 16-entry fully associative with replacement done by microcode. The V80, in contrast, has a 64-entry 2-way set associative TLB with replacement done in hardware. TLB replacement took 58 cycles in the V70 and disrupted the pipelined execution of other instructions. On the V80, a TLB replacement takes only 6 or 11 cycles depending on whether the page is in the same area; pipeline disruption no longer occurs in the V80 because of the separate TLB replacement hardware unit, which operates in parallel with the rest of the processor.[21]

All three processors use the same protection mechanism, with 4 protection levels set via a program status word, Ring 0 being the privileged level that could access a special set of registers on the processors.[21]

All three models support a triple-mode redundancy configuration with three CPUs used in a byzantine fault–tolerance scheme with bus freeze, instruction retry, and chip replacement signals.[21][28] The V80 added parity signals to its data and address buses.[21]

String operations were implemented in microcode in the V60/V70; but these were aided by a hardware data control unit, running at full bus speed, in the V80. This made string operations about five times faster in the V80 than in the V60/V70.[21]

All floating-point operations are largely implemented in microcode across the processor family and are thus fairly slow. On the V60/V70, the 32-bit floating-point operations take 120/116/137 cycles for addition/multiplication/division, while the corresponding 64-bit floating-point operations take 178/270/590 cycles. The V80 has some limited hardware assist for phases of floating-point operations—e.g. decomposition into sign, exponent, and mantissa—thus its floating-point unit was claimed to be up to three times as effective as that of the V70, with 32-bit floating-point operations taking 36/44/74 cycles and 64-bit operations taking 75/110/533 cycles (addition/multiplication/division).[21]

Operating systems

Unix (non-real-time and real-time)

NEC ported several variants of the Unix operating system to its V60/V70/V80 processors for user-application-oriented systems, including real-time ones. The first flavor of NEC's UNIX System V port for V60 was called PC-UX/V Rel 2.0 (V60).[64] (Also refer to external link photos below.) NEC developed a Unix variant with a focus on real-time operation to run on V60/V70/V80. Called Real-time UNIX RX-UX 832, it has a double-layered kernel structure, with all task scheduling handled by the real-time kernel.[5] A multiprocessor version of RX-UX 832 was also developed, named MUSTARD (Multiprocessor Unix for Embedded Real-Time Systems).[65] The MUSTARD-powered computer prototype uses eight V70 processors. It utilizes FRM function, and can configure and change the configuration of master and checker upon request.[66][67]

I-TRON (real-time)

For hardware-control-oriented embedded systems, the I-TRON-based real-time operating system, named RX616, was implemented by NEC for the V60/V70.[27][23] The 32-bit RX616 was a continuous fork from the 16-bit RX116, which was for the V20-V50.[45][24]

FlexOS (real-time)

In 1987, Digital Research, Inc. also announced that they were planning on porting FlexOS to the V60 and V70.[68]

CP/M and DOS (legacy 16-bit)

The V60 could also run CP/M and DOS programs (ported from the V20-V50 series) using V20/V30 emulation mode.[33] According to a 1991 article in InfoWorld, Digital Research was working on a version of Concurrent DOS for the V60 at some point; but this was never released, as the V60/V70 processors were not imported to the US for use in PC clones.[69]

Development tools

C/C++ cross-compilers

As part of its development tool kit and integrated development environment (IDE), NEC had its own C-compiler, the PKG70616 "Software Generation tool package for V60/V70".[70] In addition, GHS (Green Hills Software) made its native mode C compiler (MULTI), and MetaWare, Inc. (currently Synopsys, via ARC International) made one, for V20/V30 (Intel 8086), emulation mode, called High C/C++.[71][18]: acknowledgement  Cygnus Solutions (currently Red Hat) also ported GCC as a part of an enhanced GNU compiler system (EGCS) fork,[72] but it seems not to be public.[73][74]

As of 2018, the processor-specific directory necv70 is still kept alive in the newlib C-language libraries (libc.a and libm.a) by RedHat.[75] Recent maintenance seems to be done on Sourceware.org. The latest source code is available from its git repository.[76]

MV-4100 Ada 83–certified system

The Ada 83–certified "platform system" was named MV-4000, certified as "MV4000". This certification was done with a target system, that utilized the real-time UNIX RX-UX 832 OS running on a VMEbus (IEEE 1014)–based system with a V70 processor board plugged in. The host of the cross compiler was an NEC Engineering Work Station EWS 4800, whose host OS, EWS-US/V, was also UNIX System V–based.[77][78][79][80]

The processor received Ada-83 validation from AETECH, Inc.,[77] running the Ada Compiler Validation Capability tests.[81]

System Name Certificate Number Compiler Type HOST Machine HOST OS TARGET Machine TARGET OS
NEC Ada Compiler System for EWS-UX/V to V70/RX-UX832, Version 1.0 910918S1.11217 Base NEC EWS4800/60 EWS-UX/V R8.1 NEC MV4000 RX-UX832 V1.6
NEC Ada Compiler System for EWS-UX/V(Release 4.0) to V70/RX-UX832 Version Release 4.1 (4.6.4) 910918S1.11217 Derived EWS4800 Superstation RISC Series EWS-UX/V(R4.0) R6.2 NEC MV4000 RX-UX832 V1.63
MV-4000 Features[78]
System bus: IEEE1014 D1.2/IEC821 Rev C.1 (8-slot)
Expansion bus: IEC822 Rev C or V70 cache bus (6-slot)
Built-in 100M byte (formatted) 3.5-inch SCSI hard disk
Built-in 1M-byte 3.5-inch floppy disk drive 1
Expansion SCSI (1 ch)
EMI evaluation: VCCI - 1 kind

Evaluation board kits

NEC released some plug-in evaluation board kits for the V60/V70.

Parts No. Descriptions Remarks
EBIBM-7061UNX V60 coprocessor slave board with Unix for PC-XT/AT w/ PC-UX/V Rel 2.0 (V60)
PS98-145-HMW V60 coprocessor slave board with Unix for NEC PC-9801 w/ PC-UX/V Rel 2.0 (V60)
EBIBM-70616SBC V60 single board computer for Multibus I
A part of MV-4000 V70 single board computer for VMEbus Ada 83 certified

In-circuit emulator

On-chip software debug support with the IE-V60

NEC based its own full (non-ROM and non-JTAG) probe-based in-circuit emulator, the IE-V60, on the V60, because V60/V70 chips themselves had emulator-chip capabilities. The IE-V60 was the first in-circuit emulator for V60 that was manufactured by NEC. It also had a PROM programmer function.Section 9.4, p. 205[2] NEC described it as a "user friendly software debug function". The chips have various trapping exceptions, such as data read (or write) to the user specified address, and 2 break-points simultaneously.Section 9[1]

External bus status pins

The external bus system indicates its bus status using 3 status pins, which provide three bits to signal such conditions as first instruction fetch after branch, continuous instruction fetch, TLB data access, single data access, and sequential data access. Section 6.1, p. 114 [2]

ST[2:0] Description
111 Instruction fetch
011 Instruction fetch after branch
101 "TLB" data access
100 "System base (interrupt & exception vector) table" data access
011 Single data access
010 Short-path data access (Skipped address by read-after-write)
001 Sequential data access

Debugging with V80

These software and hardware debugging functions were also built into the V80. However, the V80 did not have an in-circuit emulator, possibly because the presence of such software as real-time UNIX RX-UX 832 and real-time I-TRON RX616 rendered such a function unnecessary. Once Unix boots up, there is no need for an in-circuit emulator for developing either device drivers or application software. What is needed is a C compiler, a cross compiler, and a screen debugger—such as GDB-Tk—that works with the target device,.

HP 64758

Hewlett-Packard (currently Keysight) offered probing-pod-based in-circuit emulation hardware for the V70, built on their HP 64700 Series systems,[82][83] the successor to the HP 64000 Series, specifically the HP 64758.[84][85][82] It enables trace function like a logic analyzer. This test equipment also displays disassembled source code automatically, with trace data display and without an object file,[82] and displays high-level language source code when the source code and the object files are provided and they were compiled in DWARF format. An interface for the V60 (10339G) was also in the catalog,[85] but the long probing-pod cable required "special grade qualified" devices, i.e. the high-speed grade V70.

HP 64758: Main units, sub-units, and hosted interface

Product Description
64758A V70 20 MHz Emulator with 512KB of emulation memory
64758AX One-Time-Update
64758B V70 20MHZ Emulator with 1MB of emulation memory
64758G V70 20 MHz Emulation Subsystem, 512KB
64758H V70 20 MHz Emulation Subsystem, 1MB
64758S V70 (uPD70632)–hosted User Interface

Software options

Product Description
64879L V70 Assembler/Linker, Single-user License
64879M V70 Assembler/Linker, Media & Manuals
64879U V70 Assembler/Linker Multi-user license

Hardware options

Product Description
B3068B V70-Hosted Graphical User Interface
10339G NEC V60 Interface
E2407A NEC V70 Interface

Failings

Strategic failure of the V80 microarchitecture

In its development phase, the V80 was thought to have the same performance as the Intel 80486,[86] but they ended up having many different features. The internal execution for each instruction of the V80 needed at least two cycles, while that of i486 required one. The internal pipeline of the V80 seemed buffered asynchronous, but that of i486 was synchronous. In other words, the internal microarchitecture of V80 was CISC, but that of i486 was RISC. Both of their ISAs allowed long non-uniform CISC instructions, but the i486 had a wider, 128-bit internal cache memory bus, while that of V80 had a 32-bit width. This difference can be seen on their die photos.[21][18][22][17] The design was fatal from the performance point of view, but NEC did not change it. NEC might have been able to redesign the physical design, with the same register-transfer level, but it did not.

Lack of commercial success

The V60-V80 architecture did not enjoy much commercial success.[32]

The V60, V70, and V80 were listed in the 1989 and 1990 NEC catalogs in their PGA packaging.[87][88] A NEC catalog from 1995 still listed the V60 and V70 (not only in their PGA version but also in a QFP packaging, and also included a low-cost variant of the V60 named μPD70615, which eliminated V20/V30 emulation and FRM function), alongside their assorted chipsets; but the V80 was not offered in this catalog.[36] The 1999 edition of the same catalog no longer had any V60-V80 products.[89]

Successors

The V800 series

In 1992, NEC launched a new model, the V800 Series 32-bit microcontroller; but it did not have a memory management unit (MMU).[90] It had a RISC-based architecture, inspired by the Intel i960 and MIPS architectures, and other RISC processor instructions, such as JARL (Jump and Register Link) and load–store architecture.

At this time, the enormous software assets of the V60/V70, such as real-time Unix, were abandoned and never returned to their successors, a scenario Intel avoided.

The V800 Series had 3 major variants, the V810, V830, and V850 families.[91][3][92]

The V820 (μPD70742) was a simple variant of the V810 (μPD70732), but with peripherals.

The designation V840 may have been skipped as a designation because of Japanese tetraphobia (see page 58[36]). One Japanese pronunciation of "4" means "death", thus avoid names evoking such as Death-watch Shi-ban (the number 4 – Shi-ban) Bug (死番虫, precisely "deathwatch beetle").

As of 2005, it was already the V850 era, and the V850 family has been enjoying great success.[93] As of 2018, it is called the Renesas V850 family and the RH850 family, with V850/V850E1/V850E2 and V850E2/V850E3 CPU cores, respectively. Those CPU cores have extended the ISA of the original V810 core;[94] running with the V850 compiler.[95]

Modern software-based simulation

MAME

Because the V60/V70 had been used for many Japanese arcade games, MAME (for "Multiple Arcade Machine Emulator"), which emulates multiple old arcade games for enthusiasts, includes an CPU simulator for their instruction set architecture.[25] It is a kind of an instruction set simulator, not for developers but for users.

It has been maintained by the MAME development team. The latest open-source code, written in C++, is available from the GitHub repository.[96] The operation codes in the file optable.hxx are exactly the same as those of the V60.[1]

See also

References

  1. ^ a b c d e f g h i j k l NEC (November 1986). μPD70616 Programmer's Reference Manual (PRELIMINARY ed.). The Internet Archive, a 501(c)(3) non-profit.
    EPUB, KINDLE, PDF, PDF w/text, FULL TEXT, etc, are available
  2. ^ a b c d e f g Kani, Dr. Kenji (April 1987). Vシリーズマイクロコンピュータ 2 [V-Series Microcomputer 2] (in Japanese). Maruzen. ISBN 978-4621031575.
    本書は日本電気(株)が、わが国ではじめて開発した32ビットマイクロプロセッサV60について解説したものである。[This book explains the V60, Japanese first developed 32-bit microprocessor by NEC.]
  3. ^ a b Suzuki, Hiroaki; Sakai, Toshichika; Harigai, Hisao; Yano, Yoichi (1995-04-25). "A 0.9-V, 2.5 MHz CMOS 32-bit Microprocessor". IEICE TRANSACTIONS on Electronics. E78-C (4): 389–393. ISSN 0916-8516. Retrieved 2018-01-09.
    Summary:
    A 32-bit RISC microprocessor "V810" that has 5-stage pipeline structure and a 1 Kbyte, direct-mapped instruction cache realizes 2.5 MHz operation at 0.9 V with 2.0 mW power consumption. The supply voltage can be reduced to 0.75 V. To overcome narrow noise margin, all the signals are set to have rail-to-rail swing by pseudo-static circuit technique. The chip is fabricated by a 0.8 μm double metal-layer CMOS process technology to integrate 240,000 transistors on a 7.4 mm7.1 mm die.
  4. ^ a b c Nakayama, T.; Harigai, H.; Kojima, S.; Kaneko, H.; Igarashi, H.; Toba, T.; Yamagami, Y.; Yano, Y. (Oct 1989). "A 6.7-MFLOPS floating-point coprocessor with vector/matrix instructions". IEEE Journal of Solid-State Circuits. 24 (5): 1324–1330. Bibcode:1989IJSSC..24.1324N. doi:10.1109/JSSC.1989.572608. ISSN 1558-173X.
    Abstract:
    An 80-bit floating-point coprocessor which implements 24 vector/matrix instructions and 22 mathematical functions is described. This processor can execute floating-point addition/rounding and pipelined multiplication concurrently, under the control of horizontal-type microinstructions. The SRT division method and CORDIC trigonometrical algorithm are used for a favorable cost/performance implementation. The performance of 6.7 MFLOPS in the vector-matrix multiplication at 20 MHz has been attained by the use of parallel operations. The vector/matrix instruction is about three times faster than conventional add and multiply instructions. The chip has been fabricated in 1.2- mu m double-metal layer CMOS process containing 433000 transistors on an 11.6*14.9-mm/sup 2/ die size.
  5. ^ a b Mizuhashi, Yukiko; Teramoto, Msanoro (August 1989). "Real-time UNIX operating system: RX-UX 832". Microprocessing and Microprogramming. 27 (1–5): 533–538. doi:10.1016/0165-6074(89)90105-1.
    Abstract:
    This paper describes requirements for real-time UNIX operating systems, design concept and the implementation of RX-UX 832 real-time UNIX operating system for v60/v70 microprocessor which are NEC's 32-bit microprocessors. RX-UX 832 is implemented adopting the building block structure, composed of three modules, real-time kernel, file-server and Unix supervisor. To guarantee a real-time responsibility, several enhancements were introduced such as, fixed priority task scheduling scheme, contiguous block file system and fault tolerant functions.
    Thus, RX-UX 832 allows system designers to use standard Unix as its man-machine interface to build fault tolerant systems with sophisticated operability and provides high-quality software applications on the high performance microchips.
  6. ^ a b "Akatsuki: Dawn rises again at Venus". 11 December 2015. Retrieved 2018-01-07.
  7. ^ a b Hardenbergh, Hal W (1988). "RISCs CISCs and Fabs". Programmer's Journal. 6 (2). Avant-Garde Creations: 15.
    So far we haven't mentioned two 32-bit CISC chips, the NEC V60/70 and the AT&T WE32 family. Unlike the NEC V20/25/30/50, the V60/70 is not based on the Intel architecture. NEC is targeting the V60/70 at embedded applications, ...
    Google Books
  8. ^ a b c Yamahata, Hitoshi; Suzuki, Nariko; Koumoto, Yasuhiko; Shiiba, Tadaaki (1987-02-06). "マイクロプロセッサV60のアーキテクチャ" [Architecture of the microprocessor V60] (PDF). SIG Technical Reports; Microcomputer 43-2 (in Japanese). 1987 (8(1986-ARC-043)). Information Processing Society of Japan: 1–8. AN10096105.
    This report will describe a single chip 32-bit CMOS VLSI microprocessor V60. It has been implemented by using a double metal-layer CMOS process technology with 1.5 um design rule to integrate 375,000 transistors. It integrates the virtual memory management unit for demand paging and the floating-point operations that conform to the IEEE-754 Floating-Point Standard. By using V20/V30 emulation mode, it can directly execute object programs of 16-bit CPU (V30). Instruction formats are suited to code-generation phase of compilers. 237 instructions are provided for high-level language and operating system. It can execute 3.5 MIPS (Million Instructions per Second) at 16-MHz operation with 16-bit data bus.
  9. ^ Sakamura, Ken (April 1988). "Recent Trends" (PDF). IEEE Micro. 8 (2): 10–11. ISSN 0272-1732. Retrieved 2018-01-08.
    The V60/V70, NEC's proprietary CPU, is the first commercial-base, general-purpose, 32-bit microprocessor in Japan.
  10. ^ Rowen, C.; Przbylski, S.; Jouppi, N.; Gross, T.; Shott, J.; Hennessy, J. (1984). "A pipelined 32b NMOS microprocessor". 1984 IEEE International Solid-State Circuits Conference. Digest of Technical Papers. XXVII: 180–181. doi:10.1109/ISSCC.1984.1156607. S2CID 42147153.
    Stanford MIPS
  11. ^ Sherburne, R. W.; Katevenis, M. G. H.; Patterson, D. A.; Sequin, C. H. (1984). "A 32-bit NMOS microprocessor with a large register file". IEEE Journal of Solid-State Circuits. 19 (5): 682–689. Bibcode:1984IJSSC..19..682S. doi:10.1109/JSSC.1984.1052208. ISSN 0018-9200. S2CID 23195124.
    UCB RISC-II
  12. ^ Riordan, T.; Grewal, G. P.; Hsu, S.; Kinsel, J.; Libby, J.; March, R.; Mills, M.; Ries, P.; Scofield, R. (1988). "The MIPS M2000 system". Proceedings 1988 IEEE International Conference on Computer Design: VLSI. pp. 366–369. doi:10.1109/ICCD.1988.25724. ISBN 0-8186-0872-2. S2CID 60801545.
    MIPS M2000 (R2000)
  13. ^ Namjoo, M.; Agrawal, A.; Jackson, D. C.; Quach, L. (1988). "CMOS gate array implementation of the SPARC architecture". Digest of Papers. COMPCON Spring 88 Thirty-Third IEEE Computer Society International Conference. pp. 10–13. doi:10.1109/CMPCON.1988.4818. ISBN 0-8186-0828-5. S2CID 21078114.
    SPARC, 1st Gen.
  14. ^ Kohn, L.; Fu, S. W. (1989). "A 1,000,000 transistor microprocessor". IEEE International Solid-State Circuits Conference, 1989 ISSCC. Digest of Technical Papers. pp. 54–55. doi:10.1109/ISSCC.1989.48231. S2CID 58413700.
    Intel 860
  15. ^ NEC (June 1997). 16-BIT V SERIES; INSTRUCTIONS (5 ed.). The Internet Archive, a 501(c)(3) non-profit.
    EPUB, KINDLE, PDF, FULL TEXT, etc, are available.
  16. ^ a b Hennessy: Stanford University, John L; Patterson: University of California at Berkeley, David A. (2007). Computer Architecture: A Quantitative Approach (Fourth ed.). Morgan Kaufmann Publishers. ISBN 978-0-12-370490-0.
    Open Access: EPUB, KINDLE, PDF, FULL TEXT, etc, are available.
  17. ^ a b Fu, B.; Saini, A.; Gelsinger, P. P. (1989). "Performance and microarchitecture of the i486 processor". Proceedings 1989 IEEE International Conference on Computer Design: VLSI in Computers and Processors. pp. 182–187. doi:10.1109/ICCD.1989.63352. ISBN 0-8186-1971-6. S2CID 62082864.
    Intel 80486
    Abstract:
    The i486 microprocessor includes a carefully tuned, five-stage pipeline with an integrated 8-kB cache. A variety of techniques previously associated only with RISC (reduced-instruction-set computer) processors are used to execute the average instruction in 1.8 clocks. This represents a 2.5* reduction from its predecessor, the 386 microprocessor. The pipeline and clock count comparisons are described in detail. In addition, an onchip floating-point unit is included which yields a 4* clock count reduction from the 387 numeric coprocessor. The microarchitecture enhancements and optimizations used to achieve this goal, most of which are non-silicon-intensive, are discussed. All instructions of the 386 microprocessor and the 387 numeric coprocessor are implemented in a completely compatible fashion.
  18. ^ a b c Crawford, J.H. (February 1990). "The i486 CPU: executing instructions in one clock cycle". IEEE Micro. 10 (1): 27–36. CiteSeerX 10.1.1.126.4216. doi:10.1109/40.46766. ISSN 0272-1732.
  19. ^ "Despite its aging design, the x86 is still in charge". CNET.
  20. ^ Wade, James (1 October 1996). "A Community-Level Analysis of Sources and Rates of Technological Variation in the Microprocessor Market". Academy of Management Journal. 39 (5): 1218–1244. doi:10.2307/256997. ISSN 0001-4273. JSTOR 256997. The sponsors that did not use RISC technology were NEC, AT&T, and Followers of the TRON standard. All three of these microprocessors were specialized for users for whom performance was the highest priority. The Hitachi microprocessor followed the TRON standard, a high-performance CISC technology that, Japanese developers suggested, would be a viable alternative to RISC. The AT&T chip was portrayed as a chip suitable for building top-of-the-line, minicomputer-like computing systems. Similarly, NEC's V60 and V70 were patterned after one of NEC's 36-bit mainframe computers.
  21. ^ a b c d e f g h i j k l m n o p Komoto, Yasuhiko; Saito, Tatsuya; Mine, Kazumasa (1990-08-25). "Overview of 32-bit V-Series Microprocessor" (pdf). Journal of Information Processing. 13 (2): 110–122. ISSN 1882-6652. Retrieved 2018-01-08. Open Access
    Abstract:
    The advances in semiconductor manufacturing technology make it possible to integrate a floating-point unit and a memory management unit noto one microprocessor chip. They also permit the designers of a microprocessor to implement techniques used in the design of mainframe computers especially with regard to pipeline structures. The architecture of the V60 V70 and V80 was made possible by there advances. The V60 and V70 are NEC's first 32-bit microprocessors and include almost all the functions required by applied systems in a chip. The instruction set provides a high-level-language-oriented structure operating system sup-port functions and support functions for highly reliable systems. The V80 also employs the same architecture and achieves higher performance by means of cache memories and branch prediction mechanisms. The V80achieved a performance from two to four times higher than that of the V70.
  22. ^ a b Kaneko, Hiroaki; Suzuki, Nariko; Wabuka, Hhiroaki; Maemura, Koji (April 1990). "Realizing the V80 and its system support functions". IEEE Micro. 10 (2): 56–69. doi:10.1109/40.52947. ISSN 0272-1732. S2CID 2634866.
    Abstract:
    An overview is given of the architecture of an overall design considerations for the 11-unit, 32-b V80 microprocessor, which includes two 1-kB cache memories and a branch prediction mechanism that is a new feature for microprocessors. The V80's pipeline processing and system support functions for multiprocessor and high-reliability systems are discussed. Using V80 support functions, multiprocessor and high-reliability systems were realized without any performance drop. Cache memories and a branch prediction mechanism were used to improve pipeline processing. Various hardware facilities replaced the usual microprogram to ensure high performance.

    Kaneko, Hiraoki; Suzuki, Nariko; Wabuka, Hiroshi; Maemura, Koji (March 1990). "ditto". IEEE Micro. 10 (2). ACM: 56–69. doi:10.1109/40.52947. S2CID 2634866. |url-access=subscription
  23. ^ a b Shimojima, Takehiko; Teramoto, Masanori (1987). "V60 real-time operating system". Microprocessing and Microprogramming. 21 (1–5): 197–204. doi:10.1016/0165-6074(87)90038-X. ISSN 0165-6074.
    Abstract:
    This paper describes the requirements for 32-bit microprocessor real-time operating systems, design objectives and the implementation of the V60/V70 Real-Time Operating System (RTOS) and its programming supports.
  24. ^ a b Monden, Hiroshi; Teramoto, Takashi; Koga, Masanori (1986-03-14). "V60用アルタイムOSの検討 -32ビットI-TRONに向けて-" [Feasibility study of real-time OS for the V60 - toward for the 32-bit I-TRON -] (PDF). SIG (ARC) Technical Reports (in Japanese). 1986 (19(1985-ARC-061)). Information Processing Society of Japan: 1–8. AN10096105. Open Access
  25. ^ a b "MAME:/src/emu/cpu/v60/v60.c". Mamedev.org. Archived from the original on 2014-02-22. Retrieved 2014-02-15.
  26. ^ "mamedev/mame". GitHub. Retrieved 17 May 2020.
  27. ^ a b Kimura, S.; Komoto, Y.; Yano, Y. (April 1988). "Implementation of the V60/V70 and its FRM function". IEEE Micro. 8 (2): 22–36. doi:10.1109/40.527. S2CID 9507994.
    Abstract:
    A description is given of the V60/V70, the first commercially based, general-purpose 32-bit microprocessor in Japan. Its functions include on-chip floating-point operations, a high-level-language-oriented architecture, software debugging support, and support functions to promote a high level of system reliability. Because high reliability is so important, the V60/V70 contains functional redundancy monitoring (FRM) support functions. The discussion covers the overall design considerations, architecture, implementation, hazard detection and control, and FRM functions. The V60/V70 uses a TRON real-time operating system specification.
  28. ^ a b Yano, Y.; Koumoto, Y.; Sato, Y. (Spring 1988). V60/V70 microprocessor and its systems support functions. Digest of Papers. COMPCON Spring 88 Thirty-Third IEEE Computer Society International Conference. pp. 36–42. doi:10.1109/CMPCON.1988.4824. ISBN 0-8186-0828-5. S2CID 9186701.
    Abstract:
    Two advanced 32-bit microprocessors, the V60 and V70 (mu PD70616 and mu PD70632, respectively), and their support functions for operating systems and high-reliability systems are described. Three operating system functions, namely, the virtual memory support functions, context-switch functions, and asynchronous trap functions are examined. A basic mechanism for high-reliability-system implementation, called FRM (functional redundancy monitoring), is discussed. FRM allows a system to be designed in which multiple V60s (or V70s) form a configuration in which one processor in the system acts as a master while the others act as monitors. An FRM board that uses three V60s in its redundant core is introduced.
  29. ^ a b c d Takahashi, Toshiya; Yano, Yoichi (1988-01-21). "V60/V70アーキテクチャ" [The Architecture of V60/V70 Microprocessors] (PDF). SIG Technical Reports (in Japanese). 1988 (4(1987-ARC-069)). Information Processing Society of Japan: 57–64. AN10096105.
    This report describes the architecture of V60/V70 32-bit microprocessors. The architecture integrates various features into a single silicon die, such as a rich set of general-purpose registers, high level language oriented instruction set, floating-point data handling which is suitable for scientific applications, and the FRM (Functionality Redundancy Monitoring) operation mode which supports highly-reliable systems configuration. These features will be introduced.
  30. ^ 1987 Microcomputer Data Book: Vol. 2 (PDF). NEC. August 1986. pp. 3-229–3-232.
  31. ^ Yano, Yoichi (April 2012). "32ビット・マイコン「V60」開発物語" [Development story of the 32-bit microcomputer V60] (PDF) (in Japanese). Semiconductor History Museum of Japan. Retrieved 2018-01-08.
    "ditto" (pdf). Bulletin "Encore" (in Japanese). 75. Society of Semiconductor Industry Specialists: 17–20. April 2012. Retrieved 2018-01-08.
  32. ^ a b David T. Methé (1991). Technological Competition in Global Industries: Marketing and Planning Strategies for American Industry. Greenwood Publishing Group. p. 128. ISBN 978-0-89930-480-9.
  33. ^ a b c d Dataquest, "Japanese Semiconductor Industry Service", 1st Quarter 1986, p. 18 (pdf p. 44 in this multi-volume archive)
  34. ^ Dataquest, "Japanese Semiconductor Industry Service", 1st Quarter 1987, p. 18 (pdf p. 182 in this multi-volume archive)
  35. ^ "MAME:/src/mame/drivers/model1.c". Mamedev.org. Archived from the original on 2014-04-03. Retrieved 2014-02-15.
  36. ^ a b c NEC (Oct 1995). "SEMICONDUCTOR SELECTION GUIDE" (PDF) (10th ed.). Archived from the original (PDF) on 2016-03-04.
  37. ^ "MAME:/src/mame/drivers/ssv.c". Mamedev.org. Archived from the original on 2014-04-03. Retrieved 2014-02-15.
  38. ^ Richard Tan. "STS 145 Case Study Sega: The effect of corporate conflict on game design" (PDF). Archived from the original (PDF) on 2014-02-22.
    "The Saturn originally ran on a NEC V60 chip at 16MHz. Compare this to the PlayStation CPU (MIPS R3000A 32bit RISC chip) which runs are 33.8MHz, almost double the speed. According to one Sega staff member, when Nakayama first received design specifications for the PlayStation, he was 'the maddest I have ever seen him', calling up the entire R&D division to his office to shout at them. An effort was made to compensate by adding another CPU for dual operation; however, this solution made the system so hard to develop for that, according to Yu Suzuki himself, "only 1 out of 100 programmers could use the Saturn to its full potential.""
  39. ^ a b "Model Number: PS98-145-HMW, Item Name: PC-UX/V(Rel2.0)(V60)". NEC product sheet.
  40. ^ Bungou Mini 5RX on YouTube with "high speed outline font smoothing" TV CM
  41. ^ "Bungo mini 5SX,Bungo mini 7SX,Bungo mini 7SD – Computer Museum". museum.ipsj.or.jp. Retrieved 2017-04-22.
  42. ^ Takeo, Sakurai; Osamu, Oizumi (1986). "The outline of NEC super minicomputer MS4100 Series, NEC Technical Journal". Nec技報 (in Japanese). 39 (11). NEC Technical Journal, Vol.39 Iss.11 p.p.113-124, Nov. 1986: 113–124.
  43. ^ "MS-4100 Series - Computer Museum". museum.ipsj.or.jp. Retrieved 2018-01-07.
  44. ^ "MS4100 Series". dbnst.nii.ac.jp (in Japanese). Retrieved 2018-01-08.
  45. ^ a b Dataquest, "Japanese Semiconductor Industry Service", 2nd Quarter 1987, p. 21 (pdf p. 223 in this multi-volume archive)
  46. ^ "MAME:/src/mame/drivers/segas32.c". Mamedev.org. Archived from the original on 2014-04-03. Retrieved 2014-02-15.
  47. ^ "MAME:/src/mame/drivers/ms32.c". Mamedev.org. Archived from the original on 2014-04-03. Retrieved 2014-02-15.
  48. ^ "Kibo HANDBOOK" (PDF). JAXA. September 2007. p. 101.
  49. ^ "Space Environment Data Acquisition equipment-Attached Payload (SEDA/AP)". iss.jaxa.jp. JAXA. 2007-03-30.
  50. ^ "JAXA's LSI (MPU/ASIC) roadmap, p. 9; excl. front" (PDF). Development Status for JAXA Critical Parts, 2008. JAXA.
  51. ^ "Development Status of JAXA EEE Parts" (PDF). Development Status for JAXA Critical Parts, 2008. JAXA.
  52. ^ MIPS64 5Kf Processor Core Datasheet (PDF) (01.04 ed.). MIPS Technologies Inc. 2005-01-31. Archived from the original (PDF) on 2018-02-20.
  53. ^ HAYASHI, N. Guidance Control Computer for Launch Vehicle, NEC Technical Journal, Vol. 6, No. 1/2001, pp. 145-148
  54. ^ "Database of JAXA Qualified EEE Parts and Material: Critical Parts". JAXA. Retrieved 2018-01-07.
  55. ^ Voica, Alex (2015-07-29). "Back to the future: 64-bit MIPS CPU explores the origins of the solar system – MIPS". mips.com. MIPS. Archived from the original on 2018-02-20.
  56. ^ "国際宇宙ステーション「きぼう」船外プラットフォーム搭載 宇宙環境計測ミッション装置(SEDA-AP)" [Space Environment Data Acquisition Equipment – Attached Payload (SEDA-AP) on the ISS - "Kibo" Exposed Facility] (PDF) (in Japanese). pp. 52–53. Archived from the original (PDF) on 2018-01-26.
  57. ^ NEC LAUNCHES V80 ANSWER TO INTEL's 80486 - Computer Business Review, 1989-03-15 Balcklist:www.cbronline.com/news/nec_launches_v80_answer_to_intels_80486
  58. ^ a b NEC MAY HAVE THE EDGE WITH ITS 930,000 TRANSISTOR V80 ANSWER TO INTEL'S 80486 - Computer Business Review, 1989-04-06 Balcklist:www.cbronline.com/news/nec_may_have_the_edge_with_its_930000_transistor_v80_answer_to_intels_80486
  59. ^ OSAMU, TSUJI; SATORU, KOMIYAMA; TOSHIYUKI, DOI; TETSUYA, IWAKI (July 1992). "情報機器 工業用コンピュータμPORT-III" [Information-processing equipment.Industrial computer .MU.PORT-III.]. 明電時報 [Meiden Jiho] (in Japanese) (225): 24–32. ISSN 0386-1570.
  60. ^ HISAO, SASAKI; AKIRA, SATO; TOSHIO, KARAKAMA (May 1993). "工業用コンピュータμPORT-IIIと適用事例" [Applications of industrial computer .MU.PORT-III.]. 明電時報 [Meiden Jiho] (in Japanese) (230): 41–44. ISSN 0386-1570.
  61. ^ a b Majithi, Kenneth (1987). "The New Generation of Microprocessors". IEEE Micro. 7 (4): 4–5. doi:10.1109/MM.1987.304873. ISSN 0272-1732.
    The Japanese have been equally aggressive in their new designs of high-performance microprocessors. NEC's V60 and V70 microprocessors use architectures that include not only the MMU but also an arithmetic floating-point unit on chip. Hitachi and Fujitsu have collaborated to produce a family of microprocessors adapted to the TRON operating system. These processors incorporate instruction pipelines as well as instruction and stack caches. However, unlike NEC, their FPU function is off chip.
  62. ^ "GNU Compiler Internals".
  63. ^ "Google Groups – Some comments on the NEC V60/V70". Retrieved 2017-04-22.
  64. ^ 雅則, 寺本; 健治, 赤羽; 良彦, 和田; 由紀子, 水橋; 滋, 川又 (October 1986). "PORTING UNIX System V TO THE V60 SYSTEMS" (pdf). 全国大会講演論文集 (in Japanese). 第33回 (アーキテクチャおよびハードウェア). Information Society of Japan: 163–164. Retrieved 2018-01-07.
  65. ^ Norihisa Suzuki (January 1992). Shared Memory Multiprocessing. MIT Press. p. 195. ISBN 978-0-262-19322-1.
  66. ^ "The International Symposium on Shared Memory Multiprocessing (ISSMM)" (PDF). Scientific Information Bulletin. Vol. 16, no. 3. Office of Naval Research Asian Office. July–September 1991. pp. 2–3. Archived (PDF) from the original on March 1, 2021.
  67. ^ Suzuki, Norihisa, ed. (1992). Shared Memory Multiprocessing. MIT Press. pp. 195ff. ISBN 978-026219322-1.
  68. ^ "Digital Research launches FlexOS 286 Real-Time Manufacturing Operating System". techmonitor.ai, formerly Computer Business Review. 1987-01-15. Archived from the original on 2013-01-18. Retrieved 2018-09-15.
  69. ^ Brett Glass (6 May 1991). "Answer Line". InfoWorld: 72. ISSN 0199-6649.
  70. ^ NEC. "Microprocessors and Peripherals Data Book".
  71. ^ "MetaWare High C/C++". EDM/2.
  72. ^ Cygnus Solutions. "gcc/gcc-926/config.sub". Apple Inc. Retrieved 2018-01-07.
  73. ^ Cygnus Solutions (1999-02-25). "Patch to replace CYGNUS LOCAL with EGCS LOCAL in config.sub". gcc-patches (Mailing list).
    Hi Guys,
    I would like to submit the following patch. It renames all occurrences of CYGNUS LOCAL to EGCS LOCAL, which seems slightly more accurate! :-)
    Cheers
    Nick
  74. ^ Cygnus Solutions (1999-02-25). "Re: Patch to replace CYGNUS LOCAL with EGCS LOCAL in config.sub". gcc-patches (Mailing list).
    Seems like a misguided exercise to me.
    If the changes are truly Cygnus-specific, they should not be in Egcs. Otherwise, they should be merged into the config.sub master copy (whose maintainer, by the way, in Ben!).
  75. ^ "Embedding with GNU: Newlib". Embedded. 2001-12-28. Retrieved 2014-02-15.
  76. ^ "Newlib-cygwin.git / history". Sourceware.org. 2020. Retrieved May 22, 2020.
  77. ^ a b "Ada 83 Certified Processor List". Archive.adaic.com. 1998-03-31. Retrieved 2014-02-15.
  78. ^ a b "MV-4000". Chipcatalog.com. Archived from the original on 2018-01-07. Retrieved 2014-02-15.
  79. ^ History-of-48series (refers to the EWS 4800 NEC computers)
  80. ^ Ratcliffe, Mark, ed. (1995). Ada Yearbook 1995. IOS Press. p. 198. ISBN 9789051992182. Retrieved 22 May 2020.
  81. ^ "Ada Compiler Validation Procedures – Version 5.0". Ada Resource Association. 18 November 1997. Retrieved 22 May 2020.
  82. ^ a b c "HP Emulators and Development Solutions for NEC V Series Microprocessors" (PDF). Keysight. p. 13. Retrieved 2018-01-07.
  83. ^ "HP Computer Museum". Retrieved 2018-01-07.
  84. ^ "64758G V70 20MHz emulation subsystem 512KB". Keysight. Archived from the original on 2018-01-08. Retrieved 2018-01-08.
  85. ^ a b "Agilent Test & Measurement Discontinued Products" (PDF). Keysight. p. 97. Retrieved 2018-01-08.
  86. ^ "NEC V80". groups.google.com. Google Groups.
  87. ^ NEC (June 1989). Intelligent Peripheral Devices Data Book. The Internet Archive, a 501(c)(3) non-profit. p. 18.
  88. ^ NEC (May 1990). Single-Chip Microcontroller Data Book. The Internet Archive, a 501(c)(3) non-profit. p. 30.
  89. ^ NEC (April 1999). "SEMICONDUCTORS SELECTION GUIDE" (PDF) (17th ed.). Archived from the original (PDF) on 2018-01-08.
  90. ^ Harigai, Hisao; Kusuda, Masaori; Kojima, Shingo; Moriyama, Masatoshi; Ienaga, Takashi; Yano, Yoichi (1992-10-22). "低消費電力・低電圧動作の32ビットマイクロプロセッサV810" [A low power consumption and low voltage operation 32-bit RISC Microprocessor]. SIG Technical Reports, Information Processing Society of Japan. 1992 (82 (1992-ARC-096)): 41–48.
    Abstract:
    An advanced 32-bit RISC microprocessor for embedded control; V810 is introduced in this paper. The V810 has high performance and application specified functions. V810 dissipates less power than any other RISC chips. The V810 is the first 32-bit RISC microprocessor that operates at 2.2V.
    The V810 chip is fabricated by using 0.8μm CMOS double metal layer process technology to integrate 240,000 transistors on a 7.7×7.7mm2 die.
  91. ^ "NEC Wraps ARM into Gate Arrays". EDN. Retrieved 2017-04-22.
  92. ^ Suzuki, K.; Arai, T.; Nadehara, K.; Kuroda, I. (1998). "V830R/AV: embedded multimedia superscalar RISC processor". IEEE Micro. 18 (2): 36–47. doi:10.1109/40.671401. ISSN 0272-1732.
    Abstract:
    The V830R/AV's real-time decoding of MPEG-2 video and audio data enables practical embedded-processor-based multimedia systems.
  93. ^ NEC (May 2005). "Microcontrollers and Development Tools Selection Guide" (PDF).
  94. ^ "A newer GCC compiler. « Virtual Boy Development Board « Forum « Planet Virtual Boy". planetvb.com. Archived from the original on 2019-05-30.
  95. ^ "V850 and RH850 Embedded Software Solutions". ghs.com. Green Hills Software.
  96. ^ "MAMEdev – V60". GitHub. Retrieved 26 May 2020.

Further reading

  • Yano, Y; Iwasaki, J; Sato, Y; Iwata, T; Nakagawa, K; Ueda, M (Feb 1986). A 32b CMOS VLSI microprocessor with on-chip virtual memory management. Solid-State Circuits Conference. Digest of Technical Papers. 1986 IEEE International. Vol. XXIX. IEEE. pp. 36–37. doi:10.1109/ISSCC.1986.1156924. S2CID 57668899.
    The execution unit (EXU) is a microprogrammed 32b data path processor which has thirty-two 32b general-purpose registers, sixteen 32b scratch-pad registers, a 64b barrel shifter, a 32b arithmetic logic unit (ALU); and a couple of control registers. Three data-buses that are running
  • Kaneko, H; Miki, Y; Koya, K; Araki, M (November 1986). A 32-bit CMOS microprocessor with six-stage pipeline structure. Proceedings of 1986 ACM Fall Joint Computer Conference. IEEE Computer Society Press. pp. 1000–1007.
    Abstract: 32-bit microprocessors are the key devices which carry high data processing capability, that was obtained by earlier general-purpose computer systems and mini-computer systems, in much lower cost. Earlier 32-bit microprocessors were limited to adopt excellent architecture and design using appropriate hardware by number of devices could be fabricated on a chip. Complex functions such as Virtual Memory management and ...
  • Kurosawa, A.; Yamada, K.; Kishimoto, A.; Mori, K.; Nishiguchi, N. (May 1987). "A Practical CAD System Application for Full Custom VLSI Microcomputer Chips". IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems. 6 (3): 364–373. doi:10.1109/TCAD.1987.1270281. ISSN 1937-4151. S2CID 7394658.
    Abstract: This paper presents a practical CAD system application for layout and verification, resulting in producible full-cutom VLSI microcomputer chips. The CAD system supports three design methodologies--symbolic layout mixed with mask level layout, compaction as an optimizer, and fully automated verification. For the area optimization, the symbolic layout and compactor subsystem supports a flexible description of orthogonal layout patterns with arbitrary dimensions in a loose placement manner. The layout patterns include path data, polygonal data, and symbolic cells. For power and delay optimization, the compactor compacts layout data, decreasing both resistance and capacitance for wires and ion-implanted layers. This feature is pioneering the new generation compactor. Emphasis should be put on the fact that it can compact layout data to a format 10-15 percent smaller than that accomplished manually. The verification subsystem can detect all kinds of errors, more than 30 items. A novel feature of the electrical rule check is that it investigates complementary logic errors for CMOS circuits. The synergy of those three design methodologies has brought about several significant advantages. One is manpower reduction by more than half, in the most complicated design process for unique random logic. The other is a 1600-transistors compaction output, smaller by 365 mils/sup 2/ than that manually compacted. The circuit implementation on a chip works at more than a 15 MHz clock rate. Another is the first silicon success. It has been accomplished in a full-custom VLSI microcomputer chip consisting of more than 100 000 transistors.