public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/99489] [11 Regression] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()
Date: Thu, 11 Mar 2021 18:26:38 +0000 [thread overview]
Message-ID: <bug-99489-4-HN4YzJI5CG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99489-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489
David Binderman <dcb314 at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dcb314 at hotmail dot com
--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
I notice something similar:
drive_cache.cpp:477:6: internal compiler error: gimple check: expected
gimple_call(error_mark), have gimple_phi()
in gimple_call_fndecl, at gimple.h:3171
Reduced C++ code available on request.
next prev parent reply other threads:[~2021-03-11 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 16:29 [Bug tree-optimization/99489] New: " raj.khem at gmail dot com
2021-03-09 16:30 ` [Bug tree-optimization/99489] " raj.khem at gmail dot com
2021-03-09 18:00 ` [Bug tree-optimization/99489] [11 Regression] " msebor at gcc dot gnu.org
2021-03-09 19:29 ` marxin at gcc dot gnu.org
2021-03-09 19:40 ` marxin at gcc dot gnu.org
2021-03-09 19:43 ` marxin at gcc dot gnu.org
2021-03-09 19:59 ` msebor at gcc dot gnu.org
2021-03-09 22:09 ` msebor at gcc dot gnu.org
2021-03-11 18:26 ` dcb314 at hotmail dot com [this message]
2021-03-13 21:29 ` cvs-commit at gcc dot gnu.org
2021-03-13 21:30 ` msebor at gcc dot gnu.org
2021-03-13 23:39 ` raj.khem 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-99489-4-HN4YzJI5CG@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).