public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95107] ICE in hash_operand, at fold-const.c:3768
Date: Fri, 01 Jul 2022 20:20:41 +0000	[thread overview]
Message-ID: <bug-95107-4-HPuPHKN58e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95107-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from anlauf at gcc dot gnu.org ---
The issue can be studied by playing with option -fmax-stack-var-size=n.
-fno-automatic corresponds to n=0; using n=64 and higher lets the code compile.
There's something weird going on here.

  parent reply	other threads:[~2022-07-01 20:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 16:22 [Bug fortran/95107] New: [10/11 Regression] " gscfq@t-online.de
2020-05-14  6:16 ` [Bug fortran/95107] " rguenth at gcc dot gnu.org
2020-05-14  7:47 ` marxin at gcc dot gnu.org
2020-05-14 14:34 ` [Bug fortran/95107] " gscfq@t-online.de
2020-07-23  6:51 ` rguenth at gcc dot gnu.org
2020-10-23  4:39 ` egallager at gcc dot gnu.org
2020-10-23  4:42 ` egallager at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-12-20 19:43 ` pinskia at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2022-07-01 20:20 ` anlauf at gcc dot gnu.org [this message]
2023-02-06 20:12 ` anlauf at gcc dot gnu.org
2023-02-07 18:22 ` cvs-commit at gcc dot gnu.org
2023-02-08 20:19 ` cvs-commit at gcc dot gnu.org
2023-02-10 19:30 ` cvs-commit at gcc dot gnu.org
2023-02-11 18:16 ` cvs-commit at gcc dot gnu.org
2023-02-11 18:20 ` anlauf 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-95107-4-HPuPHKN58e@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).