public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: brent verner <brent@rcfile.org>
To: gcc <gcc@gcc.gnu.org>
Subject: can you help me help?
Date: Fri, 15 Sep 2000 17:04:00 -0000	[thread overview]
Message-ID: <20000915200403.A31940@rcfile.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

Hi,

  I know all of the ones-who-know are very busy, but if someone out 
there familiar with the c++ front end could help me get started, I'd 
appreciate it much. Basically, I've been searching for references on 
how a c++ file (magically?) gets compiled... Specifically, I'm trying
to solve (what I think to be) a problem with builtin functions and
namespaces -- http://gcc.gnu.org/ml/gcc/2000-09/msg00009.html .

general questions:

Is there a 'Five minute overview of how g++ works' document floating
  around anywhere? If not, I'll put one together if someone'll help
  me understand the process.

Do any of you have a list of files that are used to compile the 
  resultant g++? (I have a list I pieced together by following the 
  Makefile, but I'm pretty sure I'm not looking at all of the relevant
  files)


thanks.
  brent

-- 
Damon Brent Verner                        o      _     _         _
Cracker Jack® Surprise Certified  _o     /\_   _ \\o  (_)\__/o  (_)
brent@rcfile.org                _< \_   _>(_) (_)/<_    \_| \   _|/' \/
brent@linux1.org               (_)>(_) (_)        (_)   (_)    (_)'  _\o_

                 reply	other threads:[~2000-09-15 17:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20000915200403.A31940@rcfile.org \
    --to=brent@rcfile.org \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).