From: Jim Blandy <jimb@codesourcery.com>
To: Fran?ois-Xavier Coudert <fxcoudert@gmail.com>
Cc: gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>,
Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
Subject: Re: Problems while debugging fortran
Date: Thu, 25 Oct 2007 18:44:00 -0000 [thread overview]
Message-ID: <m3lk9rxceq.fsf@codesourcery.com> (raw)
In-Reply-To: <20071025170621.GA27275@caradoc.them.org> (Daniel Jacobowitz's message of "Thu, 25 Oct 2007 13:06:21 -0400")
Daniel Jacobowitz <drow at false.org> writes:
> On Thu, Oct 25, 2007 at 05:06:54PM +0100, Fran?ois-Xavier Coudert wrote:
>> For the longer term, what do you think is the optimal solution? I'd
>> like to make gfortran, the Fortran front-end in GCC, do The Right
>> Thing, but what is it? Should we add this DW_AT_calling_convention tag
>> for the time being, until the meaning of the DWARF standard is made
>> clearer?
>
> I'll let Jim answer this, though I think it's reasonable.
To be clear: I think the actual code in Carlos's patch is just fine.
The comment, though, should not say things that are simply untrue.
Which is why I suggested a new comment, instead of rejecting the
patch. Whether or not we like the state of DWARF in this regard, the
comment should correct describes the state of play, no?
next prev parent reply other threads:[~2007-10-25 18:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 16:07 François-Xavier Coudert
2007-10-25 17:06 ` Daniel Jacobowitz
2007-10-25 18:44 ` Jim Blandy [this message]
2007-10-25 19:01 ` Daniel Jacobowitz
2007-10-25 19:27 ` Jim Blandy
2007-10-25 20:24 ` Joel Brobecker
2007-10-25 20:36 ` Carlos Eduardo Seo
2007-10-25 20:41 ` Joel Brobecker
[not found] ` <4721034D.2060502@linux.vnet.ibm.com>
2007-11-13 17:45 ` Problems while debugging fortran -- DWARF Michael Eager
2007-10-25 20:55 ` Problems while debugging fortran Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2007-09-15 11:37 Carlos Eduardo Seo
2007-09-20 19:47 ` Joel Brobecker
2007-09-20 20:46 ` Carlos Eduardo Seo
2007-09-20 20:56 ` Joel Brobecker
2007-09-21 6:52 ` Daniel Jacobowitz
2007-09-26 21:46 ` Carlos Eduardo Seo
2007-09-26 21:51 ` Pierre Muller
2007-09-26 21:51 ` Joel Brobecker
2007-10-24 16:20 ` Carlos Eduardo Seo
2007-10-24 19:33 ` Joel Brobecker
2007-10-24 19:57 ` Daniel Jacobowitz
2007-10-24 20:16 ` Carlos Eduardo Seo
2007-10-24 21:56 ` Carlos Eduardo Seo
2007-09-23 2:52 ` Carlos Eduardo Seo
2007-09-24 10:01 ` Joel Brobecker
2007-09-24 23:49 ` Carlos Eduardo Seo
2007-09-25 1:29 ` Joel Brobecker
2007-09-25 17:34 ` Carlos Eduardo Seo
2007-09-26 6:29 ` Joel Brobecker
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=m3lk9rxceq.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=cseo@linux.vnet.ibm.com \
--cc=fxcoudert@gmail.com \
--cc=gdb@sourceware.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