public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30887] %VAL only accepts default-kind integer/real/complex
Date: Wed, 21 Feb 2007 05:17:00 -0000	[thread overview]
Message-ID: <20070221051700.29054.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30887-11040@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from paulthomas2 at wanadoo dot fr  2007-02-21 05:16 -------
Subject: Re:  %VAL only accepts default-kind integer/real/complex

Tobias,
> ------- Comment #1 from burnus at gcc dot gnu dot org  2007-02-20 17:32 -------
> Paul, do you remember why you have added the following restriction?
>
> (The example is accepted by ifort, nagf95 and g95.)
>
> resolve.c:
>               if (((e->ts.type == BT_REAL || e->ts.type == BT_COMPLEX)
>                    && e->ts.kind > gfc_default_real_kind)
>                   || (e->ts.kind > gfc_default_integer_kind))
>                 {
>                   gfc_error ("Kind of by-value argument at %L is larger "
>                              "than default kind", &e->where);
>                   return FAILURE;
>   
One of the compilers, whose implementation of %VAL I checked, had this 
restriction.  I now cannot find which one.

There is absolutely no reason why the restriction should not be removed.

Best regards

Paul


-- 


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


  parent reply	other threads:[~2007-02-21  5:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20 17:22 [Bug fortran/30887] New: %VAL construct fails on 64 bit p dot w dot draper at durham dot ac dot uk
2007-02-20 17:29 ` [Bug fortran/30887] " pinskia at gcc dot gnu dot org
2007-02-20 17:33 ` [Bug fortran/30887] %VAL only accepts default-kind integer/real/complex burnus at gcc dot gnu dot org
2007-02-21  5:17 ` paulthomas2 at wanadoo dot fr [this message]
2007-02-22 18:52 ` sdirkse at gams dot com
2007-02-22 19:24 ` kargl at gcc dot gnu dot org
2007-02-22 19:51 ` burnus at gcc dot gnu dot org
2007-02-22 21:10 ` patchapp at dberlin dot org
2007-02-22 21:35 ` sdirkse at gams dot com
2007-02-23 15:44 ` p dot w dot draper at durham dot ac dot uk
2007-02-28 18:18 ` burnus at gcc dot gnu dot org
2007-02-28 18:26 ` burnus 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=20070221051700.29054.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).