Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.compilers > #2497

Re: Compiler bootstrapping and the standard header files

Path csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From Hans-Peter Diettrich <DrDiettrich1@netscape.net>
Newsgroups comp.compilers
Subject Re: Compiler bootstrapping and the standard header files
Date Sun, 22 Mar 2020 04:22:18 +0100
Organization Compilers Central
Lines 22
Sender news@iecc.com
Approved comp.compilers@iecc.com
Message-ID <20-03-026@comp.compilers> (permalink)
References <20-03-018@comp.compilers> <20-03-019@comp.compilers> <20-03-021@comp.compilers> <20-03-023@comp.compilers>
Mime-Version 1.0
Content-Type text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding 8bit
Injection-Info gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="64605"; mail-complaints-to="abuse@iecc.com"
Keywords practice
Posted-Date 22 Mar 2020 11:30:13 EDT
X-submission-address compilers@iecc.com
X-moderator-address compilers-request@iecc.com
X-FAQ-and-archives http://compilers.iecc.com
Xref csiph.com comp.compilers:2497

Show key headers only | View raw


Am 20.03.2020 um 23:52 schrieb cvo:

>        Why do I ask that? Because I can start debugging and fixing my
>        compiler along with my C libraries (and C headers) since the
>        beginning instead of debugging my C libraries at step 2. In other
>        words, it is true I can compile my C libraries at step 1, but I
>        cannot debug their implementation yet because at step 1 I'm using
>        the C libraries (and headers) from the host environment. I can
>        debug my C libraries implementation only at step 2.

I don't understand what is "I" in "I'm using..." here. You can tell any
*compiler* to use your headers in compiling a test program, and to link
it using your libraries. Then you can debug your libraries as part of
that test program.

Where (static runtime) "libraries" is nothing but a collection of
previously compiled object files, which deserve no further compilation
with any new program. The linker puts together all required (listed)
object files and replaces all their references to external symbols by
the symbol definition (address) found in one of these files.

DoDi

Back to comp.compilers | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Compiler bootstrapping and the standard header files codevisio@gmail.com - 2020-03-19 05:40 -0700
  Re: Compiler bootstrapping and the standard header files Hans-Peter Diettrich <DrDiettrich1@netscape.net> - 2020-03-20 01:34 +0100
    Re: Compiler bootstrapping and the standard header files Christopher F Clark <christopher.f.clark@compiler-resources.com> - 2020-03-20 06:21 -0400
      Re: Compiler bootstrapping and the standard header files cvo <codevisio@gmail.com> - 2020-03-20 15:52 -0700
        Re: Compiler bootstrapping and the standard header files Hans-Peter Diettrich <DrDiettrich1@netscape.net> - 2020-03-22 04:22 +0100
        Re: Compiler bootstrapping and the standard header files Christopher F Clark <christopher.f.clark@compiler-resources.com> - 2020-03-22 13:51 -0400
          Re: Compiler bootstrapping and the standard header files Kaz Kylheku <493-878-3164@kylheku.com> - 2020-03-23 13:49 +0000
  Re: Compiler bootstrapping and the standard header files Christian Gollwitzer <auriocus@gmx.de> - 2020-03-20 10:21 +0100
  Re: Compiler bootstrapping and the standard header files gah4@u.washington.edu - 2020-03-21 15:32 -0700

csiph-web