Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Jim Blandy <jimb@zwingli.cygnus.com>, gdb@sources.redhat.com
Subject: Re: DWARF2 problem with g++-3.0
Date: Wed, 13 Jun 2001 22:55:00 -0000	[thread overview]
Message-ID: <87zobbhage.fsf@cgsoftware.com> (raw)
In-Reply-To: <87hexjitk9.fsf@cgsoftware.com>

Daniel Berlin <dan@cgsoftware.com> writes:


> As Jason Merrill confirmed for me, for at least C and C++, we can
> eliminate any symbols with the same name, declared in the same line,
> of the same file.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
And before you worry, i've subsetted this elimination to only be
performed for symbols in include files, and turned off by default,
just to be on the safe side.
Even though the subsetting makes it exactly equivalent to the BINCL/EINCL optimization STABS
performs (in full form, you can generate pathological C code
that isn't strictly legal, but gcc will allow you to compile.  You
can't do the same for C++, but i didn't want to special case the
language). Literally. It will remove exactly the same symbols, hand verified.
It provably has to, anyway.  It's just an explicit form
of EINCL/BINCL optimization.
EINCL/BINCL tells you all the symbols in the include file for you.
We have to calculate it approriately (which isn't particularly
difficult, since we know which is the main source file for a CU, and
which are the include files.  And know what symbols go with what files. 
files).


-- 
"I like to pick up hitchhikers.  When they get in the car I say,
"Put on your seat belt.  I want to try something.  I saw it once
in a cartoon, but I think I can do it."
"-Steven Wright


  reply	other threads:[~2001-06-13 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 20:41 Daniel Berlin
2001-06-13  7:53 ` Jim Blandy
2001-06-13 21:17   ` Daniel Berlin
2001-06-13 22:55     ` Daniel Berlin [this message]
2001-06-14 15:59     ` Jim Blandy

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=87zobbhage.fsf@cgsoftware.com \
    --to=dan@cgsoftware.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@zwingli.cygnus.com \
    /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