From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28558 invoked by alias); 16 Jan 2003 04:41:10 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 28551 invoked from network); 16 Jan 2003 04:41:09 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 16 Jan 2003 04:41:09 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18Z3ig-0004hQ-00; Thu, 16 Jan 2003 00:41:42 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18Z1pq-0004Rg-00; Wed, 15 Jan 2003 23:40:58 -0500 Date: Thu, 16 Jan 2003 04:41:00 -0000 From: Daniel Jacobowitz To: David Lecomber Cc: gdb-patches@sources.redhat.com Subject: Re: Fortran: Intel vs G77 Message-ID: <20030116044058.GA17068@nevyn.them.org> Mail-Followup-To: David Lecomber , gdb-patches@sources.redhat.com References: <20030115215104.A17981@streamline-computing.com> <20030115220843.GA12316@nevyn.them.org> <20030115232223.A18112@streamline-computing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030115232223.A18112@streamline-computing.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-01/txt/msg00592.txt.bz2 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