public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael dot baudin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35959] Recursive function with allocatable array
Date: Fri, 18 Apr 2008 08:14:00 -0000	[thread overview]
Message-ID: <20080418081334.17692.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35959-16071@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]



------- Comment #3 from michael dot baudin at gmail dot com  2008-04-18 08:13 -------
Subject: Re:  Recursive function with allocatable array

Hi Paul,

The generic source code that you sent to me is interesting
and you analysis is very clear. Thank you for taking the time
to fix this.

But I wonder how you produced this source (which have many in common
with C), because I looked in the  gfortran manual, and I obviously
did not find any option to generate the generic source code,
which is an internal step. Is that available only with the middle-end
of gfortran and not available for end-users ?

Best regards,

Michaël


On Thu, Apr 17, 2008 at 10:37 PM, pault at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
>  ------- Comment #2 from pault at gcc dot gnu dot org  2008-04-17 20:37 -------
>  This is indeed a bug.  A fix will be posted in half an hour or so.
>
>
>  Paul
>
>
>  --
>
>  pault at gcc dot gnu dot org changed:
>
>            What    |Removed                     |Added
>  ----------------------------------------------------------------------------
>          AssignedTo|unassigned at gcc dot gnu   |pault at gcc dot gnu dot org
>                    |dot org                     |
>              Status|NEW                         |ASSIGNED
>    Last reconfirmed|2008-04-17 05:59:41         |2008-04-17 20:37:53
>
>
>                date|                            |
>
>
>  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35959
>
>  ------- You are receiving this mail because: -------
>  You reported the bug, or are watching the reporter.
>


-- 


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


  parent reply	other threads:[~2008-04-18  8:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16 20:05 [Bug fortran/35959] New: " michael dot baudin at gmail dot com
2008-04-17  6:00 ` [Bug fortran/35959] " pault at gcc dot gnu dot org
2008-04-17 20:38 ` pault at gcc dot gnu dot org
2008-04-18  8:14 ` michael dot baudin at gmail dot com [this message]
2008-04-18 14:05 ` jvdelisle at gcc dot gnu dot org
2008-04-18 14:12 ` michael dot baudin at gmail dot com
2008-04-18 15:07 ` michael dot baudin at gmail dot com
2008-04-19 21:57 ` pault at gcc dot gnu dot org
2008-04-19 22:31 ` pault at gcc dot gnu dot org
2008-04-19 22:33 ` pault at gcc dot gnu dot org
2008-04-24 19:56 ` michael dot baudin at gmail dot com

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=20080418081334.17692.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).