Content deleted Content added
Typo fix, looks like someone forgot to check their cursor before typing |
m cite repair; |
||
Line 213:
<ref name="C2GO">{{cite web |title=C->Go translator |website=[[GitHub]] |url=https://github.com/rsc/c2go |access-date=2018-01-11 |url-status=live |archive-url=https://web.archive.org/web/20181207133222/https://github.com/rsc/c2go |archive-date=2018-12-07}}</ref>
<ref name="Go_ReleaseNotes">{{cite web |title=Go 1.5 Release Notes |url=https://golang.org/doc/go1.5 |access-date=2018-01-11 |url-status=live |archive-url=https://web.archive.org/web/20200201131555/https://golang.org/doc/go1.5 |archive-date=2020-02-01}}</ref>
<ref name="Cox_Go">{{cite web |title=Go 1.3+ Compiler Overhaul |author-first=Russ |author-last=Cox
<ref name="Scanlon_1988">{{cite book |title=8086/8088/80286 assembly language |author-last=Scanlon |author-first=Leo J. |date=1988 |publisher=Brady Books |isbn=978-0-13-246919-7 |page=[https://archive.org/details/8086808880286ass0000scan/page/12 12] |url=https://archive.org/details/8086808880286ass0000scan/page/12 |quote=[…] The [[8086]] is software-compatible with the [[8080]] at the assembly-language level. […]}}</ref>
<ref name="Kildall_1972_Optimization">{{Cite book |title=Global expression optimization during compilation |author-first=Gary Arlen |author-last=Kildall |author-link=Gary Arlen Kildall |type=Ph.D. dissertation |publisher=[[University of Washington]], Computer Science Group |___location=Seattle, Washington, USA |date=May 1972 |id=Thesis No. 20506, Technical Report No. 72-06-02}}</ref>
Line 235:
<ref name="Hughes_1982_MS-DOS">{{cite magazine |title=CP/M-86 And MS-DOS: A Comparative Analysis |series=Operating Systems |author-first=David B. |author-last=Hughes |date=November 1982 |magazine=[[PC Magazine]] |publisher=[[Software Communications, Inc.]] |issn=<!-- not assigned at this time, but already applied for --> |volume=1 |number=7 |pages=181–182, 187–190 [189<!-- quote taken from page 189 -->] |url=https://books.google.com/books?id=vy3cBZkjbZgC&pg=PA189 |access-date=2020-02-10 |url-status=live |archive-url=https://web.archive.org/web/20200210202327/https://books.google.de/books?id=vy3cBZkjbZgC&pg=PA189&dq=combined+CP/M-80+DOS+opcode+program&hl=de&sa=X&ved=2ahUKEwjO7N2Q6MfnAhVS-6QKHTPADzcQ6AEwAHoECAAQAQ#v=onepage&q=combined%20CP%2FM-80%20DOS%20opcode%20program&f=false |archive-date=2020-02-10 |quote=[…] An impressive and useful array of software development utilities is a standard feature of [[MS-DOS]]. A program that translates [[8080]] or [[Z80]] code into [[8086]] source code, a linker, and a library runtime combine with a powerful assembler to give the programmer everything needed to take full advantage of the PC's 16-bit processor. The MS-DOS translation program allows the user to translate code developed under [[CP/M-80]] or [[SB-80]] […] 8-bit operating system […] to [[MS-DOS 1.2]] or [[MS-DOS 2.0|2.0]]. Some modification beyond simple translation may be necessary to get the programs to run on 16-bit systems, so I suggest that this tool be used primarily by a technically trained user. […]}}</ref>
<ref name="Bunnell_1982_CPM">{{cite magazine |title=Gary Kildall – The Man Who Created CP/M: CP/M's Creator – An Indepth PC-Exclusive Interview with Software Pioneer Gary Kildall |series=Operating Systems |editor1-first=David Hugh |editor1-last=Bunnell |editor-link=David Hugh Bunnell |editor2-first=Jim |editor2-last=Edlin |author-first=Gary Arlen |author-last=Kildall |author-link=Gary Arlen Kildall |date=June–July 1982 |magazine=[[PC Magazine]] |publisher=[[Software Communications, Inc.]] |issn=<!-- not assigned at this time, but already applied for --> |volume=1 |number=3 |pages=32–38, 40 [35<!-- quote taken from page 35 -->] |url=https://archive.org/stream/PC-Mag-1982-06/PC-Mag-1982-06_djvu.txt |access-date=2020-01-17 |quote=[…] PC: What are some of the complexities involved in translating a program from [[8080]] to [[8086]] form? [[Gary Arlen Kildall|Kildall]]: Straight translations at the source program level you can do pretty much mechanically. For example, an 8080 "Add immediate 5" instruction turns into an "Add AL 5" on the 8086 — very straightforward translation of the op codes themselves. The complexity in [[mechanical translation]] comes from situations such as this: The 8080 instruction DAD H takes the HL register and adds DE to it. For the 8086 the equivalent instruction would be something like ADD DX BX, which is fine, no particular problem. You just say the DX register is the same as HL and BX the same as DE. The problem is that the 8086 instruction has a side effect of setting the zero flag, and the 8080 instruction does not. In mechanical translation you end up doing something like saving the flags, restoring the flags, doing some shifts and rotates, and so forth. These add about five or six extra instructions to get the same semantic effect. There are a lot of sequences in 8080 code that produce very strange sequences in 8086 code; they just don't map very well because of flag registers and things of that sort. The way we get software over is a thing called XLT-86. It's been out six months or so. PC: By "better" code do you mean smaller? Kildall: Twenty percent smaller than if you just took every op code and did a straight translation, saving the registers to preserve semantics. PC: How does the size of the translated program compare to the 8080 version? Kildall: If you take an 8080 program, move it over to 86 land and do an XLT-86 translation, you'll find that it is roughly 10 to 20 percent larger. With 16-bit machines it's more difficult to address everything; you get op codes that are a little bit bigger on the average. An interesting phenomenon is that one of the reasons you don't get a tremendous speed increase in the 16-bit world is because you're running more op codes over the data bus. […]}}</ref>
<ref name="Laws_2014_IEEE">{{Cite web |title=Legacy of Gary Kildall: The CP/M IEEE Milestone Dedication |author-first1=Robert |author-last1=Huitt |author-first2=Gordon |author-last2=Eubanks |author-link2=Gordon Eubanks |author-first3=Thomas "Tom" Alan |author-last3=Rolander |author-link3=Thomas Alan Rolander |author-first4=David |author-last4=Laws |author-first5=Howard E. |author-last5=Michel |author-first6=Brian |author-last6=Halla |author-first7=John Harrison |author-last7=Wharton |author-link7=John Harrison Wharton |author-first8=Brian |author-last8=Berg |author-first9=Weilian |author-last9=Su |author-first10=Scott |author-last10=Kildall |author-link10=Scott Kildall |author-first11=Bill |author-last11=Kampe |editor-first=David |editor-last=Laws |date=2014-04-25 |___location=Pacific Grove, California, USA |type=Video transscription |id=CHM Reference number: X7170.2014 |publisher=[[Computer History Museum]] |url=https://archive.computerhistory.org/resources/access/text/2014/06/102746909-05-01-acc.pdf |access-date=2020-01-19 |url-status=live |archive-url=https://web.archive.org/web/20141227142045/http://archive.computerhistory.org/resources/access/text/2014/06/102746909-05-01-acc.pdf |archive-date=2014-12-27 |quote=[…] [[Thomas Alan Rolander|Rolander]]: I mentioned earlier that [[Gary Arlen Kildall|Gary]] liked to approach a problem as an architect. […] And he would draw the most beautiful pictures of his data structures. […] And when he finished that […] and was convinced those data structures were now correct, he would go into just an unbelievable manic coding mode. He would just go for as many as 20 hours a day […] he was just gone during these periods of time. On a couple of those occasions, when he'd get something running the first time, which could be in the middle of night. And all you who have written software have seen that, for example, that the first time it comes up on the screen,
<ref name="Wharton_1994">{{Cite journal |title=Gary Kildall, industry pioneer, dead at 52: created first microcomputer languages, disk operating systems |journal=[[Microprocessor Report]] |publisher=[[MicroDesign Resources Inc.]] (MDR) |author-first=John Harrison |author-last=Wharton |author-link=John Harrison Wharton |volume=8 |number=10 |date=1994-08-01 |url=http://tech-insider.org/personal-computers/research/1994/0801.html |access-date=2016-11-18 |url-status=live |archive-url=https://web.archive.org/web/20161118222925/http://tech-insider.org/personal-computers/research/1994/0801.html |archive-date=2016-11-18 |quote=[…] Ironically, many of the techniques [[Gary Arlen Kildall|Gary]] pioneered are being rediscovered now, ten years later. [[Apple Computer|Apple]] and [[Digital Equipment Corporation|DEC]] are touting [[binary recompilation]] as a "new" technology for porting existing software to the [[PowerPC]] or [[DEC Alpha|Alpha]] architecture. Actually, DRI introduced an [[8080]]-to-[[8086]] binary recompiler in the early 1980s. […]}}</ref>
<ref name="SPA_1995">{{cite web |title=SPA Award to Dr. Gary A.Kildall: 1995 SPA Lifetime Achievement Award Winner |date=1995-03-13 |publisher=[[Software Publishers Association]] (SPA) |via=www.digitalresearch.biz |url=https://www.digitalresearch.biz/kildallr.htm |access-date=2019-12-21 |url-status=live |archive-url=https://web.archive.org/web/20191221150356/https://www.digitalresearch.biz/kildallr.htm |archive-date=2019-12-21 |quote=[…] [[Gary Arlen Kildall|Kildall]] founded [[Digital Research, Inc.]] (DRI) in 1976, which is now part of [[Novell]]. […] In the 1980's, DRI introduced a [[binary recompiler]]. […]}}</ref>
Line 251:
<ref name="Garetz_1980_Sorcim">{{cite news |title=According to Garetz… |author-first=Mark |author-last=Garetz |newspaper=[[InfoWorld]] – News For Microcomputer Users |issn=0199-6649 |publisher=[[Popular Computing, Inc.]] |date=1980-12-22 |volume=2 |issue=23 |page=12 |url=https://books.google.com/books?id=nD4EAAAAMBAJ&pg=PT11 |access-date=2020-01-18 |url-status=live |archive-url=https://web.archive.org/web/20200201163107/https://books.google.com/books?id=nD4EAAAAMBAJ&pg=PT11&lpg=PT11 |archive-date=2020-02-01 |quote=[…] Last week was the semi-annual [[California Computer Swap Meet]]. This event is organized by John Craig […] [[Sorcim]] […] was debuting […] new products at the show […] Their other product was TRANS-86. TRANS-86 will take any [[CP/M]] compatible [[8080]]/[[8085]]/[[Z80|Z-80]] source code file and translate it into [[8086]] code. You can then assemble the new file with ACT-86. […]}}</ref>
<ref name="BYTE_1980_86-DOS">{{cite magazine |title=86-DOS – 8086 OPERATING SYSTEM - $95 |author=Seattle Computer Products |author-link=Seattle Computer Products |magazine=[[BYTE]] |issn=0360-5280 |id={{CODEN|BYTEDJ}} |date=August 1980 |volume=5 |number=8 |publisher=[[BYTE Publications Inc.]] |type=Advertisement |page=173 |url=https://archive.org/stream/byte-magazine-1980-08/1980_08_BYTE_05-08_The_Forth_Language#page/n173/mode/2up |access-date=2013-08-18 |url-status=live |archive-url=https://web.archive.org/web/20170405025551/https://archive.org/stream/byte-magazine-1980-08/1980_08_BYTE_05-08_The_Forth_Language |archive-date=2017-04-05 |quote=[…] 1. Read [[Z80]] source code file written in [[CP/M]] format and convert to [[86-DOS]] format. 2. Translator program translates Z80 source code to [[8086]] source code. 3. Resident assembler assembles the translated 8086 source code to 8086 [[object code]]. 4. Minor hand correction and optimization. (A recent 19K Z80 program translation took us about four hours to fix up. Even without optimization, it ran twice as fast as the original! […])}} [https://tech-insider.org/personal-computers/research/acrobat/8008-a.pdf<!-- https://web.archive.org/web/20200201163325/https://tech-insider.org/personal-computers/research/acrobat/8008-a.pdf -->]</ref>
<ref name="ARC_1988_Transpiler">{{anchor|ARC-1988}}{{cite magazine |title=Aus BASIC mach C: B→C Transpiler |trans-title=Turn BASIC into C: B→C Transpiler |author=ARC-Softwaresystems |___location=Esslingen, Germany |type=Advertisement |language=de |magazine=
<ref name="Pountain_1989">{{anchor|Pountain-1989}}{{cite magazine |title=Configuring parallel programs, Part 1: The Occam Transpiler, now under development, will make writing software for parallel processing easier |author-first=Dick |author-last=Pountain |magazine=[[BYTE (magazine)|BYTE]] |publisher=[[McGraw-Hill, Inc.]] |issn=0360-5280 |volume=14 |number=13 |series= |date=December 1989 |id=<!-- |ia=byte-magazine-1989-12 --> ark:/13960/t34188734 |pages=349–352 |url=https://archive.org/details/byte-magazine-1989-12/page/n382/mode/1up |access-date=2022-01-06 |quote-page=350 |quote=[…] The name ''Transpiler'' is meant to suggest a combination of [[transputer]] and [[compiler]], in just the same way that ''transputer'' was coined from ''[[transistor]]'' and ''[[computer]]'' (i.e., a computer that is also a component). […]}} (NB. Uses the term ''Occam transpiler'' as a synonym for a source-to-source compiler working as a [[pre-processor]] that takes a normal [[occam (programming language)|Occam]] program as input and derives a new Occam source code as output with link-to-channel assignments etc. added to it thereby ''[[computer configuration|configuring]]'' it for [[parallel processing (computing)|parallel processing]] to run as efficient as possible on a network of [[transputer]]s.)</ref>
<ref name="Sector7_1993_Transpiler">{{cite news |title=Transpiler |author=Sector 7 Software Limited |___location=Bedford, Bedfordshire, UK |newspaper=[[Official Gazette of the United States Patent and Trademark Office]] |volume=1157 |edition=1 |date=1993-12-07 |orig-date=1992-09-22 |publisher=[[U.S. Patent and Trademark Office]] |page=TM 81 |series=Class 9 |id=SN 74-316.610 |url=https://books.google.com/books?id=Aokm04NulboC&pg=RA1-PA81 |access-date=2020-01-18 |url-status=live |archive-url=https://web.archive.org/web/20200201130513/https://books.google.de/books?id=Aokm04NulboC&pg=RA1-PA81&lpg=RA1-PA81&redir_esc=y |archive-date=2020-02-01 |quote=[…] Priority claimed under Sec. 44(D) on United Kingdom Application No. 1495953, filed 1992-03-31 Reg. No. A1495953, dated 1992-03-31, expires 1999-03-31. For computer software and programs (U.S. Cl. 38). First use 1991-08-01, in commerce 1991-08-01.}} (NB. This company develops products such as VX/BASIC, a BASIC-to-C transpiler for [[DEC VMS]]. Despite their claim, theirs is not the first public use of the term transpiler, see i.e. [[#ARC-1988|ARC's BASIC-to-C transpiler]] for the [[Commodore Amiga]] in 1988 and the [[#Pountain-1989|Occam Transpiler]] by Concurrent Technology Systems (CTS)<!-- by Meier and Wespi --> in 1989.)</ref>
<ref name="Ocam1">{{cite web |title=Overview |work=Js_of_ocaml - Reference Manual |publisher=Ocsigen |url=http://ocsigen.org/js_of_ocaml/manual/overview |access-date=2014-10-08
<ref name="J2EIF">{{cite book |title=J2Eif Research Page – Chair of Software Engineering |doi=10.1007/978-3-642-21952-8_4 |publisher=Se.inf.ethz.ch |url=http://se.inf.ethz.ch/research/j2eif/ |access-date=2014-07-08 |url-status=live |archive-url=https://web.archive.org/web/20200101165402/http://se.inf.ethz.ch/research/j2eif/ |archive-date=2020-01-01}}</ref>
<ref name="C2EIF">{{cite web |title=C2Eif Research Page – Chair of Software Engineering |publisher=Se.inf.ethz.ch |url=http://se.inf.ethz.ch/research/c2eif/ |access-date=2014-07-08 |url-status=live |archive-url=https://web.archive.org/web/20200101165402/http://se.inf.ethz.ch/research/c2eif/ |archive-date=2020-01-01}}</ref>
| |||