public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/54694] [4.7/4.8/4.9 Regression] internal compiler error: in dwarf2out_frame_debug_expr, at dwarf2out.c:2387
Date: Fri, 10 Jan 2014 19:17:00 -0000	[thread overview]
Message-ID: <bug-54694-4-IGXPKNLkpG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54694-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to H.J. Lu from comment #12)
> *** Bug 59763 has been marked as a duplicate of this bug. ***

Are you sure this is a duplicate? The ICE is at different location and adding
-mno-avx doesn't help. In fact, -march=corei7 was not used in the testcase at
all.
>From gcc-bugs-return-440030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 10 19:20:06 2014
Return-Path: <gcc-bugs-return-440030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21229 invoked by alias); 10 Jan 2014 19:20:05 -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 21184 invoked by uid 48); 10 Jan 2014 19:20:02 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/59764] New: Read logicals, line buffer, item_count, and error message consistancy
Date: Fri, 10 Jan 2014 19:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
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-59764-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-01/txt/msg01172.txt.bz2
Content-length: 964

http://gcc.gnu.org/bugzilla/show_bug.cgi?idY764

            Bug ID: 59764
           Summary: Read logicals, line buffer, item_count, and error
                    message consistancy
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libfortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jvdelisle at gcc dot gnu.org

The itemc-count variable is used for two purposes, keep track of items in a
read cycle and as a pointer into a look-ahead line buffer when reading
logicals.  Some of the error messages for bad logicals need to be revised to
reflect what the value means. It is the position with the line where the error
was found and not the sequence number of the item in the READ list.

Consider separating these uses of the item_count variable so they do not
collide when reading logicals.

See pr59700 for related test cases.


  parent reply	other threads:[~2014-01-10 19:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 21:10 [Bug preprocessor/54694] New: " toralf.foerster at gmx dot de
2012-09-25  7:34 ` [Bug preprocessor/54694] " rguenth at gcc dot gnu.org
2012-09-25 15:27 ` toralf.foerster at gmx dot de
2012-09-26  9:10 ` rguenth at gcc dot gnu.org
2012-09-26 17:19 ` toralf.foerster at gmx dot de
2012-09-26 17:59 ` markus at trippelsdorf dot de
2013-01-03 19:35 ` toralf.foerster at gmx dot de
2013-11-16 21:46 ` valentin.ilie at gmail dot com
2013-11-28 11:45 ` octoploid at yandex dot com
2013-11-28 12:08 ` [Bug debug/54694] [4.7/4.8/4.9 Regression] " Joost.VandeVondele at mat dot ethz.ch
2013-11-28 12:15 ` hjl.tools at gmail dot com
2013-11-28 12:17 ` hjl.tools at gmail dot com
2013-12-19 15:19 ` rguenth at gcc dot gnu.org
2014-01-10 19:17 ` ubizjak at gmail dot com [this message]
2014-01-10 19:26 ` hjl.tools at gmail dot com
2014-01-13 19:32 ` rth at gcc dot gnu.org
2014-01-13 19:42 ` toralf.foerster at gmx dot de
2014-01-15 21:41 ` rth at gcc dot gnu.org
2014-01-15 21:47 ` [Bug debug/54694] [4.7/4.8 " rth at gcc dot gnu.org
2014-01-16 16:24 ` rth at gcc dot gnu.org
2014-01-16 16:34 ` rth at gcc dot gnu.org
2014-01-16 16:35 ` rth at gcc dot gnu.org
2014-01-16 19:16 ` jakub at gcc dot gnu.org
2014-01-16 19:21 ` jakub at gcc dot gnu.org
2014-01-16 19:22 ` jakub at gcc dot gnu.org
2015-09-05  2:49 ` gang.chen.5i5j at gmail dot com

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-54694-4-IGXPKNLkpG@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).