public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19292] [meta-bug] g77 features lacking in gfortran
Date: Sun, 08 Jan 2006 00:51:00 -0000	[thread overview]
Message-ID: <20060108005122.10519.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19292-8513@http.gcc.gnu.org/bugzilla/>



------- Comment #12 from pinskia at gcc dot gnu dot org  2006-01-08 00:51 -------
(In reply to comment #11)
> As I am clearly no the author the the code, I have no real position to defend.
> As my post 25705 makes clear legalistic arguments should be avoided. I also
> coded a parallel C program and used f2c on the code fragment posted. In both
> cases gcc-4.1.0 emitted object code without complaint. In this respect C and
> fortran are both block structured languages without nesting of subroutines.
> Therefore, if gcc-4.1.0 can handle it for C a parallel construct should do it
> for fortran.

C is different than Fortran.  I am not clear why you are bring that up at all.

Also ICC warns about the code which is why I put in PR 25705 which makes me
question the code  and if other compiler also warns (or even errors out) about
it (by default), it is even more questionable.

Also fortran does have nesting of subroutines, I don't get why you said it is
not, it is a feature of Fortran 90.  You can do something like:
function g(f)
REAL :: g
REAL :: f
g = h()
contains
function h()
REAL :: h
h = f +1.0
end function
end function


-- 


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



  parent reply	other threads:[~2006-01-08  0:51 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19292-8513@http.gcc.gnu.org/bugzilla/>
2005-11-12 23:29 ` fxcoudert at gcc dot gnu dot org
2006-01-07 20:30 ` malitzke at metronets dot com
2006-01-07 21:55 ` kargl at gcc dot gnu dot org
2006-01-07 22:17 ` sgk at troutmask dot apl dot washington dot edu
2006-01-08  0:33 ` malitzke at metronets dot com
2006-01-08  0:51 ` pinskia at gcc dot gnu dot org [this message]
2006-01-08  1:58 ` sgk at troutmask dot apl dot washington dot edu
2006-01-08  2:30 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2006-01-08  2:43 ` sgk at troutmask dot apl dot washington dot edu
2006-01-08 10:41 ` malitzke at metronets dot com
2006-01-08 13:18 ` tobi at gcc dot gnu dot org
2006-01-08 16:37 ` sgk at troutmask dot apl dot washington dot edu
2006-01-08 20:27 ` pault at gcc dot gnu dot org
2006-05-27 19:24 ` sgk at troutmask dot apl dot washington dot edu
2006-05-27 20:24 ` Thomas dot Koenig at online dot de
2006-05-27 20:28 ` sgk at troutmask dot apl dot washington dot edu
2006-07-03 12:14 ` franke dot daniel at gmail dot com
2006-07-03 12:58 ` fxcoudert at gcc dot gnu dot org
2006-07-03 16:41 ` jvdelisle at gcc dot gnu dot org
2006-07-03 17:17 ` sgk at troutmask dot apl dot washington dot edu
2006-07-26 12:07 ` fxcoudert at gcc dot gnu dot org
2006-10-02  9:41 ` fxcoudert at gcc dot gnu dot org
2006-12-17 18:21 ` pertusus at free dot fr
2006-12-18 21:39 ` pertusus at free dot fr
2007-08-14 23:22 ` fxcoudert at gcc dot gnu dot org
2007-08-16 12:10 ` fxcoudert at gcc dot gnu dot org
2005-01-06 14:39 [Bug fortran/19292] New: [metabug] " tobi at gcc dot gnu dot org
2005-01-20 10:47 ` [Bug fortran/19292] [meta-bug] " Thomas dot Koenig at online dot de
2005-01-22 22:33 ` pbrook at gcc dot gnu dot org
2005-01-23  0:25 ` dje at gcc dot gnu dot org
2005-01-23 22:38 ` pbrook at gcc dot gnu dot org
2005-01-29 15:39 ` pinskia at gcc dot gnu dot org
2005-02-19 12:59 ` wilson at gcc dot gnu dot org
2005-02-20 22:21 ` kargl at gcc dot gnu dot org
2005-02-22 13:07 ` pinskia at gcc dot gnu dot org
2005-02-24 14:32 ` rth at gcc dot gnu dot org
2005-03-11 14:17 ` pinskia at gcc dot gnu dot org
2005-03-13 19:10 ` tobi at gcc dot gnu dot org
2005-03-13 19:29 ` tobi at gcc dot gnu dot org
2005-03-14 20:17 ` tobi at gcc dot gnu dot org
2005-03-16  0:19 ` fengwang at gcc dot gnu dot org
2005-03-16 14:32 ` tobi at gcc dot gnu dot org
2005-03-17  2:14 ` pinskia at gcc dot gnu dot org
2005-03-22 22:17 ` fxcoudert at gcc dot gnu dot org
2005-03-22 23:19 ` tobi at gcc dot gnu dot org
2005-03-25  7:07 ` fxcoudert at gcc dot gnu dot org
2005-03-25 13:37 ` fxcoudert at gcc dot gnu dot org
2005-03-26 17:44 ` pinskia at gcc dot gnu dot org
2005-04-03  8:10 ` fxcoudert at gcc dot gnu dot org
2005-04-06  9:54 ` fxcoudert at gcc dot gnu dot org
2005-04-08 11:12 ` fxcoudert at gcc dot gnu dot org
2005-04-20  1:10 ` milan at cmm dot ki dot si
2005-04-20  1:15 ` pinskia at gcc dot gnu dot org
2005-04-23 16:11 ` pault at gcc dot gnu dot org
2005-04-23 16:14 ` pault at gcc dot gnu dot org
2005-04-23 16:15 ` pault at gcc dot gnu dot org
2005-04-23 16:18 ` pault at gcc dot gnu dot org
2005-04-24 14:01 ` tobi at gcc dot gnu dot org
2005-04-30 17:53 ` pinskia at gcc dot gnu dot org
2005-05-03  7:05 ` tkoenig at gcc dot gnu dot org
2005-05-03 19:47 ` tkoenig at gcc dot gnu dot org
2005-05-03 19:50 ` tkoenig at gcc dot gnu dot org
2005-05-03 19:52 ` tkoenig at gcc dot gnu dot org
2005-05-05 23:26 ` pinskia at gcc dot gnu dot org
2005-05-11 11:18 ` pinskia at gcc dot gnu dot org
2005-05-15  3:25 ` pinskia at gcc dot gnu dot org
2005-05-31 17:01 ` ebotcazou at gcc dot gnu dot org
2005-06-16 22:29 ` fxcoudert at gcc dot gnu dot org
2005-06-16 23:04 ` fxcoudert at gcc dot gnu dot org
2005-06-17 16:25 ` fxcoudert at gcc dot gnu dot org
2005-07-01 22:11 ` pinskia at gcc dot gnu dot org
2005-07-07  9:56 ` fengwang at gcc dot gnu dot org
2005-07-09 12:14 ` tobi at gcc dot gnu dot org
2005-07-12  4:25 ` pinskia at gcc dot gnu dot org
2005-07-12  4:26 ` pinskia at gcc dot gnu dot org
2005-07-12  4:26 ` pinskia at gcc dot gnu dot org
2005-07-14 15:23 ` pault at gcc dot gnu dot org
2005-07-16 20:54 ` pinskia at gcc dot gnu dot org
2005-07-19  8:48 ` fxcoudert at gcc dot gnu dot org
2005-07-19 21:45 ` steven at gcc dot gnu dot org
2005-08-02 10:52 ` fxcoudert at gcc dot gnu dot org
2005-08-06 13:35 ` pinskia at gcc dot gnu dot org
2005-08-31 12:52 ` fxcoudert at gcc dot gnu dot org
2005-09-08 18:51 ` rsandifo at gcc dot gnu dot org
2005-09-09 22:17 ` pinskia at gcc dot gnu dot org
2005-09-09 22:17 ` pinskia at gcc dot gnu dot org
2005-09-12 11:07 ` tobi at gcc dot gnu dot org
2005-09-16  8:57 ` fxcoudert at gcc dot gnu dot org
2005-09-18 19:53 ` tkoenig at gcc dot gnu dot org
2005-09-29 21:33 ` pinskia 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=20060108005122.10519.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).