public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29216] Derived type components of function results are not initialised
Date: Mon, 25 Sep 2006 16:29:00 -0000	[thread overview]
Message-ID: <20060925162942.9417.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29216-13292@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from pault at gcc dot gnu dot org  2006-09-25 16:29 -------
Yup, does it for me too! Confirmed.

As soon as I am near no an F95 standard, I will confirm that a function result
should indeed be initialized; logic suggests that it should!

Paul

$ /irun/bin/gfortran --version
GNU Fortran 95 (GCC) 4.2.0 20060919 (experimental)
Copyright (C) 2006 Free Software Foundation, Inc.

GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Fortran
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING


Administrator@NONE-X6EIN5I8FN /home/alloc_comps
$ ./a
 F           3
 T  1628825276
 T  1628825276


-- 

pault at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-09-25 16:29:41
               date|                            |


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


  reply	other threads:[~2006-09-25 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 15:47 [Bug fortran/29216] New: " stephan dot kramer at imperial dot ac dot uk
2006-09-25 16:29 ` pault at gcc dot gnu dot org [this message]
2006-10-08 22:04 ` [Bug fortran/29216] " pault at gcc dot gnu dot org
2006-10-10  7:56 ` fxcoudert at gcc dot gnu dot org
2006-10-10 12:48 ` pault at gcc dot gnu dot org
2006-10-10 20:49 ` pault at gcc dot gnu dot org
2006-10-16 16:51 ` pault at gcc dot gnu dot org
2006-10-17  4:55 ` pault at gcc dot gnu dot org
2006-10-17 14:05 ` patchapp at dberlin dot org
2006-10-18 11:20 ` patchapp at dberlin dot org
2006-10-19  4:51 ` pault at gcc dot gnu dot org
2006-10-19  6:42 ` pault at gcc dot gnu dot org
2006-11-10 21:53 ` pault 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=20060925162942.9417.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).