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: Thu, 20 Dec 2012 10:48:00 -0000 [thread overview] Message-ID: <bug-54818-4-rnTFfbxwbF@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 #8 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-12-20 10:48:15 UTC --- Author: burnus Date: Thu Dec 20 10:48:11 2012 New Revision: 194632 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194632 Log: 2012-12-20 Tobias Burnus <burnus@net-b.de> PR fortran/54818 * trans-intrinsic.c (gfc_conv_intrinsic_transfer): Ensure that the string length is of type gfc_charlen_type_node. 2012-12-20 Tobias Burnus <burnus@net-b.de> PR fortran/54818 * gfortran.dg/transfer_intrinsic_4.f: New. Added: branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/transfer_intrinsic_4.f Modified: branches/gcc-4_7-branch/gcc/fortran/ChangeLog branches/gcc-4_7-branch/gcc/fortran/trans-intrinsic.c branches/gcc-4_7-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-12-20 10:48 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 2012-12-20 8:13 ` burnus at gcc dot gnu.org 2012-12-20 10:48 ` burnus at gcc dot gnu.org [this message] 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-rnTFfbxwbF@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).