From: David Lecomber <david@allinea.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Wu Zhou <woodzltc@cn.ibm.com>,
kamaraju@gmail.com, fortran@gcc.gnu.org,
gdb <gdb@sources.redhat.com>
Subject: Re: gfortran - gdb problem
Date: Tue, 26 Jul 2005 06:57:00 -0000 [thread overview]
Message-ID: <1122361436.5625.22.camel@cpc4-oxfd8-3-0-cust114.oxfd.cable.ntl.com> (raw)
In-Reply-To: <20050726031703.GA25841@nevyn.them.org>
> The fact is, our symbol table does not support case insensitive lookup.
> I suppose one cheap solution to this would be to lower case based on CU
> language when reading in the symbol table, but that's not a very pretty
> solution. Perhaps Elena (the symbol table maintainer) has another idea.
It's presently got a bit of a mix up.. If you look in symtab.c's
lookup_symbol, you see it checks the language's sensitivity and converts
to lower case if so.
However, if you look at what any of the code which adds symbols does,
none of it actually converts any fortran symbols to lower case before
putting them in the table. Result, total mess up if your compiler
happens to put things in upper case in the dwarf section, for example
(such as Absoft). Most compilers I've seen generate only lower case for
Fortran.
Cheers
David
--
David Lecomber
CTO Allinea Software
Tel: +44 1926 623231
Fax: +44 1926 623232
next prev parent reply other threads:[~2005-07-26 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 7:31 Wu Zhou
2005-07-25 13:09 ` Daniel Jacobowitz
2005-07-26 3:05 ` Wu Zhou
2005-07-26 3:19 ` Daniel Jacobowitz
2005-07-26 6:57 ` David Lecomber [this message]
2005-07-26 9:01 ` Wu Zhou
2005-07-26 13:06 ` Daniel Jacobowitz
2005-07-28 3:43 ` Wu Zhou
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=1122361436.5625.22.camel@cpc4-oxfd8-3-0-cust114.oxfd.cable.ntl.com \
--to=david@allinea.com \
--cc=drow@false.org \
--cc=fortran@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kamaraju@gmail.com \
--cc=woodzltc@cn.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).