public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107397] New: [10/11/12/13 Regression] ICE in gfc_arith_plus, at fortran/arith.cc:654
Date: Tue, 25 Oct 2022 17:29:13 +0000	[thread overview]
Message-ID: <bug-107397-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107397
           Summary: [10/11/12/13 Regression] ICE in gfc_arith_plus, at
                    fortran/arith.cc:654
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Affects versions down to r10, r9 gives an error.
Started between 20190630 and 20190728.


$ cat z1.f90
program p
   type t
      real :: a = 1.0
   end type
   type(t), parameter :: x = z'1'
   x%a = x%a + 2
   x%a = x%a - 2
   x%a = x%a * 2
   x%a = x%a / 2
   x%a = x%a ** 2
end


$ gfortran-13-20221023 -c z1.f90
f951: internal compiler error: Segmentation fault
0xf43b3f crash_signal
        ../../gcc/toplev.cc:314
0x7c25fb gfc_arith_plus
        ../../gcc/fortran/arith.cc:654
0x7c0ee3 reduce_binary
        ../../gcc/fortran/arith.cc:1514
0x7c1352 eval_intrinsic
        ../../gcc/fortran/arith.cc:1701
0x83418c match_level_2
        ../../gcc/fortran/matchexp.cc:524
0x8342c2 match_level_3
        ../../gcc/fortran/matchexp.cc:551
0x8343b4 match_level_4
        ../../gcc/fortran/matchexp.cc:599
0x8343b4 match_and_operand
        ../../gcc/fortran/matchexp.cc:693
0x8345a2 match_or_operand
        ../../gcc/fortran/matchexp.cc:722
0x834672 match_equiv_operand
        ../../gcc/fortran/matchexp.cc:765
0x834744 match_level_5
        ../../gcc/fortran/matchexp.cc:811
0x833b11 gfc_match_expr(gfc_expr**)
        ../../gcc/fortran/matchexp.cc:870
0x82b0f0 gfc_match(char const*, ...)
        ../../gcc/fortran/match.cc:1131
0x82ceb9 gfc_match_assignment()
        ../../gcc/fortran/match.cc:1330
0x858310 match_word
        ../../gcc/fortran/parse.cc:67
0x858310 decode_statement
        ../../gcc/fortran/parse.cc:363
0x859e0a next_free
        ../../gcc/fortran/parse.cc:1402
0x859e0a next_statement
        ../../gcc/fortran/parse.cc:1634
0x85b84b parse_spec
        ../../gcc/fortran/parse.cc:4190
0x85ea5c parse_progunit
        ../../gcc/fortran/parse.cc:6237

             reply	other threads:[~2022-10-25 17:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 17:29 gscfq@t-online.de [this message]
2022-10-25 18:21 ` [Bug fortran/107397] " anlauf at gcc dot gnu.org
2022-10-25 19:31 ` marxin at gcc dot gnu.org
2022-10-26 14:07 ` kargl at gcc dot gnu.org
2022-10-28 11:12 ` rguenth at gcc dot gnu.org
2022-10-28 20:31 ` anlauf at gcc dot gnu.org
2022-10-28 21:43 ` sgk at troutmask dot apl.washington.edu
2022-10-28 21:51 ` anlauf at gcc dot gnu.org
2022-10-29 19:09 ` anlauf at gcc dot gnu.org
2022-12-18  3:39 ` cvs-commit at gcc dot gnu.org
2022-12-18 12:18 ` rimvydas.jas at gmail dot com
2022-12-18 12:19 ` rimvydas.jas at gmail dot com
2022-12-19 10:35 ` cvs-commit at gcc dot gnu.org
2023-01-17 20:49 ` [Bug fortran/107397] [10/11/12 " anlauf at gcc dot gnu.org
2023-07-07 10:44 ` [Bug fortran/107397] [11/12 " rguenth at gcc dot gnu.org
2023-07-07 20:30 ` anlauf at gcc dot gnu.org
2023-08-05 23:52 ` jvdelisle at gcc dot gnu.org
2023-08-06  0:34 ` cvs-commit at gcc dot gnu.org
2023-08-06  0:34 ` cvs-commit at gcc dot gnu.org
2023-08-06  0:54 ` cvs-commit at gcc dot gnu.org
2023-08-06  0:54 ` cvs-commit at gcc dot gnu.org
2023-08-06  1:04 ` jvdelisle 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-107397-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).