public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66927] [6 Regression] ICE in gfc_conf_procedure_call
Date: Tue, 27 Oct 2015 01:01:00 -0000	[thread overview]
Message-ID: <bug-66927-4-k2Y72KeUkB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66927-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66927

--- Comment #17 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Done, 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68108
>From gcc-bugs-return-500639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Oct 27 01:08:57 2015
Return-Path: <gcc-bugs-return-500639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117447 invoked by alias); 27 Oct 2015 01:08:57 -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 117392 invoked by uid 55); 27 Oct 2015 01:08:53 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66927] [6 Regression] ICE in gfc_conf_procedure_call
Date: Tue, 27 Oct 2015 01:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: vehre at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66927-4-AyRYAc7z5p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66927-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg02194.txt.bz2
Content-length: 488

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66927

--- Comment #18 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Oct 27, 2015 at 01:01:37AM +0000, juergen.reuter at desy dot de wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66927
> 
> --- Comment #17 from Jürgen Reuter <juergen.reuter at desy dot de> ---
> Done, 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68108
> 

I may have a patch already written.  Need to run testsuite.
>From gcc-bugs-return-500640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Oct 27 01:09:24 2015
Return-Path: <gcc-bugs-return-500640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118291 invoked by alias); 27 Oct 2015 01:09:23 -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 118227 invoked by uid 55); 27 Oct 2015 01:09:18 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66927] [6 Regression] ICE in gfc_conf_procedure_call
Date: Tue, 27 Oct 2015 01:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: vehre at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66927-4-EiwSsMTSzp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66927-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg02195.txt.bz2
Content-length: 488

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66927

--- Comment #19 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Oct 27, 2015 at 01:01:37AM +0000, juergen.reuter at desy dot de wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66927
> 
> --- Comment #17 from Jürgen Reuter <juergen.reuter at desy dot de> ---
> Done, 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68108
> 

I may have a patch already written.  Need to run testsuite.
>From gcc-bugs-return-500641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Oct 27 01:11:41 2015
Return-Path: <gcc-bugs-return-500641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40694 invoked by alias); 27 Oct 2015 01:11:40 -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 35605 invoked by uid 48); 27 Oct 2015 01:11:36 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68108] [6.0 regression] erroneous error message 'scalar integer expression expected'
Date: Tue, 27 Oct 2015 01:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-68108-4-sIjTNHelF9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68108-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68108-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: 2015-10/txt/msg02196.txt.bz2
Content-length: 1485

https://gcc.gnu.org/bugzilla/show_bug.cgi?idh108

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-10-27
                 CC|                            |kargl at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |kargl at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from kargl at gcc dot gnu.org ---
This looks like fallout from my patch for PR fortran/67805.

2015-10-24  Steven G. Kargl  <kargl@gcc.gnu.org>

        PR fortran/67805
        * array.c (gfc_match_array_constructor): Check for error from type
        spec matching.
        * decl.c (char_len_param_value): Check for valid of charlen parameter.
        Reap dead code dating to 2008.
        match.c (gfc_match_type_spec): Special case the keyword use in REAL.

Tentative patch

Index: decl.c
==================================================================--- decl.c      (revision 229390)
+++ decl.c      (working copy)
@@ -754,7 +754,8 @@ char_len_param_value (gfc_expr **expr, b

       gfc_reduce_init_expr (e);

-      if ((e->ref && e->ref->u.ar.type != AR_ELEMENT)
+      if ((e->ref && e->ref->type == REF_ARRAY
+          && e->ref->u.ar.type != AR_ELEMENT)
          || (!e->ref && e->expr_type == EXPR_ARRAY))


      parent reply	other threads:[~2015-10-27  1:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18  9:40 [Bug fortran/66927] New: [6.0 regression] " juergen.reuter at desy dot de
2015-07-18  9:41 ` [Bug fortran/66927] " juergen.reuter at desy dot de
2015-07-18  9:55 ` dominiq at lps dot ens.fr
2015-07-18  9:58 ` vehre at gcc dot gnu.org
2015-07-18 10:01 ` juergen.reuter at desy dot de
2015-07-18 13:01 ` vehre at gcc dot gnu.org
2015-07-21  7:58 ` [Bug fortran/66927] [6 Regression] " rguenth at gcc dot gnu.org
2015-08-06 10:09 ` vehre at gcc dot gnu.org
2015-10-06  8:40 ` vehre at gcc dot gnu.org
2015-10-16  8:34 ` rguenth at gcc dot gnu.org
2015-10-25 12:29 ` vehre at gcc dot gnu.org
2015-10-25 13:03 ` vehre at gcc dot gnu.org
2015-10-25 16:47 ` hjl.tools at gmail dot com
2015-10-25 18:04 ` vehre at gcc dot gnu.org
2015-10-26 13:04 ` vehre at gcc dot gnu.org
2015-10-26 22:43 ` juergen.reuter at desy dot de
2015-10-26 23:42 ` juergen.reuter at desy dot de
2015-10-27  0:55 ` kargl at gcc dot gnu.org
2015-10-27  1:01 ` juergen.reuter at desy dot de [this message]

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-66927-4-k2Y72KeUkB@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).