From: | Hans-Peter Diettrich <DrDiettrich1@netscape.net> |
Newsgroups: | comp.compilers |
Date: | Sun, 17 Oct 2021 07:02:30 +0200 |
Organization: | Compilers Central |
References: | 21-10-017 21-10-018 21-10-025 21-10-028 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="41526"; mail-complaints-to="abuse@iecc.com" |
Keywords: | design |
Posted-Date: | 17 Oct 2021 14:27:21 EDT |
In-Reply-To: | 21-10-028 |
On 10/16/21 11:55 PM, Hans-Peter Diettrich wrote:
> [The Bell Labs portable C compiler output assembler source code, although
> most people didn't notice since it normally assembled it and threw the
> assembler code away. Last time I checked gcc and clang do the same. -John]
I meant the final executable result is (can be) generated from source
code by a single C compiler invocation. How this result is obtained in
detail, in how many passes, by how many related tools, is not so obvious
and of less interest to the user.
Nowadays dedicated managing tools are available, starting with (batch)
Make and a number of (interactive) Integrated Development Environments.
Here the compiler can be recognized as a source code translation part of
the system, not as the all-embracing process.
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.