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/60561] New: ICE in gimplify_var_or_parm_decl, at gimplify.c:1721  for gfortran.dg/associate_1.f03
Date: Tue, 18 Mar 2014 09:28:00 -0000	[thread overview]
Message-ID: <bug-60561-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60561
           Summary: ICE in gimplify_var_or_parm_decl, at gimplify.c:1721
                    for gfortran.dg/associate_1.f03
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org

A similar backtrace one gets for PR c++/58907.

Compiling the testsuite's gfortran.dg/associate_1.f03 with "gfortran" leads to
an ICE.

The is no ICE if one runs "gfortran -std=f2003 -fall-intrinsics -cpp 
associate_1.f03" as it is done in the test suite itself.



$ gfortran associate_1.f03
Warning: associate_1.f03:97: Illegal preprocessor directive
Warning: associate_1.f03:112: Illegal preprocessor directive
associate_1.f03: In function ‘test_char’:
associate_1.f03:104:0: internal compiler error: in gimplify_var_or_parm_decl,
at gimplify.c:1721
     str = "foobar"
 ^
0x8a998a gimplify_var_or_parm_decl
        ../../gcc/gimplify.c:1721
0x8b0424 gimplify_expr(tree_node**, gimple_statement_base**,
gimple_statement_base**, bool (*)(tree_node*), int)
        ../../gcc/gimplify.c:7879
0x8b8edd gimplify_addr_expr
        ../../gcc/gimplify.c:4801
>From gcc-bugs-return-446657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 18 09:31:02 2014
Return-Path: <gcc-bugs-return-446657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12373 invoked by alias); 18 Mar 2014 09:31:01 -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 12114 invoked by uid 48); 18 Mar 2014 09:30:57 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/60557] UBSAN: ICE after ubsan_expand_null_ifn
Date: Tue, 18 Mar 2014 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
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:
Message-ID: <bug-60557-4-VfHOgtbj27@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60557-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60557-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-03/txt/msg01526.txt.bz2
Content-length: 412

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

--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> This should hopefully fix it.

Looks good to me. For the testcase of comment 1, it also gives the expected
run-time diagnostic:

test.f90:19: runtime error: signed integer overflow: 809078955 * 65539 cannot
be represented in type 'integer(kind=4)'


             reply	other threads:[~2014-03-18  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18  9:28 burnus at gcc dot gnu.org [this message]
2014-03-18  9:34 ` [Bug fortran/60561] " rguenth at gcc dot gnu.org
2014-03-18  9:35 ` dominiq at lps dot ens.fr
2014-03-18  9:39 ` dominiq at lps dot ens.fr
2014-03-18  9:48 ` dominiq at lps dot ens.fr
2014-03-18 11:00 ` burnus at gcc dot gnu.org
2014-12-08 23:26 ` dominiq at lps dot ens.fr

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-60561-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: 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).