From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: kamaraju@gmail.com, fortran@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: gfortran - gdb problem
Date: Tue, 26 Jul 2005 09:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0507230443210.11626@localhost.localdomain> (raw)
In-Reply-To: <20050726031703.GA25841@nevyn.them.org>
On Mon, 25 Jul 2005, Daniel Jacobowitz wrote:
> No; adding checks specific to the language is almost always wrong. The
> only case insensitive languages in the GDB source tree are Scheme (and
> I don't think the Scheme support has worked in many years) and Fortran.
> So disabling it for Fortran is about the same as deleting the code
> entirely.
OK. I cancel this method. I don't know the big picture before.
>
> Here's the original patch:
> http://sourceware.org/ml/gdb-patches/2000-08/msg00025.html
>
> Presumably, whatever HP Fortran compiler Jimmy Guo was trying to add
> support for always generated symbols in lowercase, so this was
> sufficient. gfortran doesn't. It appears to use case somewhat
> inconsistently.
>
> 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.
IMHO, the case insensitive lookup might be the long-term resolution. What
about define "strcmp" as an macro of "strcasecmp" if case_sensitive is
false? This might seems ugly, but it should help here.
Regards
- Wu Zhou
next prev parent reply other threads:[~2005-07-26 9:01 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
2005-07-26 9:01 ` Wu Zhou [this message]
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=Pine.LNX.4.63.0507230443210.11626@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=drow@false.org \
--cc=fortran@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kamaraju@gmail.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).