public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55852] [4.6/4.7/4.8 regression] internal compiler error: in gfc_build_intrinsic_call, at fortran/expr.c:4647 Date: Tue, 08 Jan 2013 16:56:00 -0000 [thread overview] Message-ID: <bug-55852-4-ECCY3VnId1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55852-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55852 --- Comment #10 from Andreas Schwab <schwab@linux-m68k.org> 2013-01-08 16:55:58 UTC --- The test case fails because the match is too strict. $ grep iszs intrinsic_size_3.f90.003t.original integer(kind=2) iszs; iszs = (integer(kind=2)) MAX_EXPR <(D.854->dim[0].ubound - D.854->dim[0].lbound) + 1, 0>;
next prev parent reply other threads:[~2013-01-08 16:56 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-03 1:08 [Bug fortran/55852] New: " latlon90180+gcc_bugzilla at gmail dot com 2013-01-03 9:39 ` [Bug fortran/55852] " janus at gcc dot gnu.org 2013-01-03 9:43 ` [Bug fortran/55852] [4.6/4.7/4.8 regression] " janus at gcc dot gnu.org 2013-01-03 11:01 ` dominiq at lps dot ens.fr 2013-01-03 11:10 ` burnus at gcc dot gnu.org 2013-01-03 11:13 ` dominiq at lps dot ens.fr 2013-01-04 17:27 ` jakub at gcc dot gnu.org 2013-01-06 20:56 ` tkoenig at gcc dot gnu.org 2013-01-06 21:59 ` tkoenig at gcc dot gnu.org 2013-01-07 11:11 ` burnus at gcc dot gnu.org 2013-01-07 15:24 ` burnus at gcc dot gnu.org 2013-01-07 19:11 ` burnus at gcc dot gnu.org 2013-01-08 16:56 ` schwab@linux-m68k.org [this message] 2013-02-13 14:39 ` burnus at gcc dot gnu.org 2013-02-13 14:44 ` janus at gcc dot gnu.org 2013-02-13 15:09 ` burnus at gcc dot gnu.org 2013-02-13 17:51 ` burnus at gcc dot gnu.org 2013-02-13 17:52 ` burnus at gcc dot gnu.org 2013-02-13 19:21 ` latlon90180+gcc_bugzilla 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-55852-4-ECCY3VnId1@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).