public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97969] [9/10/11 Regression][ARM/Thumb] Certain combo of codegen options leads to compilation infinite loop with growing memory use
Date: Wed, 25 Nov 2020 17:15:20 +0000 [thread overview]
Message-ID: <bug-97969-4-V0atQZ7vqZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97969-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97969
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vmakarov at gcc dot gnu.org
--- Comment #4 from ktkachov at gcc dot gnu.org ---
This seems to go into a bad loop somewhere in LRA.
next prev parent reply other threads:[~2020-11-25 17:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 15:22 [Bug c/97969] New: [ARM/Thumb] " pmiscml at gmail dot com
2020-11-24 15:24 ` [Bug c/97969] " pmiscml at gmail dot com
2020-11-24 15:33 ` pmiscml at gmail dot com
2020-11-24 15:43 ` [Bug c/97969] [9/10/11 Regression][ARM/Thumb] " ktkachov at gcc dot gnu.org
2020-11-25 8:17 ` [Bug target/97969] " rguenth at gcc dot gnu.org
2020-11-25 17:15 ` ktkachov at gcc dot gnu.org [this message]
2020-11-27 12:25 ` pmiscml at gmail dot com
2020-11-27 17:32 ` ktkachov at gcc dot gnu.org
2020-12-06 4:34 ` haoxintu at gmail dot com
2020-12-07 9:56 ` ktkachov at gcc dot gnu.org
2020-12-07 10:04 ` haoxintu at gmail dot com
2020-12-07 10:34 ` pmiscml at gmail dot com
2020-12-07 10:38 ` pmiscml at gmail dot com
2020-12-07 10:56 ` haoxintu at gmail dot com
2021-01-11 20:32 ` vmakarov at gcc dot gnu.org
2021-01-12 8:31 ` wirkus at gcc dot gnu.org
2021-01-12 15:11 ` vmakarov at gcc dot gnu.org
2021-01-12 15:12 ` vmakarov at gcc dot gnu.org
2021-01-12 15:38 ` wirkus at gcc dot gnu.org
2021-01-12 16:28 ` cvs-commit at gcc dot gnu.org
2021-01-13 17:24 ` pmiscml at gmail dot com
2021-01-15 10:02 ` wirkus at gcc dot gnu.org
2021-01-20 17:37 ` vmakarov at gcc dot gnu.org
2021-01-21 23:10 ` vmakarov at gcc dot gnu.org
2021-05-04 12:31 ` [Bug target/97969] [9/10/11/12 " rguenth at gcc dot gnu.org
2021-05-25 9:18 ` przemyslaw.wirkus at arm dot com
2021-05-25 9:39 ` rguenth at gcc dot gnu.org
2021-05-25 10:06 ` wirkus at gcc dot gnu.org
2021-06-01 8:19 ` [Bug target/97969] [9/10 " rguenth at gcc dot gnu.org
2021-06-02 22:26 ` cvs-commit at gcc dot gnu.org
2022-05-27 8:57 ` [Bug target/97969] [9 " rguenth 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-97969-4-V0atQZ7vqZ@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).