public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "c dot lemmen at fz-juelich dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/18108] [gfortran] overloading does not work for functions
Date: Wed, 08 Jun 2005 08:57:00 -0000 [thread overview]
Message-ID: <20050608085721.21327.qmail@sourceware.org> (raw)
In-Reply-To: <20041022084631.18108.martin@mpa-garching.mpg.de>
------- Additional Comments From c dot lemmen at fz-juelich dot de 2005-06-08 08:57 -------
> > Surprisingly (to me), adding a second call to the function resolves the problem,
> > i.e. in the examples below the following code works
> >
> > subroutine baz
> > logical l
> > l = bar (3)
> > l = bar (3) ! alternatively, call l=bar(3.0)
> > end subroutine
> >
> I verified that it actually calls the right routine under these circumstances.
> From the compiler output with -fump-parse-tree:
> ASSIGN l bar_real[[((3.0000000))]]
> ASSIGN l bar_real[[((3.0000000))]]
>
Does this mean that calling twice is a verified workaround solution? Should I
have confidence in the results of this workaround?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18108
next prev parent reply other threads:[~2005-06-08 8:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 8:46 [Bug fortran/18108] New: " martin at mpa-garching dot mpg dot de
2004-10-22 8:47 ` [Bug fortran/18108] " martin at mpa-garching dot mpg dot de
2004-10-29 8:13 ` c dot lemmen at fz-juelich dot de
2004-11-11 11:44 ` c dot lemmen at fz-juelich dot de
2004-11-12 10:40 ` martin at mpa-garching dot mpg dot de
2004-11-26 13:33 ` martin at mpa-garching dot mpg dot de
2004-11-26 14:40 ` bdavis at gcc dot gnu dot org
2004-11-30 15:21 ` tobi at gcc dot gnu dot org
2004-11-30 15:22 ` tobi at gcc dot gnu dot org
2005-01-11 0:17 ` steven at gcc dot gnu dot org
2005-05-05 16:40 ` pinskia at gcc dot gnu dot org
2005-06-08 8:57 ` c dot lemmen at fz-juelich dot de [this message]
2005-06-08 9:02 ` martin at mpa-garching dot mpg dot de
2005-06-08 10:20 ` c dot lemmen at fz-juelich dot de
2005-06-08 11:28 ` c dot lemmen at fz-juelich dot de
2005-06-09 10:16 ` martin at mpa-garching dot mpg dot de
2005-06-13 14:13 ` david dot c dot gregory at gmail dot com
2005-07-07 22:38 ` steven at gcc dot gnu dot org
2005-07-15 20:40 ` tkoenig at gcc dot gnu dot org
2005-08-02 7:54 ` paulthomas2 at wanadoo dot fr
2005-08-02 10:14 ` c dot lemmen at fz-juelich dot de
2005-08-02 10:24 ` steven at gcc dot gnu dot org
2005-08-11 22:27 ` 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=20050608085721.21327.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).