Re: Fortran: Intel vs G77

[Daniel Jacobowitz <drow@mvista.com>]

On Wed, Jan 15, 2003 at 11:22:23PM +0000, David Lecomber wrote:
> 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..

Could you try a recent (i.e. 3.2 or 3.2.1) version of g77?  Those are
pretty old.

> >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?

No, testing this sort of thing on gcc_compiled is too much of a hack
until we have looked directly at the debug info and figured out what it
should say.

> >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)

Ask assign@gnu.org for the paperwork, they'd be glad to give it to you.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer