public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug fortran/45748] New: -fimplicit-none strange behaviour
@ 2010-09-22 16:13 themos dot tsikas at gmail dot com
2010-09-22 19:09 ` [Bug fortran/45748] " jvdelisle at gcc dot gnu dot org
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: themos dot tsikas at gmail dot com @ 2010-09-22 16:13 UTC (permalink / raw)
To: gcc-bugs
Code:
SUBROUTINE BUG(WORK)
DOUBLE PRECISION WORK(MAX(2,3))
INTRINSIC MAX
END
Compile:
>gfortran -fimplicit-none -c foo.f
foo.f:4.72:
END
1
Error: Symbol 'a1' at (1) has no IMPLICIT type
foo.f:4.72:
END
1
Error: Symbol 'a2' at (1) has no IMPLICIT type
________________________________________________________________
nonsensical error when there shouldn't be one?
Regards
Themos Tsikas
--
Summary: -fimplicit-none strange behaviour
Product: gcc
Version: 4.5.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: themos dot tsikas at gmail dot com
GCC build triplet: x86_64-unknown-linux-gnu
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45748
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug fortran/45748] -fimplicit-none strange behaviour 2010-09-22 16:13 [Bug fortran/45748] New: -fimplicit-none strange behaviour themos dot tsikas at gmail dot com @ 2010-09-22 19:09 ` jvdelisle at gcc dot gnu dot org 2010-09-22 19:12 ` jvdelisle at gcc dot gnu dot org ` (2 subsequent siblings) 3 siblings, 0 replies; 5+ messages in thread From: jvdelisle at gcc dot gnu dot org @ 2010-09-22 19:09 UTC (permalink / raw) To: gcc-bugs ------- Comment #1 from jvdelisle at gcc dot gnu dot org 2010-09-22 19:09 ------- Please post result of gfortran -v -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45748 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug fortran/45748] -fimplicit-none strange behaviour 2010-09-22 16:13 [Bug fortran/45748] New: -fimplicit-none strange behaviour themos dot tsikas at gmail dot com 2010-09-22 19:09 ` [Bug fortran/45748] " jvdelisle at gcc dot gnu dot org @ 2010-09-22 19:12 ` jvdelisle at gcc dot gnu dot org 2010-09-22 19:29 ` dominiq at lps dot ens dot fr 2010-09-22 20:22 ` [Bug fortran/45748] [4.5/4.6 Regression] -fimplicit-none failures when using intrinsic MAX burnus at gcc dot gnu dot org 3 siblings, 0 replies; 5+ messages in thread From: jvdelisle at gcc dot gnu dot org @ 2010-09-22 19:12 UTC (permalink / raw) To: gcc-bugs ------- Comment #2 from jvdelisle at gcc dot gnu dot org 2010-09-22 19:12 ------- I do not see the problem with gfortran 4.3.4 on Cygwin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45748 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug fortran/45748] -fimplicit-none strange behaviour 2010-09-22 16:13 [Bug fortran/45748] New: -fimplicit-none strange behaviour themos dot tsikas at gmail dot com 2010-09-22 19:09 ` [Bug fortran/45748] " jvdelisle at gcc dot gnu dot org 2010-09-22 19:12 ` jvdelisle at gcc dot gnu dot org @ 2010-09-22 19:29 ` dominiq at lps dot ens dot fr 2010-09-22 20:22 ` [Bug fortran/45748] [4.5/4.6 Regression] -fimplicit-none failures when using intrinsic MAX burnus at gcc dot gnu dot org 3 siblings, 0 replies; 5+ messages in thread From: dominiq at lps dot ens dot fr @ 2010-09-22 19:29 UTC (permalink / raw) To: gcc-bugs ------- Comment #3 from dominiq at lps dot ens dot fr 2010-09-22 19:29 ------- Confirmed on x86_64-apple-darwin10.3.0 for 4.5.0 and trunk, but not 4.4.4, hence it is a regression. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45748 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug fortran/45748] [4.5/4.6 Regression] -fimplicit-none failures when using intrinsic MAX 2010-09-22 16:13 [Bug fortran/45748] New: -fimplicit-none strange behaviour themos dot tsikas at gmail dot com ` (2 preceding siblings ...) 2010-09-22 19:29 ` dominiq at lps dot ens dot fr @ 2010-09-22 20:22 ` burnus at gcc dot gnu dot org 3 siblings, 0 replies; 5+ messages in thread From: burnus at gcc dot gnu dot org @ 2010-09-22 20:22 UTC (permalink / raw) To: gcc-bugs ------- Comment #4 from burnus at gcc dot gnu dot org 2010-09-22 20:22 ------- As you might have guessed, the error is with regards to the arguments of MAX which are A1 and A2. The arguments are defined as BT_UNKNOWN, cf. in intrinsics.c: add_sym_1m ("max", GFC_ISYM_MAX, CLASS_ELEMENTAL, ACTUAL_NO, BT_UNKNOWN, 0, GFC_STD_F77, gfc_check_min_max, gfc_simplify_max, gfc_resolve_max, a1, BT_UNKNOWN, dr, REQUIRED, a2, BT_UNKNOWN, dr, REQUIRED); The backtrace shows: #0 gfc_set_default_type (sym=0x144e6b0, error_flag=1, ns=<value optimized out>) at fortran/symbol.c:263 #1 0x00000000005328d7 in resolve_formal_arglist (proc=0x144d1f0) at fortran/resolve.c:303 -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |rejects-valid Known to fail| |4.5.0 4.6.0 Known to work| |4.4.0 Last reconfirmed|0000-00-00 00:00:00 |2010-09-22 20:22:16 date| | Summary|-fimplicit-none strange |[4.5/4.6 Regression] - |behaviour |fimplicit-none failures when | |using intrinsic MAX Target Milestone|--- |4.5.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45748 ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-09-22 20:22 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-09-22 16:13 [Bug fortran/45748] New: -fimplicit-none strange behaviour themos dot tsikas at gmail dot com 2010-09-22 19:09 ` [Bug fortran/45748] " jvdelisle at gcc dot gnu dot org 2010-09-22 19:12 ` jvdelisle at gcc dot gnu dot org 2010-09-22 19:29 ` dominiq at lps dot ens dot fr 2010-09-22 20:22 ` [Bug fortran/45748] [4.5/4.6 Regression] -fimplicit-none failures when using intrinsic MAX burnus at gcc dot gnu dot org
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).