public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/14957] [gfortran] testsuite issues Date: Thu, 03 Jun 2004 19:15:00 -0000 [thread overview] Message-ID: <20040603191527.13781.qmail@sourceware.org> (raw) In-Reply-To: <20040414171503.14957.jv244@cam.ac.uk> ------- Additional Comments From tobi at gcc dot gnu dot org 2004-06-03 19:15 ------- (In reply to comment #0) > incorrect equivalence: > intrinsic_fraction_exponent.f90 > intrinsic_set_exponent.f90 Indeed, this could be achieved with TRANSFER instead. We don't seem to enforce all restrictions on EQUIVALENCE, we might want to enforce them but allow a way out via a language extension. The problem is: INTEGER I REAL R EQUIVALENCE (R,I) ! not allowed, can only equivalence same basic type > arguments of different kind to max: > intrinsic_minmax.f90 This is a language extension. See the code in check.c:check_rest(). This shouldn't pass with -pedantic. > syntax error (subroutine missing?): > stack_varsize.f90 Test passes here. Supposedly it's been fixed in the meantime. > non-standard intrinsic (dcmplx): > cmplx.f90 A language extension. > incorrect length of character variables passed: > intrinisic_index.f90 > intrinisic_trim.f90 True, this is a quality of implementation issue we should keep track of. > f95: > st_function.f90, line 32: Subobject of constant not allowed in statement > function Do you have a quote from the standard to back this? I couldn't find one. > several instances where e.g. an integer is passed to a subroutine expecting a > real. In principle that is illegal (but very common, indeed). Does it warn with -pedantic? It should. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |tobi at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14957
next prev parent reply other threads:[~2004-06-03 19:15 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-14 18:27 [Bug fortran/14957] New: " jv244 at cam dot ac dot uk 2004-04-14 18:35 ` [Bug fortran/14957] " pinskia at gcc dot gnu dot org 2004-04-14 19:27 ` jv244 at cam dot ac dot uk 2004-05-13 23:24 ` jv244 at cam dot ac dot uk 2004-06-03 19:15 ` tobi at gcc dot gnu dot org [this message] 2004-06-10 11:07 ` jv244 at cam dot ac dot uk 2004-06-10 11:31 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-06-10 11:52 ` jv244 at cam dot ac dot uk 2004-06-10 12:19 ` tobi at gcc dot gnu dot org 2004-06-10 12:35 ` tobi at gcc dot gnu dot org 2004-06-10 12:41 ` cvs-commit at gcc dot gnu dot org 2004-06-10 12:48 ` tobi at gcc dot gnu dot org 2004-06-12 15:02 ` cvs-commit at gcc dot gnu dot org 2004-06-28 7:28 ` [Bug fortran/14957] " pinskia at gcc dot gnu dot org 2004-07-15 20:32 ` tobi at gcc dot gnu dot org 2004-08-25 17:06 ` 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=20040603191527.13781.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: linkBe 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).