chunk_id
stringlengths 5
8
| chunk
stringlengths 1
1k
|
|---|---|
263_4 | Palaeocene to Middle Eocene, marking the start of Cenozoic Era. |
263_5 | Table showing the major formations discussed in the following sections:
Tal Formation
The Tal Formation belongs to the Mussoorie Group of Outer Lesser Himalaya of Garhwal in northwestern India. It is well exposed along the Krol Belt, and is overlying the Precambrian Krol Group.
The Tal in the Mussoorie Synform can be divided into the Lower Tal and Upper Tal. For the Lower Tal, there are four subdivisions: the Chert, Argillaceous, Arenaceous and Calcareous Units. The basal black shale succession with sandy limestone represents a depositional environment of a protected lagoon or embayment, while the overlying siltstone is deposited in a mud flat of an intertidal zone. |
263_6 | The Upper Tal can be subdivided into lower quartzitic sequence and upper thick calcareous sequence containing abundant fragmentary shells of bivalves, gastropods, bryozoa, etc. The Phulchatti quartzite succession represents the deposits of a shoal environment, while the uppermost shell limestone sequence indicates an increasing energy of the shallow tidal sea, and a marine transgression in the Cretaceous.
There is an increase of energy for deposition from the Lower Tal to the Upper Tal. Because of the lack of well-defined body fossils in the Tal, it has been proposed that the deposits of the Tal were formed in the Late Precambrian near Precambrian-Cambrian transition, except for the uppermost Manikot Shell Limestone, which has been proposed to have been formed in the Late Cretaceous and unconformably overlain by the Subathu Formation in the Tal Valley, Garhwal Himayala.
The details of lithologies and depositional environment of Tal Formation are shown in the table below: |
263_7 | Gondwana strata
Gondwana strata are not exposed in the Garhwal Himalaya after the Tal Formation owing to the great hiatus; some outcrops can be found in Central and Eastern Himalaya during Late Paleozoic to Mesozoic times.
Central Himalaya – Central and Western Nepal |
263_8 | In Nepal, the older LHS with age ranging from the Paleoproterozoic to uppermost Precambrian are separated from the younger LHS by the Great Lesser Himalayan Unconformity. Missing Early Proterozoic strata of the LHS suggest that the rocks may have been eroded before the deposition of the Gondwana strata. Younger continental facies Gondwana strata were first deposited after the unconformity. They are then unconformably overlain by a marine facies Tertiary Unit. The Gondwana strata are mainly developed within two zones in Nepal in the central Himalaya. The first is in central Nepal, where several outcrops of the Tansen Group can be found. The second is in western Nepal, where the Gondwana strata are exposed in the Jumla–Humla basins near the Tethyan Himalaya. |
263_9 | The Tansen area contains Gondwana sediments that are identified by the presence of fossils. Two major formation can be found there. They are older Sisne Formation (or the Lower Gondwanas) and younger Taltung and Amile formations (or the Upper Gondwanas). The Sisne Formation is dominated by glacial diamictite and fluvial deposits. In the upper part of the formation, shales are found to contain fenstellid bryozoan fossils, indicating that the Lower Gondwanas in central Nepal dates from the Late Carboniferous to the Permian. |
263_10 | The Upper Gondwanas are further subdivided into the Taltung and Amile formations. The Taltung Formation is characterised by coarse-grained, volcaniclastic conglomerates, sandstones and silty shales. They were deposited by northwestward-flowing fluvial channels. Abundant plant fossils are found in the Taltung Formation, and they are dated to the Late Jurassic to the Early Cretaceous. The Amile Formation is unconformably overlying the Taltung Formation. It is dominated by white quartz arenites, quartz pebble sandstones, carbonaceous shales and limestones with coral, mollusc and vertebrate fossils. In the upper part of the formation, an abrupt change of lithology from thick, coarse-grained quartzose sandstones to interbedded layers of black marine shales and fine-grained quartzose sandstones are observed. This is probably the contact between the Upper Amile Formation and the overlying Bhainskati Formation of the Tertiary Unit. The Amile Formation is dated to the Early Cretaceous to Early |
263_11 | Paleocene, while the Bhainskati Formation is biostratigraphically dated as from the Middle to Late Eocene. |
263_12 | In the Jumla area of western Nepal, Gondwana strata unconformably overly the caronbate rocks of the Uppermost Nawakot Unit of Mesoproterozoic age. The Gondwanas here are characterized by quartzose sandstones, black shales, quartz pebble conglomerates as well as coal and lignite. They are dated as Jurassic to Paleocene. The lithology of Gondwanas here is quite similar to that of the Amile Formation in central Nepal. Also, the Gondwana Unit is overlain by the Bhainskati Formation of the Tertiary Unit, similar to the situation in central Nepal. |
263_13 | However, in fact, the Gondwana Unit is not very well developed in the Jumla area. The strata with lithology similar to that of the Taltung Formation and Lower Gondwanas are missing here. In other words, the LHS in the Jumla area is lacking a part of the Gondwana Unit of age ranging from Late Carboniferous-Permian to Early Cretaceous. This is probably due to a greater effect by the Great Lesser Himalayan Unconformity in the Jumla area than in the Tansen area.
Eastern Himalaya – Bhutan
Compared with Nepal, the Gondwana strata are exposed in a relatively smaller area in Bhutan. In southeastern Bhutan, the basal LHS begins with the metamorphic Daling-Shumar Group, followed by the Baxa Group that is characterized by quartzite, phyllite and dolomite succession of Neoproterozoic to probably Cambrian age. The bottom of the Gondwana Units (Diuri Formation) is then directly overlying the Baxa Group. |
263_14 | Generally, there are three main formations of Gondwana Units exposed in southeastern Bhutan. The bottom one is the Diuri Formation with Proterozoic to Permian ages. It consists of conglomerate, quartzite, phyllite as well as diamictite with interbedded slates. At the base of this formation, pebbles are composed of quartzite and siliceous dolomite. They are embedded in a fine quartzite matrix. The thicker beds of slate and phyllite are overlying the conglomerate layers. Clear schistosity can be observed. The diamictite found implies a source of glacial origin. It is probably correlated to the glaciation event of the Gondwana supercontinent during the Late Paleozoic. |
263_15 | The Diuri Formation is then overlain by the Setikhola Formation, which is characterized by feldspathic sandstone, shale, graywacke, coal lenses and plant fossils. One sequence consists of interbedding of sandstone and shale and is intensely bioturbated with flames structures observed as well. This indicates a depositional environment of beach or mudflat. Also, another sequence of interbedding calcareous greywacke and carbonaceous shale is found. Ripples and cross-laminae can be observed on the greywacke, while small-scaled sun cracks and slump folds can be seen on shale. It is proposed that this sequence has a depositional environment of semi-isolated basin. The marine fossils contained here indicate a Permian age of the Setikhola Formation. |
263_16 | The uppermost Gondwana unit is the Damudas Sub-Group, which is characterized by arenite, shale, slate and black coal beds. In fact, the Setikhola Formation and Damudas Sub-Group are together termed as the Gondwana succession. The bedrock of the Damudas Sub-Group is made up of gritty, micaceous and cross-laminated sandstones. These friable sandstone layers are interbedded with coal beds that have been sheared and crushed. Abundant plant fossils like fern leaves can be found on the carbonaceous shale, characterising the Damuda coalfields and indicating a Permian age. Generally, the strata here are lenticular and display a fining-upwards sequence. In tectonic context, it is proposed that the Gondwana strata here have experienced post—Gondwana orogenic movements, resulting in folded rocks followed by overturned beddings. |
263_17 | Singtali and Subathu formations
Following a sedimentary break or unconformity, the Singtali and Subathu formations were deposited as foreland basin sediments in the Garhwal Outer Lesser Himalaya during the Late Cretaceous to Middle Palaeocene. Both formations can be found overlying the Tal Formation in an extremely complex structural setting including isoclinal overturned folding and multiple thrusting events. In addition, with the similarities of the lithology as well as depositional environment, it is sometimes quite difficult to distinguish between the Singtali and Subathu Formations. The main difference discussed in the following is related to the tectonic events during their deposition. |
263_18 | Singtali Formation
The Singtali Formation belongs to the Sirmur Group of the Outer Lesser Himalaya of Garhwal. It is also called "Upper Tal" as the uppermost Manikot Shell Limestone, however, this formation is distinct from the basement Tal Formation upon which it rests unconformably. Its main lithology is dominated by sandy, oolitic and shelly limestones with subordinate quartz arenites. Medium-bedded massive strata are predominant and no sedimentary structures are visible. The Singtali Formation has been assigned as a Late Cretaceous-Palaeocene age based on faunal evidence. In terms of depositional environment, the dominance of limestone in the Singtali Formation and sparse fauna would imply shallow marine conditions at that time. A high-energy, agitated environment can be inferred from the presence of ooids. |
263_19 | Subathu Formation or Group |
263_20 | The Subathu Formation also belongs to the Sirmur Group of the Outer Lesser Himalaya of Garhwal. In 2020 literature it is referred to as Subathu Group. It is a sequence of limestones, green mudrocks and subordinate sandstones, and has been paleontologically dated as from Late Palaeocene to Middle Eocene. The rocks are rich in fossils. The limestones with normal marine fauna and thick mudstones with well preserved, burrowing-type molluscs indicate a quiet, relatively shallow shelf environment during the period of deposition. This depositional environment is similar to that of the Singtali Formation. The Subathu contains the oldest Himalayan foreland basin rocks. Near the Krol and Garhwal thrusts in northeastern India, the Subathu Formation exists as a narrow and discontinuous strip, indicating that it has experienced extremely high tectonic shearing and shattering as a result of overthrusting of rocks. Consequently, the Subathu Formation is only partially preserved in the Krol nappe and |
263_21 | under the Garhwal thrust, and unconformably overlies the Tal Formation. |
263_22 | Distinctions between the Singtali and Subathu Formations
In the Singtali Formation times (Late Cretaceous-Palaeocene), the Indian craton submerged and stable shallow marine conditions ensued. This event is possibly related to flexure, such that the Spontang ophiolite was obducted onto the Northern Indian Plate margin. One more possible explanation is related to extensional tectonics, such that India has drifted and detached from Gondwana, and northwards subduction of the Neotethys (Tethys Ocean) beneath Asia occurred. Therefore, the Singtali Formation has been interpreted as pre-collisional transgressive sediments, at the same time there was a global eustatic sea level rise during the Late Cretaceous. |
263_23 | The tectonic setting of the Subathu Formation is different from that of the Singtali Formation. It was deposited during the suturing of India and Eurasia, between the initial and terminal continental collision. The inferred pattern of northward shallowing and reduced sedimentation conflicts with classic foreland basin models. However, these depositional patterns may reflect basement fault reactivation, giving rise to paleohighs, rather than simply crustal loading following on from the collision.
Their individual tectonic significance related to foreland basin evolution are discussed in greater detail in the next section. The general similarities and differences between the Singtali and Subathu formations are shown in the table below:
Geological significance during Paleozoic to Mesozoic times |
263_24 | Gondwana strata
In the Nepal Himalaya, the Lower Gondwana glacial diamictite is unconformably overlain by the fluvial Taltung Formation (Upper Gondwana), which contains abundant plant fossils distributed widely within the Tansen area. Alkali basalt lava flows are interbedded with the fluvial beds in the Lower Taltung. Gravelly braided river facies are shown in the Lower Taltung while silty meandering river facies are displayed in the Upper Taltung, as a result, the sequence is fining upwards. The strata were deposited in a terrestrial basin on Gondwana. |
263_25 | Because of the appearance of glacial diamictite and index plant fossils found in the Lower and Upper Gondwanas respectively, it has been proposed that the Lesser Himalaya had been a part of Gondwanaland during the Permian to Cretaceous. Later on, the presence of basaltic lava flows indicate a tectonic setting related to basaltic volcanism as the volcanic clasts were derived from the underlying lava and transported by rivers from Gondwana land. The interbedding layers of fluvial sediments and basaltic lava bands imply that there was repeated occurrence of basaltic eruption and erosion and sedimentation of fluvial deposits alternatively. These events were probably caused by breaking up and rifting of Gondwanaland during the Late Jurassic to Early Cretaceous. |
263_26 | The whole sequence of Upper Gondwanas (including both the Taltung and Amile Formations) represents non-marine deposition. Data from the paleocurrent direction show that the sediments were derived from the south, because the Indian subcontinent was drifting northwards towards the Lesser Himalaya. After that, the Bhainskati Formation was deposited in shallow marine environment. The upper Bhainskati has been found to have been deposited in a brackish or fresh water environment, indicating a gradual and minor regression period. The regression phase was probably initiated by the sea level change in the northern Neotethys. However, overall there were no significant changes in tectonic setting during the Early Cretaceous to Early Paleocene. In fact, the Bhainskati Formation is correlated to the Subathu Formation in the Garhwal Himalaya. The deposition of these marine facies in a shallow marine environment is associated with the foreland basin development. |
263_27 | Tectonic events related to Singtali Formation |
263_28 | The Early Tertiary geology of the Indian Lesser Himalaya conforms well with the classic foreland basin model. In Late Cretaceous times, this area of the northern region of the Indian Plate finally became submerged after a long period when sub-aerial conditions had dominated. This resulted in deposition of the marine Singtali Formation. A possible explanation for this event is that ophiolites such as the Spontang ophiolite were obducted onto the Indian Plate Zanskar continental shelf in the Campanian or Maastrichtian, resulting in downward displacement and flexure of the Indian Plate hundreds of kilometres to the south. Moreover, it has been proposed that the marine transgression is related to extensional tectonic setting, such that the Late Albian has detached from India and has started to drift from the Gondwana supercontinent, Also, the Neotethys has subducted northwards beneath Asia. This event is accompanied with the Late Cretaceous global eustatic sea-level high stand as well. |
263_29 | Tectonic events related to Subathu Formation
The initial contact between India and Eurasia have taken place at 62 – 60 Ma in the northwestern Himalayas, with terminal collision culminating by 55 Ma in the east. The Subathu Formation rocks were deposited during the suturing and initial collision of India and Eurasia.
However, the western intermediate structural level localities show a much thinner Subathu marine sequence compared to the eastern intermediate structural level localities and the lowest structural level. The thickness variations between the west and the east could be explained by the progressive suturing of India and Eurasia from northwest to east, with later suturing in the east allowing a longer period where marine conditions could predominate. |
263_30 | This progressive suturing, however, would not explain the thickness difference between the lowest and intermediate structural levels. As the intermediate structural level restores further to the north than the lower structural level, northward shallowing of the basin (i.e. towards the load) is implied. This is different from the theoretical model, where the depocentre is close to the load and shallows towards the craton. In the Lesser Himalayan early foreland basin, palaeohighs, which are resulted from basement fault reactivation, may have been located in the west between the load to the north and the marine Subathu basin to the south. This would result in shallowing towards, and reduced sedimentation on the palaeohigh, which coupled with the probable distal nature of the basin, therefore, explaining the thin sequences of the western intermediate structural level localities. |
263_31 | After suturing, fluvial facies are overlying the marine Subathu Formation. It is associated with the uplift of HImalaya and regression of sea in the Late Eocene.
See also
Geology of the Himalaya
Geology of Nepal
Himalayan foreland basin
References
Geology of the Himalaya
Geologic formations of Asia
Geologic formations of India
Geologic formations of Pakistan
Geology of Bhutan
Geology of Nepal |
264_0 | A cross compiler is a compiler capable of creating executable code for a platform other than the one on which the compiler is running. For example, a compiler that runs on a PC but generates code that runs on Android smartphone is a cross compiler.
A cross compiler is necessary to compile code for multiple platforms from one development host. Direct compilation on the target platform might be infeasible, for example on embedded systems with limited computing resources.
Cross compilers are distinct from source-to-source compilers. A cross compiler is for cross-platform software generation of machine code, while a source-to-source compiler translates from one programming language to another in text code. Both are programming tools. |
264_1 | Use
The fundamental use of a cross compiler is to separate the build environment from target environment. This is useful in several situations:
Embedded computers where a device has extremely limited resources. For example, a microwave oven will have an extremely small computer to read its keypad and door sensor, provide output to a digital display and speaker, and to control the machinery for cooking food. This computer is generally not powerful enough to run a compiler, a file system, or a development environment.
Compiling for multiple machines. For example, a company may wish to support several different versions of an operating system or to support several different operating systems. By using a cross compiler, a single build environment can be set up to compile for each of these targets. |
264_2 | Compiling on a server farm. Similar to compiling for multiple machines, a complicated build that involves many compile operations can be executed across any machine that is free, regardless of its underlying hardware or the operating system version that it is running.
Bootstrapping to a new platform. When developing software for a new platform, or the emulator of a future platform, one uses a cross compiler to compile necessary tools such as the operating system and a native compiler.
Compiling native code for emulators for older now-obsolete platforms like the Commodore 64 or Apple II by enthusiasts who use cross compilers that run on a current platform (such as Aztec C's MS-DOS 6502 cross compilers running under Windows XP). |
264_3 | Use of virtual machines (such as Java's JVM) resolves some of the reasons for which cross compilers were developed. The virtual machine paradigm allows the same compiler output to be used across multiple target systems, although this is not always ideal because virtual machines are often slower and the compiled program can only be run on computers with that virtual machine.
Typically the hardware architecture differs (e.g. compiling a program destined for the MIPS architecture on an x86 computer) but cross-compilation is also applicable when only the operating system environment differs, as when compiling a FreeBSD program under Linux, or even just the system library, as when compiling programs with uClibc on a glibc host. |
264_4 | Canadian Cross
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 Mac OS X 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. |
264_5 | 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. |
264_6 | The term Canadian Cross came about because at the time that these issues were under discussion, Canada had three national political parties.
Timeline of early cross compilers
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.
GCC and cross compilation
GCC, a free software collection of compilers, can be set up to cross compile. It supports many platforms and languages. |
264_7 | GCC requires that a compiled copy of binutils be 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. |
264_8 | 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 itself will produce; otherwise the target platform setting is irrelevant. 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''. |
264_9 | Another method popularly used by embedded Linux developers involves the combination of GCC compilers with specialized sandboxes like Scratchbox, scratchbox2, 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
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 PCs and Macs. |
264_10 | 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, Macintosh 68XXX and Amiga.
From the 1980s and continuing throughout the 1990s until Manx Software Systems disappeared, the MS-DOS version of Aztec C was offered both as a native mode compiler or as a cross compiler for other platforms with different processors including the Commodore 64 and Apple II. 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. |
264_11 | 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 and which were less robust than the "baseline" MS-DOS version 3 and later which Aztec C86 targeted until its demise. |
264_12 | 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.
Microsoft C cross compilers |
264_13 | Early history – 1980s
Microsoft C (MSC) has a shorter history than others 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.
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. |
264_14 | Long before Borland, BSD Unix (Berkeley University) had gotten C from the authors of the C language: Kernighan and Ritchie who wrote it in unison while working for AT&T (labs). K&R's original needs was not only elegant 2nd level parsed syntax to replace asm 1st level parsed syntax: it was designed so that a minimal amount of asm be written to support each platform (the original design of C was ability to cross compile using C with the least support code per platform, which they needed.). Also yesterdays C directly related to ASM code wherever not platform dependent. Today's C (more-so c++) is no longer C compatible and the asm code underlying can be extremely different than written on a given platform (in Linux: it sometimes replaces and detours library calls with distributor choices). Today's C is a 3rd or 4th level language which is used the old way like a 2nd level language. |
264_15 | 1987
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. |
264_16 | 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". 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. |
264_17 | 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. |
264_18 | 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. |
264_19 | Early 1990s
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). |
264_20 | 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. |
264_21 | Late 1990s
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. |
264_22 | .NET and beyond
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. |
264_23 | 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 environment. |
264_24 | Free Pascal
Free Pascal was developed from the beginning as a cross compiler. The compiler executable (ppcXXX where XXX is a target architecture) is capable of producing executables (or just object files if no internal linker exists, or even just assembly files if no internal assembler exists) for all OS of the same architecture. For example, ppc386 is capable of producing executables for i386-linux, i386-win32, i386-go32v2 (DOS) and all other OSes (see ). For compiling to another architecture, however, a cross architecture version of the compiler must be built first. The resulting compiler executable would have additional 'ross' before the target architecture in its name. i.e. if the compiler is built to target x64, then the executable would be ppcrossx64. |
264_25 | To compile for a chosen architecture-OS, the compiler switch (for the compiler driver fpc) -P and -T can be used. This is also done when cross-compiling the compiler itself, but is set via make option CPU_TARGET and OS_TARGET. GNU assembler and linker for the target platform is required if Free Pascal does not yet have internal version of the tools for the target platform.
Clang
Clang is natively a cross compiler, at build time you can select which architectures you want Clang to be able to target.
See also
MinGW
Scratchbox
Free Pascal
Cross assembler
References |
264_26 | External links
Cross Compilation Tools – reference for configuring GNU cross compilation tools
Building Cross Toolchains with gcc is a wiki of other GCC cross-compilation references
Scratchbox is a toolkit for Linux cross-compilation to ARM and x86 targets
Grand Unified Builder (GUB) for Linux to cross-compile multiple architectures e.g.:Win32/Mac OS/FreeBSD/Linux used by GNU LilyPond
Crosstool is a helpful toolchain of scripts, which create a Linux cross-compile environment for the desired architecture, including embedded systems
crosstool-NG is a rewrite of Crosstool and helps building toolchains.
buildroot is another set of scripts for building a uClibc-based toolchain, usually for embedded systems. It is utilized by OpenWrt.
ELDK (Embedded Linux Development Kit). Utilized by Das U-Boot.
T2 SDE is another set of scripts for building whole Linux Systems based on either GNU libC, uClibc or dietlibc for a variety of architectures
Cross Linux from Scratch Project |
264_27 | IBM has a very clear structured tutorial about cross-building a GCC toolchain.
Cross-compilation avec GCC 4 sous Windows pour Linux - A tutorial to build a cross-GCC toolchain, but from Windows to Linux, a subject rarely developed |
264_28 | Compiler theory |
265_0 | U.S. Route 74 (US 74) is an east–west United States highway that runs for from Chattanooga, Tennessee to Wrightsville Beach, North Carolina. Primarily in North Carolina, it serves as an important highway from the mountains to the sea, connecting the cities of Asheville, Charlotte and Wilmington.
Route description
|-
|TN
|63.0
|101.4
|-
|NC
|451.8
|727.1
|-
|Total
|514.8
|828.5
|}
Tennessee
US 74 was designated in 1927. The route travels from the I-24/I-75 interchange, in Chattanooga, northeast to Cleveland, where it then continues east, along with US 64, to the North Carolina state line. The highway is predominantly freeway or expressway grade four-lane, except between Ocoee and Ducktown, where it is a curvy two-lane mountain highway along the Ocoee River known as the Ocoee Scenic Byway. |
265_1 | TDOT's signage for US 74 is poor. Most highways that cross it will typically only list I-75 or US 64 instead; I-75 completely ignores US 74 along its route, even ignoring it at their intersection, showing instead the US 64 Bypass.
North Carolina
From the Tennessee state line, US 74 traverses across the southern portion of the state, connecting the major cities Asheville, Charlotte, and Wilmington, for a total of . |
265_2 | In western North Carolina, US 74 enters the state with a concurrency with US 64. Routed along on pre-existing highways in the region, specifically the: Appalachian Highway (at-grade expressway, except in the Nantahala Gorge) and the Great Smoky Mountains Expressway (controlled-access freeway, which is broken in three sections along the route); it shares a revolving door of concurrency changes with US 19, US 129, US 441 and US 23. The alternating named highway (depending on grade of road) is considered the commercial back-bone and main truck route of Western North Carolina, connecting the cities of Murphy, Andrews, Bryson City, Cherokee, Sylva, and Waynesville. In or around October, the fall colors create an influx of more tourists in the region. In the winter months, the highway is the first to be salted and plowed; however, both the Nantahala Gorge and Balsam Gap tend to get the most snow and/or ice in the region and should be traveled with care. |
265_3 | North of Clyde, US 74 merges with Interstate 40 and goes east, in concurrency, to Asheville. From there, it then goes southeast, in concurrency with Interstate 26 till Columbus, where it separates and continues east along a mostly controlled-access highway, except in Shelby, to Interstate 85, in Kings Mountain. |
265_4 | After crossing a unique weave intersection with Interstate 85, it joins with US 29 and travels through downtown Gastonia along Franklin Boulevard. East of Gastonia, it becomes Wilkinson Boulevard as it go through McAdenville, Cramerton and Belmont. After crossing the Lake Wylie/Catawba River, via Sloans Ferry Bridge, it enters Charlotte, with connections with Interstate 485 and Interstate 85/Charlotte Douglas International Airport, via Little Rock Road. At Morehead Street, west of Center City, it splits with US 29 for Interstate 277 along the John Belk Freeway. East of Center City, it goes solo again along Independence Freeway/Boulevard to Matthews, where it connects again with Interstate 485. |
265_5 | Going southeast, it goes through Stallings, Indian Trail and Monroe, where it briefly overlaps with US 601, before continuing east again through Wingate, Marshville, Peachland, Polkton, Wadesboro and Lilesville. On this stretch, prior to 2018, signage for the route was very poor, only being found at a few locations along the route. As part of the US 74 Monroe Bypass project, signage along the route was improved by the NCDOT. |
265_6 | Crossing the Pee Dee River and into the Sandhills region, US 74 meets up with Future Interstates I-73/I-74, in Rockingham. After a future interchange near NC 38 that will end its overlap with Interstate 73, US 74/Future I-74 continues southeast, bypassing Laurinburg and Maxton. East of Maxton and through Lumberton, the highway is officially US 74/Interstate 74, before dropping back to Future I-74 west of Boardman; the concurrency with Future I-74 ends at Bolton, where a future interchange will split from US 74 to continue south towards South Carolina. This is one of only two instances (along with I-41 in Wisconsin) of similarly-numbered U.S. and Interstate routes being designated on the same road. |
265_7 | Near Chadbourn, US 74 overlaps with US 76, which continue mostly together till Wrightsville Beach, where US 74 dead-ends north and US 76 dead-ends south. The highway connects the cities and towns of Whiteville, Lake Waccamaw, and Wilmington. The road through the Cape Fear region is flat, surrounded by parts of the Green Swamp.
ADHS corridors
US 74 overlaps with two corridors that are part of the Appalachian Development Highway System (ADHS), which is part of Appalachian Regional Commission (ARC). Passed in 1965, the purpose of ADHS is to generate economic development in previously isolated areas, supplement the interstate system, connect Appalachia to the interstate system, and provide access to areas within the Region as well as to markets in the rest of the nation. |
265_8 | Corridor A – From I-285, in Sandy Springs, Georgia to I-40, near Clyde, North Carolina. US 74 overlap from US 23, in Dillsboro, to I-40, near Clyde; it is also completed with divided four-lane limited-access and controlled-access sections. This corridor is signed as "Appalachian Highway," in white text on blue background.
Corridor K – From I-75, in Cleveland, Tennessee, to US 23, in Dillsboro, North Carolina. The entire section of US 74 is authorized for ADHS funding. The majority of the route is a four-lane limited-access road, with a section that is controlled-access between Bryson City and Cherokee. Current two-lane sections that are impending improvements are: Ocoee River to Ducktown and the Nantahala Gorge. In North Carolina, this corridor is signed as "Appalachian Highway," in white text on blue background. |
265_9 | Scenic byways
The Ocoee Scenic Byway is a National Forest Scenic Byway that traverses through the Cherokee National Forest, in East Tennessee. 19 miles of the Byway are concurrent with US 74 (in addition to U.S. Route 64). Features include the Ocoee Whitewater Center and scenic bluffs along Ocoee River and Gorge.
Nantahala Byway is a byway from Marble to Whittier; it is known for its scenic views of the Nantahala Gorge, The Great Smoky Mountains Railroad, and whitewater rafting on the Nantahala River. US 74 overlaps of the byway from Marble to Bryson City. The byway also overlaps with US 19 and US 129.
Dedicated and memorial names
US 74 features several dedicated bridges and stretches of highway throughout its route. |
265_10 | American Indian Highway – this name was authored by Tuscarora Indian Robert M. Chavis, he launched a campaign to obtain support from all the city councils and the Robeson county Commissioners, they all signed onto the partition Mr. Chavis sent to the NCDOT and it was approved by the state DOT, official North Carolina name of the section of US 74/I-74 in Robeson County (mile marker 191-213). It is named to honor the large American Indian population in Robeson County (approved: November 8, 2001).
Andrew Jackson Highway – Official North Carolina name of US 74 throughout the state, except in Robeson County (it is still named along the old sections of US 74 now called US 74 Business and Alternate). It was established to honor of the seventh President of the United States, Andrew Jackson (approved: April 4, 1963). Signage is found primarily east of Charlotte, overlapping other official North Carolina dedicated sections. |
265_11 | C. Heide Trask Bridge – Official North Carolina name of bridge over the Inland Waterway, in Wrightsville Beach (approved: June 9, 1958).
Cameron Morrison Bridge – Was an official North Carolina name of the first bridge and later westbound US 74 bridge, over the Pee Dee River. It was named in honor of Governor Morrison, who was a Richmond County native. The bridge, built in 1925, was dedicated to Morrison originally at an unknown date; in 1983, after the bridge was reconstructed to modern standards, it was rededicated to R.W. Goodman.
Dean Arledge Memorial Highway – Official North Carolina name of US 74 between I-26 and NC 9, in Polk County (approved: March 3, 2000).
G R Kindley Freeway – Official North Carolina name of US 74/I-74 along the Rockingham-Hamlet bypass. It is named in honor of the former mayor of Rockingham (approved: September 8, 2000). |
265_12 | Herman H. West Bridge – Official North Carolina name of bridge over the Valley River, in Cherokee County. It was dedicated in honor of the former state Senator and Representative (approved: September 8, 2000).
Hezekiah Pridgen, Sr. Bridge – Official North Carolina name of bridge over US 701, in Columbus County (approved: August 4, 1995).
James Archibald Hardison Bridge – Official North Carolina name of the eastbound US 74 bridge, over the Pee Dee River. It is named in honor of the former Highway Commissioner and member of the Highway Commission under three governors, from 1933-1937 and 1953-1961 (approved: December 30, 1958).
J. Ollie Harris Highway – Official North Carolina name of US 74 Bypass at Kings Mountain (approved: October 3, 1997).
James Arthur Callahan Freeway – Official North Carolina name of a section of US 74/I-26 in Rutherford County (approved: May 10, 1992). |
265_13 | John Belk Freeway – Official North Carolina name of US 74/I-277, from I-77/US 21 to Independence Boulevard, in Uptown Charlotte. It is named in honor of John M. Belk, who was mayor of Charlotte from 1969-1977 (approved: September 11, 1981).
R.W. Goodman Bridge – Official North Carolina name of the westbound US 74 bridge, over the Pee Dee River. It is named in honor of the former Richmond County sheriff R. W. Goodman (approved: March 11, 1983).
Senator Jesse Helms Freeway – Official North Carolina name of US 74 between US 601 to the Anson-Union County line (approved: January 8, 1993). Named in honor of the late five-term U.S. senator who was born in Union County in 1921.
Solon David Smart Memorial Highway – Official North Carolina name of highway from NC 120 to US 221A, in Rutherford County (approved: December 1, 2000).
W Cliff Martin Highway – Official North Carolina name of US 74 from Union County line to Wadesboro, in Anson County (approved: May 2, 1997). |
265_14 | History
Established as an original U.S. Route in late 1926, US 74 traversed from Asheville to Chadbourn, in North Carolina. It was extended eastward in late 1934 to Wilmington, replacing an old alignment of US 17.
In 1936, US 74 was extended eastward again from Wilmington, via Market Street, to Wrightsville Beach, then going north on Lumina Avenue to its current eastern terminus. US 74 also spawned two alternate routes the same year, the first and shortest () in Leland, and a second in Shelby; which eventually replaced all of US 74 through the downtown area by 1949 (later renamed US 74 Business in 1960).
In 1937, US 74 was rerouted through Kings Mountain, replacing part of NC 7. Its old alignment became an alternate route, but was replaced a year later by both NC 161 and NC 274. |
265_15 | By 1949, US 74 was on its first bypass around Rutherfordton, via Ruth; its former route becoming an alternate route (later renamed US 74 Business in 1960). In 1952, the first Monroe Bypass was completed, leaving a short-lived alternate route going through the downtown area. By 1953, the first bypass around Rockingham was completed, leaving a short lived alternate route through the downtown area.
In 1970, US 74 was placed on new freeway alignment bypassing Spindale, Forest City, Ellenboro, and Mooresboro; the old route was replaced by an extension of US 74 Business. In 1973, US 74 was realigned onto new road south of Lumberton. In 1975, US 74/US 76 was rerouted onto new freeway bypass south of Leland and then east of Belville, its old alignment becoming secondary roads. In 1976, US 74/US 76 was bypassed north of Chadbourn and Whiteville, leaving behind US 74 Bus./US 76 Bus. |
265_16 | In 1984, Maxton was bypassed, replaced by an extension of US 74 Bus. In 1985, US 74 was rerouted north of Kings Mountain onto new freeway bypass; its old alignment becoming US 74 Bus. In 1986, Hallsboro and Lake Waccamaw were bypassed; its old alignment replaced by NC 214. |
265_17 | Also in 1986, US 74 was extended west, from Asheville to Chattanooga, Tennessee. The routing extension started at its former western terminus with US 70, going northerly, in concurrency with US 70, to I-240, where it overlapped briefly before joining US 19/US 23. From Asheville, in concurrency with US 19/US 23, it went through Canton and Lake Junaluska. From Lake Junaluska, in concurrency with US 23, it went through Waynesville. Near Dillsboro it switches US 23 for US 441 and continues till it splits north within the Qualla Boundary. West of Bryson City, it overlaps with NC 28. In Topton, it joins with US 129 and continues southwesterly till at Murphy, where it joins with US 64 and separates from US 19/US 129. Heading west, in concurrency with US 64, it enters Tennessee; traversing through Ducktown, it reaches Cleveland, where it then follows the US 64 Bypass to I-75. Continuing southeasterly, as a hidden concurrency with I-75, it connects with Chattanooga, ending at its new |
265_18 | terminus at I-24. |
265_19 | In 1988, US 74 was extended east to its current eastern terminus in Wrightsville Beach. In 1990, US 74 was rerouted onto I-277 (John Belk Freeway), this left a section of Independence Boulevard that was still overlapped with NC 27. In 1992-1993, Bolton was bypassed to the north, with its old alignment becoming an extension of NC 214.
In 1994, US 74 was rerouted onto I-40 for , in Asheville, and then onto I-26, from Asheville to Columbus. East of Columbus, it traverses along new freeway to Forest City, where it meets back with its old alignment. The former routing between Asheville and Forest City becomes US 74A. In 1996, US 74 was rerouted through Wilmington. In late 1997, US 74 was rerouted onto I-40, between Clyde and Asheville. |
265_20 | In 2002, US 74 was placed on its second bypass around both Rockingham and Hamlet, its old alignment becoming US 74 Business. In 2005, US 74 was rerouted north of downtown Wilmington. In 2007, US 74 was placed on new freeway, in concurrency with I-74 from Maxton to just east of I-95; its old alignment becoming US 74 Alternate.
In 2018, US 74's new toll bypass around Monroe was completed.
Independence Boulevard
Independence Boulevard and Independence Expressway are two major interconnected roads in Mecklenburg County, North Carolina that carry US 74. Originally constructed in the 1940s and early 1950s, Independence Boulevard was the city of Charlotte's first expressway. The road has undergone numerous realignments, extensions, upgrades, truncations, and renamings since the mid-20th century. |
265_21 | Ben Douglas, former mayor of Charlotte and member of the North Carolina State Highway Commission, helped lead the push for the urban highway project in the 1940s that would become Independence Boulevard. In 1946, Charlotte voters passed a referendum in favor of a $200,000 bond issue to fund the project; this was coupled with over $2 million in federal funding. The expressway was to be named after Independence Park that was largely demolished to make way for the road; the name suggestion was coined by City Clerk Lillian Hoffman on May 4, 1949 after a previous suggestion naming it after the current mayor, Herbert Baxter, was rejected. Construction commenced in the late 1940s and the new expressway which traversed east–west along the southern part of the city opened in two parts; the first opened to traffic in 1949 and the other opened in 1950. US 74 and NC 27 were subsequently shifted from their central business district alignments to the new expressway. |
265_22 | Major changes to Independence Boulevard occurred in the 1980s. A portion of West Independence Boulevard was converted from expressway to limited-access freeway and made a part of the John Belk Freeway and Interstate 277. The portion west of Interstate 77 was renamed Wilkinson Boulevard. A new intersection with I-277 was constructed and the connecting freeway along with the updated portion of East Independence Boulevard was given the name Independence Freeway; US 74 was shifted to this new alignment. After the massive transportation revamp, a few disconnected segments of the original Independence Boulevard remained. These segments were later reorganized and given the names Carson Boulevard, Stonewall Street, and South Independence Boulevard; the latter was downgraded to a surface street and renamed Charlottetown Avenue in 2007 to prevent confusion with the unconnected East Independence Boulevard. |
265_23 | The freeway and bus lanes of Independence Freeway were extended to Albemarle Road in 2005. The limited-access road extension has caused numerous businesses along the corridor to leave the area and vacate their commercial real estate, resulting in brownfield land. |
265_24 | "American Indian Highway" controversy |
265_25 | In Robeson County, the highway is designated "American Indian Highway," a name that was the brain child of Robert M. Chavis, the Wolfclan chief of the NC Tuscarora; Cherokee Indians of Robeson County, and Nottoway Nation, who authored the name in the late 1990s. American Indian people of Robeson County, NC had attempted to remove Andrew Jackson's name from the highway for some sixty years. Knowing that the new US 74 was to come, Chavis started a campaign to change the name to American Indian Highway. Chavis did this in honor of all the Indian people that had lost their lives along the Trail of Tears during the Indian Removal Act of the 1830s authored by Andrew Jackson. Chavis was cited in many newspapers across North Carolina stating that the name should be changed, because that name on this section of road was tantamount to having a major road named Adolf Hitler that ran across a Jewish state or county. Chavis, with the help of the Tuscarora East of the Mountains, obtained the |
265_26 | information on how to attempt the name change from Rep. Ronnie Sutton and the NCDOT. Then Chavis presented the reasons for the name change to all the cities of Robeson county and the Robeson County Commissioners. Once he obtained support from these entities he presented the proposal to the NC-DOT. Rep. Sutton supported the name change at the state level and the name change was approved by the NC-DOT. The new signs of American Indian Highway were placed on the new sections of I-74 once the highway construction was completed. |
265_27 | Future
In Graham County, NCDOT has proposed to relocate US 74 onto a new divided four-lane highway from Robbinsville to Stecoah. This new routing will feature controlled at-grade intersections, viaduct and tunnel (at Stecoah Gap). At a cost of $383 million, right-of-way acquisition is scheduled to begin in 2014 and construction to begin in 2016; however, this is subject to reprioritization. The project is part of an overall project to bypass the current routing through the Nantahala Gorge, where bottlenecks are common along the two-lane highway through protected valley area within the Nantahala National Forest. The overall project, from Andrews to Almond, would complete a four-lane expressway from Cherokee County to Asheville. |
265_28 | The US 74 Bypass, in Cleveland County, is a controlled-access highway bypassing north of Shelby. When completed, it will improve vehicle capacity along the US 74 corridor, reduce future traffic congestion, increase safety and improve roadway continuity between I-26 and I-85. Being built in six sections, the cost is estimated at $295.9 million; currently, three of the six sections are fully funded with construction starting in 2014, ending in 2017.
The Independence Widening project, in Mecklenburg County, is to enhance and improve traffic flow and safety along US 74 in east Charlotte, by converting the corridor into an expressway grade highway from Center City to Matthews. Current construction is being done on three new interchanges at Sharon-Amity Road, Idlewild Road and Conference Drive. The cost of this section is at $101.2 million, with construction completed by October 15, 2016. |
265_29 | In Union and Anson counties, the US 74 freeway upgrade and Wadesboro Bypass is an estimated $741 million project. Plans include linking with future Monroe Bypass to existing Rockingham Bypass with upgrading to existing facilities to freeway standards and bypass the cities of both Marshville (to the south) and Wadesboro (to the north). The project is currently unfunded.
Junction list
See also
Special routes of U.S. Route 74
North Carolina Bicycle Route 2
North Carolina Bicycle Route 5
References
External links
NCRoads.com: US 74
NCRoads.com: US 74-A
NCRoads.com: US 74 Business
Endpoints of U.S. Highway 74 |
265_30 | 74
74
74
Transportation in Hamilton County, Tennessee
Transportation in Bradley County, Tennessee
Transportation in Polk County, Tennessee
Transportation in Cherokee County, North Carolina
Transportation in Graham County, North Carolina
Transportation in Swain County, North Carolina
Transportation in Jackson County, North Carolina
Transportation in Haywood County, North Carolina
Transportation in Buncombe County, North Carolina
Transportation in Polk County, North Carolina
Transportation in Rutherford County, North Carolina
Transportation in Cleveland County, North Carolina
Transportation in Gaston County, North Carolina
Transportation in Mecklenburg County, North Carolina
Transportation in Union County, North Carolina
Transportation in Anson County, North Carolina
Transportation in Richmond County, North Carolina
Transportation in Scotland County, North Carolina
Transportation in Robeson County, North Carolina
Transportation in Columbus County, North Carolina |
265_31 | Transportation in Brunswick County, North Carolina
Transportation in New Hanover County, North Carolina
Transportation in Charlotte, North Carolina
Transportation in Chattanooga, Tennessee |
266_0 | Michael Laub (born 1953, in Belgium) is an avant-garde stage director and contemporary dance choreographer. His work has notably been shown at the Venice Biennale of 1984, the Festival d'Avignon of 2005, the Burgtheater in 2011, and several times at ImPulsTanz Vienna International Dance Festival and Hebbel am Ufer (HAU) Berlin. He has often been described as a minimalist and "one of the founding fathers of anti-illusionist theater".
Career |
266_1 | Laub's career began in the mid-1970s when based in Stockholm, founding and co-directing Maniac Productions with Edmundo Za. Their work was referred to as innovative; mixing Performance art and Video installation. Genevieve van Cauwenberge observed that the performances "are in fact polyvalent and difficult to classify. They make use of everything at once, combining their specific language, stage direction, plastic arts (Minimal Art), musical composition (repetitive sampling) body language (Body Art), Happening (intervention of hazard) and of course the electronic video image." |
266_2 | With the founding of Remote Control Productions in 1981, Michael Laub proceeded to take his work somewhat closer to theater. Influenced by various forms, ranging from soap operas to classic literature and dance, his output as director of Remote Control Productions currently stands at over thirty plays. In what is perhaps something of an oversimplification of his extensive body of work, one can divide the material by three thematic approaches; the musical (Rough, Solo, Daniel and the Dancers, Total Masala Slammer); classic literature (Frank Wedekind's Lulu, Frankula, The Hans Christian Andersen Project); and portrait work (Portraits 360 Seconds, Out of Sorts, Alone/Gregoire, and The Biography Remix with Marina Abramović). One constant, since Rewind Song in 1989, has been the collaboration between Remote Control Productions and musician Larry Steinbachek, formerly of the band Bronski Beat. |
266_3 | Many theater critics have noted the conventions-challenging nature of Laub's work. When reviewing Daniel and the Dancers one writer commented that "the theatrical illusion has been destroyed, and what is happening on stage is simply a new reality." Deconstructing theater, finding novel ways in which to reconfigure the elements of a performance, is what fascinates and distinguishes this artist. A review pertaining to the same piece in the Danish newspaper Politiken attributes a certain violence to this theatrical approach. "This is masterful comedy," writes Monna Dithmer, "-served by the Laub diva Charlotte Engelkes-and a masterclass in the Laub technique, the aim of which is to smash the whole theatre process into bits and pieces and display them in all their naked glory." |
266_4 | It was only in the mid nineties, and in particular with the success of the play Rough, that Michael Laub/Remote Control Productions garnered international recognition. As a result, the ensuing works became more elaborate in scope and far-reaching in audience. An example of this was Laub's play Total Masala Slammer/Heartbreak No. 5 (2001), in which six months of research in India brought his fascination with Bollywood, Kathak dance and music into a synthesis with Goethe and Western contemporary live art forms. The H.C. Andersen Project (2003) was another ambitious project that used a multitude of biographical and literary interpretations in exploring Laub's take on the famous Danish subject. The Austrian daily Der Standard lauded the resulting mash-up, stating the play's "masterful blend of condensed fairytales, biographical notes, and exquisitely transfigured personae from Andersen’s universe is achieved through clarity of dramatic structure, the lightness of the 'show' form, the |
266_5 | outstanding dancers and performers, and the subtle music of Larry Steinbachek". |
266_6 | Between the large-scale productions of Total Masala Slammer and The H.C. Andersen Project, Laub directed Portraits 360 Sek at Hamburg's Deutsches Schauspielhaus in 2002 which was commissioned by Tom Stromberg. This was an undertaking which would spur his long-standing fascination with the applications of portraiture in theater to evolve. Having experienced success with solo portraits (Solo with Charlotte Engelkes, and Out of Sorts with Richard Crane), Laub began, with Portraits 360 Sek to extend the idea to a collective performance, and in time, a serialized concept. |
266_7 | For the Laub portrait of the performance artist Marina Abramović in The Biography Remix (2004-'05), content called for a multi-layered format; "One moment you are watching the young Abramović on video, the next Abramović played by one of her young students, then Abramović in the flesh", but the object remained grounded in a very direct approach. While one critic noted that "above all one remembers authentic emotion, which culminated in the final glimpse of a smile from the artist. It is beautiful, very beautiful; terribly intimate; and perfectly universal." Libération concluded that "The Remix is generally as disturbing as it is moving". A quality one would anticipate, even aspire to, in a performance chronicling the life and work of an artist who has spent decades pushing the boundaries of physical and emotional endurance. |
266_8 | 360 Sek and the ensuing Portrait Series projects (there have been five to date) eschew almost all theatrics and strip the performer's role down to often uncomfortably intimate biographical details. "By linking the unstructured with the well-calculated, the director subtly conveys to the audience some idea of those elements of which theatre is composed: exuberance and effort, yearning and application, happiness and fear. Yet because the individual portraits are so direct, as an exercise in vanity this self-portraiture remains modest. The quietly non-intentional gets the same six short minutes as the noisily exhibitionist, and that is why, in the final resort, the theatre emerges victorious as a powerhouse of the imagination as opposed to a factory of personalities." The focus is on realism and authenticity. This is made all the more evident with Laub often favoring non-professionals for these projects, as their untrained stage personae are all the more vulnerable and raw. |
266_9 | The Portrait Series have proven popular, in part due to the concept's adaptability. From a theoretical point of view, The Portrait Series is an endeavor wherein he tests theater's global vocabulary. The idea being that virtually any entity comprising interesting characters can be formatted by Laub for a Portrait Series show.
He opened 2010 with the highly personal, original composition Death, Dance and some Talk in Berlin (February), followed by Portrait Series Istanbul (April–May), Portrait Series Rotterdam (September), and commencing work on the Burgporträts at the Burgtheater, Vienna. |
266_10 | After opening the Burgporträts (March) in 2011, Michael Laub's attentions shifted to the emerging arts scene in Cambodia. For the past five years he has embarked on a series of projects exploring traditional and contemporary Cambodian artistic expression. The Portrait Series Battambang began in 2012 in conjunction with Phare Ponleu Selpak, and culminated in the Galaxy Khmer tour collaboration with the rock band Cambodian Space Project, bringing these distinct voices to Europe two years later.
2016 began with the opening of the solo performance Asutorito Endoruwaito (January) in Berlin's Hebbel am Ufer, which was followed by Dance Portraits - Cambodia opening at ImPulsTanz Vienna International Dance Festival and the Weltmuseum Wien (February). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.