public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "scott+gcc+bugzilla at pakin dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54818] New: error: type mismatch in binary expression Date: Fri, 05 Oct 2012 00:15:00 -0000 [thread overview] Message-ID: <bug-54818-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54818 Bug #: 54818 Summary: error: type mismatch in binary expression Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: scott+gcc+bugzilla@pakin.org Created attachment 28360 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28360 Sample file that gfortran can't compile PGI can compile the attached file: $ pgf90 --version pgf90 12.5-0 64-bit target on x86-64 Linux -tp istanbul Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved. Copyright 2000-2012, STMicroelectronics, Inc. All Rights Reserved. $ pgf90 -c broken.f GCC cannot: $ gfortran --version GNU Fortran (GCC) 4.7.1 Copyright (C) 2012 Free Software Foundation, Inc. GNU Fortran comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of GNU Fortran under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING $ gfortran -c broken.f broken.f: In function ‘broken’: broken.f:1:0: error: type mismatch in binary expression integer(kind=8) integer(kind=8) integer(kind=4) D.1918 = D.1867 + 8; broken.f:1:0: error: type mismatch in binary expression integer(kind=8) integer(kind=8) integer(kind=4) D.1922 = D.1867 + 8; broken.f:1: confused by earlier errors, bailing out
next reply other threads:[~2012-10-05 0:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-05 0:15 scott+gcc+bugzilla at pakin dot org [this message] 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 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@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).