public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32404] Wrong-code with sbdart (valgrind errors, different output)
Date: Wed, 20 Jun 2007 17:04:00 -0000	[thread overview]
Message-ID: <20070620170356.18549.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32404-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from burnus at gcc dot gnu dot org  2007-06-20 17:03 -------
> I can reproduce what you see, nor make any sense of the instructions comparing
"cannot" I presume
> the outputs: when I do what you indicate, all I see in the output is a
> namelist-type

I knew I would forget something. I did run "bash test_runs" before, which
creates the "INPUT" files. The last "INPUT" file (which I therefore used) was

 &INPUT
  tcloud = 15
  zcloud = 1
  wlinf  = .72
  wlsup  = .72
  idatm  = 1
  isalb  = 4
  sza    = 60
  iout   = 23
  nstr   = 20
  uzen=  5,15,25,35,45,55,65,75,85,95,105,115,125,135,145,155,165,175
  phi=0,15,30,45,60,75,90,105,120,135,150,165,180 /


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-06-20 17:03:56
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32404


  parent reply	other threads:[~2007-06-20 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 15:29 [Bug fortran/32404] New: " burnus at gcc dot gnu dot org
2007-06-20  9:41 ` [Bug fortran/32404] " fxcoudert at gcc dot gnu dot org
2007-06-20 17:04 ` burnus at gcc dot gnu dot org [this message]
2007-06-20 20:00 ` burnus at gcc dot gnu dot org

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=20070620170356.18549.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).