Meta tags:
Headings (most frequently used words):
cross, early, compilers, and, 1990s, compiler, contents, use, canadian, timeline, of, gcc, compilation, manx, aztec, microsoft, free, pascal, clang, plan, see, also, references, external, links, history, 1980s, 1987, late, net, beyond,
Text of the page (most frequently used words):
the (189), and (102), for (89), cross (85), #compiler (62), was (37), that (37), with (34), code (33), #compilers (33), microsoft (32), machine (31), windows (26), this (25), platform (25), which (25), target (25), from (22), build (22), language (21), edit (21), systems (20), gcc (20), dos (20), like (19), embedded (18), system (18), compilation (18), compile (18), aztec (18), development (17), linux (16), used (16), but (15), other (15), operating (14), tools (14), support (13), architecture (13), can (13), platforms (13), msc (13), using (11), also (11), its (11), native (11), compiling (11), compiled (11), will (11), were (11), host (11), programming (10), time (10), are (10), first (10), run (10), bit (10), use (9), source (9), environment (9), free (9), pascal (9), version (9), not (9), when (9), where (9), then (9), runtime (9), their (9), languages (8), developers (8), available (8), software (8), including (8), example (8), studio (8), provided (8), program (8), wikipedia (7), computer (7), has (7), another (7), gnu (7), history (7), canadian (7), had (7), provide (7), still (7), programs (7), machines (7), processor (7), visual (7), 1980s (7), running (7), all (6), assembly (6), libraries (6), toolchain (6), building (6), set (6), based (6), scratchbox (6), clang (6), versions (6), apple (6), commodore (6), executable (6), would (6), such (6), net (6), applications (6), 1990s (6), application (6), c86 (6), than (6), early (6), one (6), manx (6), virtual (6), search (5), mobile (5), about (5), may (5), page (5), links (5), different (5), retrieved (5), devices (5), developed (5), ibm (5), variety (5), create (5), multiple (5), arm (5), basic (5), unix (5), required (5), just (5), same (5), more (5), processors (5), released (5), both (5), today (5), offered (5), throughout (5), library (5), 1987 (5), new (5), contents (4), under (4), you (4), articles (4), hardware (4), uclibc (4), android (4), firmware (4), very (4), scripts (4), i386 (4), archived (4), computers (4), called (4), assembler (4), done (4), have (4), internal (4), executables (4), object (4), built (4), level (4), while (4), common (4), produce (4), several (4), market (4), generation (4), link (4), practice (4), until (4), could (4), targeted (4), pass (4), into (4), main (4), small (4), only (4), most (4), many (4), later (4), runs (4), output (4), path (4), binutils (4), hide (4), move (4), sidebar (4), toggle (3), view (3), terms (3), non (3), july (3), wayback (3), 2012 (3), list (3), java (3), shell (3), boot (3), proprietary (3), single (3), memory (3), database (3), general (3), architectures (3), crosstool (3), toolchains (3), x86 (3), references (3), supported (3), fenwick (3), 2008 (3), timeline (3), original (3), because (3), three (3), see (3), does (3), plan (3), able (3), switch (3), via (3), make (3), beginning (3), capable (3), even (3), capability (3), they (3), directly (3), clr (3), core (3), allows (3), across (3), day (3), took (3), advantage (3), produced (3), written (3), binding (3), some (3), transferred (3), device (3), similar (3), what (3), who (3), calling (3), linked (3), collection (3), distinct (3), programmers (3), current (3), company (3), notable (3), 8086 (3), rom (3), without (3), these (3), actually (3), executed (3), algol (3), read (3), file (3), table (2), contact (2), privacy (2), policy (2), text (2), additional (2), foundation (2), 2026 (2), categories (2), french (2), expanded (2), short (2), description (2), wikidata (2), org (2), php (2), open (2), iot (2), project (2), buildroot (2), glibc (2), dietlibc (2), video (2), consumer (2), electronics (2), board (2), package (2), tutorial (2), whole (2), either (2), libc (2), utilized (2), usually (2), win32 (2), mac (2), freebsd (2), targets (2), external (2), llvm (2), fortran (2), masm (2), obsolete (2), automake (2), october (2), 1984 (2), name (2), needed (2), canada (2), national (2), parties (2), mingw (2), between (2), driver (2), itself (2), option (2), linker (2), producing (2), files (2), exists (2), must (2), before (2), compatible (2), side (2), allowing (2), those (2), compatibility (2), mono (2), offer (2), emulators (2), require (2), configuration (2), framework (2), layer (2), routines (2), themselves (2), api (2), beyond (2), older (2), longer (2), instead (2), continues (2), late (2), continued (2), over (2), left (2), turned (2), companies (2), disappeared (2), release (2), emerging (2), mixed (2), through (2), introduced (2), rather (2), favoured (2), static (2), generally (2), linking (2), type (2), during (2), handheld (2), symbol (2), particular (2), stack (2), there (2), together (2), convention (2), binary (2), now (2), operations (2), interpreter (2), becoming (2), industry (2), projects (2), larger (2), interfaces (2), emerged (2), years (2), made (2), own (2), two (2), kernel (2), creating (2), often (2), choice (2), being (2), less (2), mode (2), although (2), legacy (2), 6502 (2), involves (2), programmer (2), necessary (2), chrooted (2), always (2), game (2), dreamcast (2), requires (2), each (2), script (2), 68c (2), z80 (2), practical (2), help (2), information (2), slower (2), uses (2), slow (2), differs (2), coding (2), jvm (2), limited (2), resources (2), microwave (2), useful (2), tracing (2), execution (2), appearance (2), upload (2), changes (2), article (2), log (2), account (2), donate (2), menu (2), add, topic, cookie, statement, statistics, conduct, legal, safety, contacts, disclaimers, apply, site, agree, registered, trademark, profit, organization, wikimedia, inc, creative, commons, attribution, sharealike, license, rendered, parsoid, last, edited, utc, hidden, sources, webarchive, template, theory, https, index, title, cross_compiler, oldid, 1366850989, robotics, lightweight, browsers, micropython, misra, capl, ada, win, real, light, weight, distribution, yocto, toybox, stand, alone, openembedded, busybox, bitbake, almquist, musl, lwip, barebox, loaders, vendor, lock, uefi, rooting, playstation, jailbreak, ios, jailbreaking, homebrew, games, hacking, defective, design, crippleware, closed, custom, controls, soc, raspberry, microcontroller, footprint, fpga, hypervisor, bootloader, asic, subject, rarely, avec, sous, pour, clear, structured, scratch, sde, das, eldk, kit, openwrt, rewrite, helps, helpful, desired, lilypond, grand, unified, builder, gub, toolkit, wiki, reference, configuring, march, 2010, call, december, 2007, utility, inside, macintosh, ritchie, 1593, 1002, 1538, 7305, tb00054, doi, 1577, bell, laboratories, technical, journal, evolution, sharing, 2004, crossgcc, crosses, tombstone, diagram, heterogenous, distinguish, independent, makefiles, natively, select, want, flag, chosen, fpc, cpu_target, os_target, yet, ppcxxx, xxx, ppc386, go32v2, oses, however, resulting, ross, x64, ppcrossx64, predecessors, become, popular, area, since, unixes, comprise, familiar, xvt, remote, deployment, environments, little, unlike, days, gone, mapping, command, line, 2001, formed, ide, mixing, 2005, 2003, binaries, providing, console, well, ran, 00c, bundled, forerunner, off, share, latest, greatest, features, bundle, already, decade, old, smaller, compete, niche, markets, backwardly, compliant, focused, remained, extended, assemblies, form, allow, passing, degree, newer, best, practices, cmm, maturity, model, reuse, monolithic, dynamic, thunk, workgroups, gui, ansi, retail, pdt3100, take, bought, motorola, serial, cable, barcode, reader, 8088, inventory, technologies, parameters, reverse, order, return, values, rules, work, rule, persisted, persists, known, register, process, interlanguage, mix, garbage, managed, simulated, qbasic, quickbasic, converted, everything, assembled, noted, efficient, optimizer, good, mission, critical, parts, considered, rewriting, fact, taken, lowest, multi, disciplinary, growth, writing, user, higher, need, long, been, modules, tweaked, efficiency, rest, after, assembling, california, purchase, product, borland, started, switching, follow, present, state, products, easy, techniques, part, clarion, clipper, shorter, others, dating, back, rebranded, lattice, thomas, james, goodnow, principal, became, author, finally, ability, low, per, capita, individual, amounted, uncommon, interface, manufacturer, cottage, paravirtualization, burner, hex, them, generating, added, transitory, robust, baseline, demise, did, c65, created, family, continuing, internet, distributions, exist, 68k, amiga, prodos, professional, macs, compatibles, jersey, shrewsbury, method, popularly, combination, specialized, sandboxes, sandbox, having, extra, paths, facilities, deceive, believes, intended, cpu, error, slowly, comparison, methods, moved, function, proot, packages, notion, cases, should, undefined, default, artifacts, whether, represents, otherwise, setting, irrelevant, consider, names, relative, shifted, grandson, son, libtool, autoconf, autotools, portion, choose, full, unreliable, alternative, containing, essential, components, newlib, standard, bin, copy, especially, important, therefore, correctly, sent, configured, normally, creates, following, bash, configure, supports, home, 1979, generated, aided, porting, alternate, 120, too, mainframe, 370, cap, zcode, 1969, due, lack, cost, showed, paper, tape, gecos, pdp, ken, thompson, section, adding, missing, needs, expansion, term, came, issues, discussion, political, instance, provides, named, turn, posix, netbsd, end, result, copied, four, involved, technique, much, convenient, given, fast, impractically, macos, typically, destined, usable, mips, resolves, reasons, paradigm, ideal, enthusiasts, developing, emulator, future, bootstrapping, complicated, any, regardless, underlying, server, farm, wish, highly, oven, extremely, keypad, door, sensor, digital, display, speaker, control, cooking, food, powerful, enough, fundamental, separate, situations, translates, direct, might, infeasible, computing, generates, ghc, glasgow, haskell, msvc, zend, engine, node, swift, objective, luajit, specific, initializer, crt0, pypy, cpython, erlang, beam, art, runtimes, meta, recompilation, transcompilation, precompilation, jit, aot, ahead, strategies, microcode, bytecode, types, intermediate, representation, optimizing, translation, concepts, encyclopedia, item, printable, download, pdf, print, export, parser, get, shortened, url, cite, permanent, related, here, actions, english, talk, українська, türkçe, русский, português, polski, 한국어, 日本語, italiano, հայերեն, فارسی, español, deutsch, čeština, català, العربية, subsection, top, personal, special, pages, recent, community, portal, learn, contribute, random, events, navigation, jump, content,
Text of the page (random words):
clibc on a glibc host canadian cross edit the canadian cross is a technique for building cross compilers for other machines where the original machine is much slower or less convenient than the target given three machines a b and c one uses machine a e g running windows xp on an ia 32 processor to build a cross compiler that runs on machine b e g running macos on an x86 64 processor to create executables for machine c e g running android on an arm processor the practical advantage in this example is that machine a is slow but has a proprietary compiler while machine b is fast but has no compiler at all and machine c is impractically slow to be used for compilation when using the canadian cross with gcc and as in this example there may be four compilers involved the proprietary native compiler for machine a 1 e g compiler from microsoft visual studio is used to build the gcc native compiler for machine a 2 the gcc native compiler for machine a 2 is used to build the gcc cross compiler from machine a to machine b 3 the gcc cross compiler from machine a to machine b 3 is used to build the gcc cross compiler from machine b to machine c 4 the end result cross compiler 4 will not be able to run on build machine a instead it would run on machine b to compile an application into executable code that would then be copied to machine c and executed on machine c for instance netbsd provides a posix unix shell script named build sh which will first build its own toolchain with the host s compiler this in turn will be used to build the cross compiler which will be used to build the whole system the term canadian cross came about because at the time that these issues were under discussion canada had three national political parties 1 timeline of early cross compilers edit this section needs expansion you can help by adding missing information july 2012 1969 the first version of unix was developed by ken thompson on a pdp 7 but due to the lack of tools and cost it was cross compiled on a gecos system and transferred via paper tape this showed practical cross compilation for os development 2 1979 algol 68c generated zcode this aided porting the compiler and other algol 68 applications to alternate platforms to compile the algol 68c compiler required about 120 kb of memory with z80 its 64 kb memory is too small to actually compile the compiler so for the z80 the compiler itself had to be cross compiled from the larger cap capability computer or an ibm system 370 mainframe 1980s aztec c offered native and cross compilation for home computers like apple ii and commodore 64 gcc and cross compilation edit gcc a free software collection of compilers can be set up to cross compile it supports many platforms and languages gcc requires that a compiled copy of binutils is available for each targeted platform especially important is the gnu assembler therefore binutils first has to be compiled correctly with the switch target some target sent to the configure script gcc also has to be configured with the same target option gcc can then be run normally provided that the tools which binutils creates are available in the path which can be done using the following on unix like operating systems with bash path path to binutils bin path make cross compiling gcc requires that a portion of the target platform s c standard library be available on the host platform the programmer may choose to compile the full c library but this choice could be unreliable the alternative is to use newlib which is a small c library containing only the most essential components required to compile c source code the gnu autotools packages i e autoconf automake and libtool use the notion of a build platform a host platform and a target platform the build platform is where the compiler is actually compiled in most cases build should be left undefined it will default from host the host platform is always where the output artifacts from the compiler will be executed whether the output is another compiler or not the target platform is used when cross compiling cross compilers it represents what type of object code the package will produce otherwise the target platform setting is irrelevant 3 for example consider cross compiling a video game that will run on a dreamcast the machine where the game is compiled is the build platform while the dreamcast is the host platform the names host and target are relative to the compiler being used and shifted like son and grandson 4 another method popularly used by embedded linux developers involves the combination of gcc compilers with specialized sandboxes like scratchbox and scratchbox 2 or proot these tools create a chrooted sandbox where the programmer can build up necessary tools libc and libraries without having to set extra paths facilities are also provided to deceive the runtime so that it believes it is actually running on the intended target cpu such as an arm architecture this allows configuration scripts and the like to run without error scratchbox runs more slowly by comparison to non chrooted methods and most tools that are on the host must be moved into scratchbox to function manx aztec c cross compilers edit manx software systems of shrewsbury new jersey produced c compilers beginning in the 1980s targeted at professional developers for a variety of platforms up to and including ibm pc compatibles and macs manx s aztec c programming language was available for a variety of platforms including ms dos apple ii dos 3 3 and prodos commodore 64 mac 68k 5 and amiga from the 1980s and continuing throughout the 1990s until manx software systems disappeared the ms dos version of aztec c 6 was offered both as a native mode compiler or as a cross compiler for other platforms with different processors including the commodore 64 7 and apple ii 8 internet distributions still exist for aztec c including their ms dos based cross compilers they are still in use today manx s aztec c86 their native mode 8086 ms dos compiler was also a cross compiler although it did not compile code for a different processor like their aztec c65 6502 cross compilers for the commodore 64 and apple ii it created binary executables for then legacy operating systems for the 16 bit 8086 family of processors when the ibm pc was first introduced it was available with a choice of operating systems cp m 86 and pc dos being two of them aztec c86 was provided with link libraries for generating code for both ibm pc operating systems throughout the 1980s later versions of aztec c86 3 xx 4 xx and 5 xx added support for ms dos transitory versions 1 and 2 9 and which were less robust than the baseline ms dos version 3 and later which aztec c86 targeted until its demise finally aztec c86 provided c language developers with the ability to produce rom able hex code which could then be transferred using a rom burner directly to an 8086 based processor paravirtualization may be more common today but the practice of creating low level rom code was more common per capita during those years when device driver development was often done by application programmers for individual applications and new devices amounted to a cottage industry it was not uncommon for application programmers to interface directly with hardware without support from the manufacturer this practice was similar to embedded systems development today thomas fenwick and james goodnow ii were the two principal developers of aztec c fenwick later became notable as the author of the microsoft windows ce kernel or nk new kernel as it was then called 10 microsoft c cross compilers edit early history 1980s edit microsoft c msc has a shorter history than others 11 dating back to the 1980s the first microsoft c compilers were made by the same company who made lattice c and were rebranded by microsoft as their own until msc 4 was released which was the first version that microsoft produced themselves 12 in 1987 many developers started switching to microsoft c and many more would follow throughout the development of microsoft windows to its present state products like clipper and later clarion emerged that offered easy database application development by using cross language techniques allowing part of their programs to be compiled with microsoft c borland c california company was available for purchase years before microsoft released its first c product 1987 edit c programs had long been linked with modules written in assembly language most c compilers even current compilers offer an assembly language pass that can be tweaked for efficiency then linked to the rest of the program after assembling compilers like aztec c converted everything to assembly language as a distinct pass and then assembled the code in a distinct pass and were noted for their very efficient and small code but by 1987 the optimizer built into microsoft c was very good and only mission critical parts of a program were usually considered for rewriting in fact c language programming had taken over as the lowest level language with programming becoming a multi disciplinary growth industry and projects becoming larger with programmers writing user interfaces and database interfaces in higher level languages and a need had emerged for cross language development that continues to this day by 1987 with the release of msc 5 1 microsoft offered a cross language development environment for ms dos 16 bit binary object code written in assembly language masm and microsoft s other languages including quickbasic pascal and fortran could be linked together into one program in a process they called mixed language programming and now interlanguage calling 13 if basic was used in this mix the main program needed to be in basic to support the internal runtime system that compiled basic required for garbage collection and its other managed operations that simulated a basic interpreter like qbasic in ms dos the calling convention for c code in particular was to pass parameters in reverse order on the stack and return values on the stack rather than in a processor register there were other programming rules to make all the languages work together but this particular rule persisted through the cross language development that continued throughout windows 16 and 32 bit versions and in the development of programs for os 2 and which persists to this day it is known as the pascal calling convention another type of cross compilation that microsoft c was used for during this time was in retail applications that require handheld devices like the symbol technologies pdt3100 used to take inventory which provided a link library targeted at an 8088 based barcode reader the application was built on the host computer then transferred to the handheld device via a serial cable where it was run similar to what is done today for that same market using windows mobile by companies like motorola who bought symbol early 1990s edit throughout the 1990s and beginning with msc 6 their first ansi c compliant compiler microsoft re focused their c compilers on the emerging windows market and also on os 2 and in the development of gui programs mixed language compatibility remained through msc 6 on the ms dos side but the api for microsoft windows 3 0 and 3 1 was written in msc 6 msc 6 was also extended to provide support for 32 bit assemblies and support for the emerging windows for workgroups and windows nt which would form the foundation for windows xp a programming practice called a thunk was introduced to allow passing between 16 and 32 bit programs that took advantage of runtime binding dynamic linking rather than the static binding that was favoured in monolithic 16 bit ms dos applications static binding is still favoured by some native code developers but does not generally provide the degree of code reuse required by newer best practices like the capability maturity model cmm ms dos support was still provided with the release of microsoft s first c compiler msc 7 which was backwardly compatible with the c programming language and ms dos and supported both 16 and 32 bit code generation msc took over where aztec c86 left off the market share for c compilers had turned to cross compilers which took advantage of the latest and greatest windows features offered c and c in a single bundle and still supported ms dos systems that were already a decade old and the smaller companies that produced compilers like aztec c could no longer compete and either turned to niche markets like embedded systems or disappeared ms dos and 16 bit code generation support continued until msc 8 00c which was bundled with microsoft c and microsoft application studio 1 5 the forerunner of microsoft visual studio which is the cross development environment that microsoft provide today late 1990s edit msc 12 was released with microsoft visual studio 6 and no longer provided support for ms dos 16 bit binaries instead providing support for 32 bit console applications but provided support for windows 95 and windows 98 code generation as well as for windows nt link libraries were available for other processors that ran microsoft windows a practice that microsoft continues to this day msc 13 was released with visual studio 2003 and msc 14 was released with visual studio 2005 both of which still produce code for older systems like windows 95 but which will produce code for several target platforms including the mobile market and the arm architecture net and beyond edit in 2001 microsoft developed the common language runtime clr which formed the core for their net framework compiler in the visual studio ide this layer on the operating system which is in the api allows the mixing of development languages compiled across platforms that run the windows operating system the net framework runtime and clr provide a mapping layer to the core routines for the processor and the devices on the target computer the command line c compiler in visual studio will compile native code for a variety of processors and can be used to build the core routines themselves microsoft net applications for target platforms like windows mobile on the arm architecture cross compile on windows machines with a variety of processors and microsoft also offer emulators and remote deployment environments that require very little configuration unlike the cross compilers in days gone by or on other platforms runtime libraries such as mono provide compatibility for cross compiled net programs to other operating systems such as linux libraries like qt and its predecessors including xvt provide source code level cross development capability with other platforms while still using microsoft c to build the windows versions other compilers like mingw have also become popular in this area since they are more directly compatible with the unixes that comprise the non windows side of software development allowing those developers to target all platforms using a familiar build environ...
|
