From: Andy Vaught <andy@maxwell.la.asu.edu>
To: gdb-patches@cygnus.com
Subject: Re: Fortran array patches
Date: Mon, 04 Jan 1999 18:23:00 -0000 [thread overview]
Message-ID: <Pine.SGI.3.96.990104181828.27148A-100000@maxwell.la.asu.edu> (raw)
Of course, only after the patch has actually been *sent* does an alternate
explanation occur-- g77 may be at fault! Running gdb on AIX works fine,
so it looks like g77 is the one that is backwards....
Andy
----------------- XOLD(K,IC,I)=
Andy Vaught .... DO ITERS=1, 10 XOLD(K,IC,I)
andy@maxwell.la.asu.edu | | /CALLMSOLVE(A,B,X,I,ITERS,TOL)+(RANNYU(0)
Arizona State University ======|WRITE(6,'(I5,2X,F12.6)')ITERS,TOL -HALF)
Tempe, Arizona USA OOOOOO \ENDDORETURN PARAMETER(ZERO=1.D0)*TENTH*DELTA
WARNING: multiple messages have this Message-ID
From: Andy Vaught <andy@maxwell.la.asu.edu>
To: gdb-patches@cygnus.com
Subject: Re: Fortran array patches
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <Pine.SGI.3.96.990104181828.27148A-100000@maxwell.la.asu.edu> (raw)
Message-ID: <19990401000000.dVXWV7AnYgWW4uTcGG39VblSty4NaSyLkCdEh5smf1g@z> (raw)
Of course, only after the patch has actually been *sent* does an alternate
explanation occur-- g77 may be at fault! Running gdb on AIX works fine,
so it looks like g77 is the one that is backwards....
Andy
----------------- XOLD(K,IC,I)=
Andy Vaught .... DO ITERS=1, 10 XOLD(K,IC,I)
andy@maxwell.la.asu.edu | | /CALLMSOLVE(A,B,X,I,ITERS,TOL)+(RANNYU(0)
Arizona State University ======|WRITE(6,'(I5,2X,F12.6)')ITERS,TOL -HALF)
Tempe, Arizona USA OOOOOO \ENDDORETURN PARAMETER(ZERO=1.D0)*TENTH*DELTA
next reply other threads:[~1999-01-04 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-04 18:23 Andy Vaught [this message]
1999-04-01 0:00 ` Andy Vaught
[not found] <Pine.SGI.3.96.990104181828.27148A-100000.cygnus.patches.gdb@maxwell.la.asu.edu>
1999-04-01 0:00 ` Stan Shebs
1999-01-31 13:48 ` Stan Shebs
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=Pine.SGI.3.96.990104181828.27148A-100000@maxwell.la.asu.edu \
--to=andy@maxwell.la.asu.edu \
--cc=gdb-patches@cygnus.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