public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "toon at moene dot indiv dot nluug dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36316] New: type mismatch in binary expression caught by verify_gimple Date: Fri, 23 May 2008 18:23:00 -0000 [thread overview] Message-ID: <bug-36316-109@http.gcc.gnu.org/bugzilla/> (raw) The following module definition: MODULE YOMCAIN IMPLICIT NONE SAVE TYPE distributed_vector REAL, pointer :: local(:) INTEGER :: global_length,local_start,local_end,nchnks END TYPE distributed_vector INTERFACE ASSIGNMENT (=) MODULE PROCEDURE assign_dv_dv END INTERFACE INTERFACE OPERATOR (*) MODULE PROCEDURE multiply_dv_dv END INTERFACE CONTAINS SUBROUTINE assign_dv_dv (handle1,handle2) ! copy one distributed_vector to another TYPE (distributed_vector), INTENT(IN) :: handle2 TYPE (distributed_vector), INTENT(INOUT) :: handle1 handle1%local(:) = handle2%local(:) RETURN END SUBROUTINE assign_dv_dv FUNCTION multiply_dv_dv (handle1,handle2) ! multiply two distributed_vectors TYPE (distributed_vector), INTENT(IN) :: handle2 TYPE (distributed_vector), INTENT(IN) :: handle1 REAL, DIMENSION(handle1%local_start:handle1%local_end) ::multiply_dv_dv multiply_dv_dv = handle1%local(:) * handle2%local(:) RETURN END FUNCTION multiply_dv_dv SUBROUTINE CAININAD_SCALE_DISTVEC () TYPE (distributed_vector) :: PVAZG TYPE (distributed_vector) :: ZTEMP TYPE (distributed_vector) :: SCALP_DV ZTEMP = PVAZG * SCALP_DV END SUBROUTINE CAININAD_SCALE_DISTVEC END MODULE YOMCAIN draws this error message when compiling with a recent 4.4.0 gfortran: a.F90: In function 'caininad_scale_distvec': a.F90:47: error: type mismatch in binary expression integer(kind=8) integer(kind=4) integer(kind=4) D.1027 = D.1026 - D.1025 a.F90:47: internal compiler error: verify_gimple failed Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. This 4.3.1 gfortran doesn't have any complaints about this source: gfortran -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure linux gnu Thread model: posix gcc version 4.3.1 20080401 (prerelease) (Debian 4.3.0-3) -- Summary: type mismatch in binary expression caught by verify_gimple Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: toon at moene dot indiv dot nluug dot nl http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36316
next reply other threads:[~2008-05-23 18:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-23 18:23 toon at moene dot indiv dot nluug dot nl [this message] 2008-05-23 18:36 ` [Bug fortran/36316] " dominiq at lps dot ens dot fr 2008-05-23 19:57 ` burnus at gcc dot gnu dot org 2008-05-23 20:08 ` toon at moene dot indiv dot nluug dot nl 2008-05-24 11:02 ` burnus at gcc dot gnu dot org 2008-05-25 22:00 ` burnus at gcc dot gnu dot org 2008-05-26 15:49 ` fxcoudert at gcc dot gnu dot org 2008-05-27 19:23 ` burnus at gcc dot gnu dot org 2008-05-27 19:23 ` 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=bug-36316-109@http.gcc.gnu.org/bugzilla/ \ --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).