Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@streamline-computing.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Fortran: Intel vs G77
Date: Wed, 15 Jan 2003 23:22:00 -0000	[thread overview]
Message-ID: <20030115232223.A18112@streamline-computing.com> (raw)
In-Reply-To: <20030115220843.GA12316@nevyn.them.org>; from drow@mvista.com on Wed, Jan 15, 2003 at 05:08:43PM -0500

On Wed, Jan 15, 2003 at 05:08:43PM -0500, Daniel Jacobowitz wrote:
>On Wed, Jan 15, 2003 at 09:51:04PM +0000, David Lecomber wrote:
[..]>
>Sure, via gcc_compiled, but that's not the right way to approach this
>problem.
>
>First of all, what version of G77 did you test with?  And what format
>of debug information?

g77 2.96 (on redhat-7.3) -- symptom also appears in the g77 of
redhat-6.2 but I don't have the version to hand --  and Intel Fortran
Compiler v6.0.

The debug info was the default from the -g option.  I've now also just
run g77 with -gdwarf and the same problem arises..

>Secondly, which compiler's debug information is correct?  Or are they
>just different and triggering different bugs?

Beats me ;-) -- a good googling uncovers g77 probably has its problems
-- but as gdb doesn't get it right all the time for either compiler,
whichever format is correct we need to do something in gdb to be
consistent.  
 
I think using the gcc_compiled flag is the way to go to merge the
patches into one gdb build.  I know it seems like a hack, but it seems
a whole lot easier than getting folks to change either the Intel or
GNU compiler.  It looks like the issue has been known about for a long
time so perhaps the compiler people just can't agree?

>Third, it really sounds like we're going to need copyright assignment
>papers from you.

No probs -- will contact the appropriate folks at FSF (unless you have
one to hand)

Cheers
David



  reply	other threads:[~2003-01-15 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 21:51 David Lecomber
2003-01-15 22:09 ` Daniel Jacobowitz
2003-01-15 23:22   ` David Lecomber [this message]
2003-01-16  4:41     ` Daniel Jacobowitz
2003-01-16 10:40       ` David Lecomber

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=20030115232223.A18112@streamline-computing.com \
    --to=david@streamline-computing.com \
    --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