public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38822] Compile-time simplification of x**(real) / ICE in in gfc_target_encode_expr
Date: Tue, 20 Jan 2009 19:41:00 -0000 [thread overview]
Message-ID: <20090120194139.23126.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38822-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from kargl at gcc dot gnu dot org 2009-01-20 19:41 -------
(In reply to comment #7)
> I have a patch that not only fixes the ICE, but it will issue an
> error for a program of the form
>
> troutmask:sgk[203] cat a.f90
> program a
> real z(int(transfer(2.e0**2.e0, 1.e0)) + 1)
> z = 1.
> print '(5ES12.5)', z
> end program a
> troutmask:sgk[204] gfc4x -o z a.f90
> troutmask:sgk[205] ./z
> 1.00000E+00 1.00000E+00 1.00000E+00 1.00000E+00 1.00000E+00
> troutmask:sgk[206] gfc4x -o z -std=f95 a.f90
> a.f90:2.32:
>
> real z(int(transfer(2.e0**2.e0, 1.e0)) + 1)
> 1
> Error: Fortran 2003: Noninteger exponent in an initialization expression at (1)
>
> Note, I plan to change the word initialization to restricted.
>
Dang, I got this wrong. There is a distinction between an initialization
and specification expressions where a non-integer exponent is indeed allowed
in the latter and prohibited in the former. I, at least, still have the
ICE fixed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38822
next prev parent reply other threads:[~2009-01-20 19:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 10:53 [Bug fortran/38822] New: " burnus at gcc dot gnu dot org
2009-01-13 16:33 ` [Bug fortran/38822] Compile-time simplification of x**(real) / " burnus at gcc dot gnu dot org
2009-01-14 15:30 ` burnus at gcc dot gnu dot org
2009-01-16 0:55 ` kargl at gcc dot gnu dot org
2009-01-16 2:47 ` kargl at gcc dot gnu dot org
2009-01-16 2:58 ` jvdelisle at gcc dot gnu dot org
2009-01-16 5:26 ` kargl at gcc dot gnu dot org
2009-01-20 19:22 ` kargl at gcc dot gnu dot org
2009-01-20 19:41 ` kargl at gcc dot gnu dot org [this message]
2009-03-29 20:41 ` kargl at gcc dot gnu dot org
2009-03-30 0:54 ` [Bug fortran/38822] Compile-time simplification of x**(real) kargl at gcc dot gnu dot org
2009-04-04 9:41 ` dominiq at lps dot ens dot fr
2009-04-04 15:10 ` kargl at gcc dot gnu dot org
2009-04-04 20:44 ` dominiq at lps dot ens dot fr
2009-04-04 21:42 ` sgk at troutmask dot apl dot washington dot edu
2009-04-05 19:43 ` dominiq at lps dot ens dot fr
2010-01-15 18:31 ` kargl at gcc dot gnu dot org
2010-05-19 14:44 ` dfranke 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=20090120194139.23126.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).