public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54818] [4.7/4.8 Regression] error: type mismatch in binary expression
Date: Wed, 19 Dec 2012 09:04:00 -0000	[thread overview]
Message-ID: <bug-54818-4-qe45yoqmTx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54818-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-12-19 09:03:46 UTC ---
My patch is wrong. It might lead to passing an integer(8) instead of integer(4)
as hidden argument when calling a procedure. The proper way it to use
gfc_charlen_type_node.

However, the following works:

--- a/gcc/fortran/trans-intrinsic.c
+++ b/gcc/fortran/trans-intrinsic.c
@@ -5664,3 +5664,3 @@ scalar_transfer:
       se->expr = tmpdecl;
-      se->string_length = dest_word_len;
+      se->string_length = fold_convert (gfc_charlen_type_node, dest_word_len);
     }


  parent reply	other threads:[~2012-12-19  9:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05  0:15 [Bug fortran/54818] New: " scott+gcc+bugzilla at pakin dot org
2012-10-05  8:55 ` [Bug fortran/54818] [4.7/4.8 Regression] " dominiq at lps dot ens.fr
2012-10-05  9:10 ` janus at gcc dot gnu.org
2012-10-05 10:02 ` rguenth at gcc dot gnu.org
2012-10-05 10:21 ` dominiq at lps dot ens.fr
2012-10-21 14:50 ` tkoenig at gcc dot gnu.org
2012-11-13 15:39 ` jakub at gcc dot gnu.org
2012-12-17 20:57 ` burnus at gcc dot gnu.org
2012-12-19  9:04 ` burnus at gcc dot gnu.org [this message]
2012-12-20  8:13 ` burnus at gcc dot gnu.org
2012-12-20 10:48 ` burnus at gcc dot gnu.org
2012-12-20 10:51 ` burnus at gcc dot gnu.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-54818-4-qe45yoqmTx@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: 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).