Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Elias Athanasopoulos <eathan@otenet.gr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] faster language identification
Date: Thu, 07 Nov 2002 11:33:00 -0000	[thread overview]
Message-ID: <20021107193409.GA25879@nevyn.them.org> (raw)
In-Reply-To: <20021107224622.D1136@neutrino.particles.org>

On Thu, Nov 07, 2002 at 10:46:22PM +0200, Elias Athanasopoulos wrote:
> Hi all,
> 
> DWARFx encodes the language. In such a case, I think it is more 
> reliable to get the language from the object, instead of looking at the 
> source files' extensions.
> 
> Comments?

Please don't.  See:

/* Set the initial language.

   A better solution would be to record the language in the psymtab when reading
   partial symbols, and then use it (if known) to set the language.  This would
   be a win for formats that encode the language in an easily discoverable place,
   such as DWARF.  For stabs, we can jump through hoops looking for specially
   named symbols or try to intuit the language from the specific type of stabs
   we find, but we can't do that until later when we read in full symbols.
   FIXME.  */

static void
set_initial_language (void)

Either that or there should be a psymtab_language() method somewhere.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-11-07 19:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 11:26 Elias Athanasopoulos
2002-11-07 11:33 ` Daniel Jacobowitz [this message]
2002-11-07 11:43   ` Elias Athanasopoulos
2002-11-07 11:47     ` Daniel Jacobowitz
2002-11-07 11:58       ` Elias Athanasopoulos
2002-11-07 12:55         ` Michael Snyder
2002-11-10  5:43           ` Elias Athanasopoulos
2002-11-10 11:03             ` Daniel Jacobowitz
2002-11-13 10:01               ` Jim Blandy
2002-11-13 10:11                 ` Daniel Jacobowitz
2002-11-13 10:39                   ` 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=20021107193409.GA25879@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=eathan@otenet.gr \
    --cc=gdb-patches@sources.redhat.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