How is compiler software compiled?

  • Thread starter Thread starter Bararontok
  • Start date Start date
  • Tags Tags
    Compiler Software
Click For Summary
SUMMARY

The discussion centers on the process of compiling compilers, specifically through techniques such as bootstrapping and cross-compilation. It clarifies the distinction between assemblers and compilers, emphasizing that assemblers are not compilers and are typically written in machine language. The conversation also highlights the historical context of programming languages, detailing how early computing relied on manual input methods and the evolution of software development tools like Turbo Assembler and Turbo C++. The participants address misconceptions about terminology and the complexities involved in writing software at different abstraction levels.

PREREQUISITES
  • Understanding of bootstrapping in compiler design
  • Familiarity with assembly language and machine language
  • Knowledge of cross-compilation techniques
  • Experience with Turbo Assembler and Turbo C++
NEXT STEPS
  • Research the bootstrapping process in compiler construction
  • Learn about cross-compilation and its applications
  • Explore the differences between assemblers and compilers
  • Investigate the historical development of programming languages and early computing methods
USEFUL FOR

Software developers, computer science students, and anyone interested in the intricacies of compiler design and the evolution of programming languages.

  • #31
jtbell said:
You're right. I guess I didn't have to re-enter the paper tape loader as often as I thought I remembered. I did have to do it often enough to have that piece of paper with machine language code (written out in octal for ease of reading) taped next to the switches. Probably my programs ran amuck sometimes and wiped out the loader. :-p

A friend of mine who used to managed the computers in the EE dept of my old university recalled almost exactly the same account of manually entering the tape boot-loader code as per your experience (almost word for word actually). So I tend to believe that your memory of this is quite sound. :)

Personally I have no first hand knowledge of this, but here is my hunch: If say the typical up-time of the computer was many days (or even weeks) then it might have been considered thoroughly worthwhile to trade-off 10-15 minutes of your time each re-boot (in manually entering the boot loader code) for the advantage of having that small extra handful of bytes available for user programs. Considering the extremely limited available memory of these early computers, then this does actually make sense.
 

Similar threads

Difference between interpreted and compiled files....
  • · Replies 29 ·
Replies
29
Views
3K
How did early compilers overcome the need for a compiler to compile itself?
  • · Replies 6 ·
Replies
6
Views
3K
C/C++ Cpp in visual studio: cmake and being able to compile
  • · Replies 0 ·
Replies
0
Views
2K
C/C++ How to avoid compilation errors with multiple header files in C++?
  • · Replies 2 ·
Replies
2
Views
2K
Interpreter vs Compiler: What Are the Differences and Benefits?
  • · Replies 59 ·
2
Replies
59
Views
9K
Storing program source as relations in a database instead of text file
  • · Replies 65 ·
3
Replies
65
Views
5K
Unison - A new approach to Distributed computing, Storing Code, etc.
  • · Replies 7 ·
Replies
7
Views
3K
C/C++ Why overload prototype statement works in .h file but not in main file
  • · Replies 2 ·
Replies
2
Views
3K
What is the best compiler now for intensive calculations?
  • · Replies 13 ·
Replies
13
Views
2K
How to include two header files that are contained in the same folder?
  • · Replies 4 ·
Replies
4
Views
5K