public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/60101] [4.7/4.8/4.9 Regression] Long compile times when mixed complex floating point datatypes are used in lengthy expressions
Date: Tue, 11 Feb 2014 13:17:00 -0000	[thread overview]
Message-ID: <bug-60101-4-i5WQQPT1aC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60101-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Sorry for not being more helpful, it was a long time ago that I worked on that.
Perhaps if you tell me which revision did the reversal/implemented the
special-handling of SAVE_EXPR, I can figure out what is going on.
>From gcc-bugs-return-443280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 11 13:29:13 2014
Return-Path: <gcc-bugs-return-443280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19091 invoked by alias); 11 Feb 2014 13:29:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19077 invoked by uid 48); 11 Feb 2014 13:29:10 -0000
From: "loximann at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60144] New: Misleading error message when missing "then" after "if" and "else if"
Date: Tue, 11 Feb 2014 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: loximann at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-60144-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-02/txt/msg01037.txt.bz2
Content-length: 1077

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`144

            Bug ID: 60144
           Summary: Misleading error message when missing "then" after
                    "if" and "else if"
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: loximann at gmail dot com

Compiler version:
GNU Fortran (Ubuntu 20130917-1ubuntu1) 4.9.0 20130917 (experimental) [trunk
revision 202647]

Test program:
--------------------
program ifelif
    if (.TRUE.)
    else if (.FALSE.)
    end if
end program
--------------------

Error messages:
----------------------
if.F90:2.15:

    if (.TRUE.)
               1
Error: Cannot assign to a named constant at (1)
if.F90:3.11:

    else if (.FALSE.)
           1
Error: Unexpected junk after ELSE statement at (1)
[...]
----------------------

Both errors should read something like "Missing THEN after IF/ELSE IF".

The first error message doesn't even make sense...


  parent reply	other threads:[~2014-02-11 13:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 19:51 [Bug c/60101] New: " thorstenkurth at me dot com
2014-02-07 12:38 ` [Bug c/60101] [4.7/4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2014-02-10 13:59 ` mpolacek at gcc dot gnu.org
2014-02-10 17:29 ` mpolacek at gcc dot gnu.org
2014-02-10 17:43 ` mpolacek at gcc dot gnu.org
2014-02-10 18:12 ` jakub at gcc dot gnu.org
2014-02-10 20:07 ` mpolacek at gcc dot gnu.org
2014-02-11 13:10 ` manu at gcc dot gnu.org
2014-02-11 13:15 ` jakub at gcc dot gnu.org
2014-02-11 13:17 ` manu at gcc dot gnu.org [this message]
2014-02-12  7:36 ` jakub at gcc dot gnu.org
2014-02-12  7:40 ` [Bug c/60101] [4.7/4.8 " jakub at gcc dot gnu.org
2014-03-06  8:02 ` jakub at gcc dot gnu.org
2014-06-12 13:35 ` [Bug c/60101] [4.7 " rguenth 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-60101-4-i5WQQPT1aC@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).