public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nicolas dot girard at nerim dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/21034] internal compiler error: in gfc_trans_auto_array_allocation, at fortran/trans-array.c:3036
Date: Fri, 15 Apr 2005 06:09:00 -0000	[thread overview]
Message-ID: <20050415060915.14801.qmail@sourceware.org> (raw)
In-Reply-To: <20050414223325.21034.nicolas.girard@nerim.net>


------- Additional Comments From nicolas dot girard at nerim dot net  2005-04-15 06:09 -------
Sure. 
Actually the main file is a .F file. The tgz I'm about to attach contain the 
following files: 
 
- main.F : main file 
- guess.h  params.h  pinch_complet.h  prec.h: included by the preprocessor 
- routines.h.ok : when renamed to routines.h, the program compiles fine 
- routines.h.bug: when renamed to routines.h, causes the bug to appear 
 
"$ diff routines.*" gives: 
408c408 
<         subroutine solution(n,xf,fg,h1,h2,beta,pas,tolerance,nmax,xav) 
--- 
>         subroutine solution(xf,fg,h1,h2,beta,pas,tolerance,nmax,xav) 
438c438 
<         parameter (n1=5,n2=5,ndims=10) 
--- 
>         parameter (n1=5,n2=5,n=1024,ndims=10) 
 
All I did was to add "n" as a new parameter of the solution() subroutine ; here 
the call to solution() is unchanged but adding a variable corresponding to n in 
the function call changes nothing, the bug still appears. 
 
Thanks again, 
cheers  

-- 


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


  parent reply	other threads:[~2005-04-15  6:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 22:33 [Bug fortran/21034] New: " nicolas dot girard at nerim dot net
2005-04-14 22:35 ` [Bug fortran/21034] " nicolas dot girard at nerim dot net
2005-04-14 23:33 ` pinskia at gcc dot gnu dot org
2005-04-15  6:09 ` nicolas dot girard at nerim dot net [this message]
2005-04-15  6:10 ` nicolas dot girard at nerim dot net
2005-04-15  8:30 ` fxcoudert at gcc dot gnu dot org
2005-06-22 15:34 ` cvs-commit at gcc dot gnu dot org
2005-06-22 16:00 ` pbrook at gcc dot gnu dot org
2005-06-22 16:03 ` fxcoudert at gcc dot gnu dot org
2005-06-22 18:51 ` pbrook at gcc dot gnu dot org
2005-06-22 18:51 ` pbrook at gcc dot gnu dot org
2005-06-22 18:52 ` [Bug fortran/21034] [4.0 only] " pinskia at gcc dot gnu dot org
2005-07-15 15:22 ` cvs-commit at gcc dot gnu dot org
2005-07-15 15:29 ` pbrook at gcc dot gnu dot org
2005-07-27 12:52 ` reichelt 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=20050415060915.14801.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).