Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Lecomber <david@streamline-computing.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Fortran: Intel vs G77
Date: Wed, 15 Jan 2003 22:09:00 -0000	[thread overview]
Message-ID: <20030115220843.GA12316@nevyn.them.org> (raw)
In-Reply-To: <20030115215104.A17981@streamline-computing.com>

On Wed, Jan 15, 2003 at 09:51:04PM +0000, David Lecomber wrote:
> The current situation with g77 and Intel meets gdb is as follows for
> multi-dim arrays
> 
> Intel compiled code:
>   whatis -- wrong way round real(4 * 5 ) is reported as real (5 * 4)
>   indexing -- correct 
>   print elements -- boundaries not aligned properly ( it prints a 5 * 4 
> as a 4 * 5 )
> 
> 
> g77 fortran compilers compiled code:
>   whatis -- correct
>   print elements -- correct
>   indexing -- 'print A(1,2)' will get the wrong answer.
> 
> So, unless there is a method to check what the compiler was used, we are
> left with
> 
>   1. status quo
> or
>   2. compile up two different versions -- one for gdb + intel, the
> other for gdb + g77
> 
> Does anyone know of the existence of such a check?

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?

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

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

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-01-15 22:09 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 [this message]
2003-01-15 23:22   ` David Lecomber
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=20030115220843.GA12316@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=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