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 middle-end/108435] [13 Regression] ICE in as_a, at is-a.h:242 since r13-142-g705bcedf6eae2d7c
Date: Fri, 20 Jan 2023 17:23:27 +0000 [thread overview]
Message-ID: <bug-108435-4-4JBAdgpbGN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108435-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108435
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|fortran |middle-end
CC| |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Possibly dup of PR107424 or at least related to that.
I don't think so. In any case, it shows also up for C
if one uses the nested-functions extension:
int
main ()
{
int i, j;
void bar()
{
#pragma omp for simd collapse(2)
for (i = 1; i <= 16; i++)
for (j = 1; j <= 16; j++) /* Note: *no* non-rectangular loop nest. */
;
}
bar ();
return 0;
}
(I get an ICE since GCC 8 and none with GCC 7; thus, I might be a regression,
but I have not checked in depth.)
next prev parent reply other threads:[~2023-01-20 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 17:47 [Bug fortran/108435] New: [13 Regression] ICE in as_a, at is-a.h:242 gscfq@t-online.de
2023-01-18 8:48 ` [Bug fortran/108435] [13 Regression] ICE in as_a, at is-a.h:242 since r13-142-g705bcedf6eae2d7c marxin at gcc dot gnu.org
2023-01-18 8:58 ` rguenth at gcc dot gnu.org
2023-01-19 12:33 ` jakub at gcc dot gnu.org
2023-01-20 17:23 ` burnus at gcc dot gnu.org [this message]
2023-02-01 14:24 ` [Bug middle-end/108435] " jakub at gcc dot gnu.org
2023-02-01 15:29 ` jakub at gcc dot gnu.org
2023-02-02 8:59 ` cvs-commit at gcc dot gnu.org
2023-02-03 13:57 ` jakub at gcc dot gnu.org
2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org
2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org
2023-05-03 15:21 ` cvs-commit 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-108435-4-4JBAdgpbGN@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).