public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/99694] [9/10 Regression] gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os since r9-7156-g33579b59aaf02eb7
Date: Mon, 22 Mar 2021 13:38:34 +0000 [thread overview]
Message-ID: <bug-99694-4-O26w4dj0vg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99694-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99694
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/10/11 Regression] gcc: |[9/10 Regression] gcc:
|fatal error: Killed signal |fatal error: Killed signal
|terminated program cc1 |terminated program cc1
|under -O2 to -Os since |under -O2 to -Os since
|r9-7156-g33579b59aaf02eb7 |r9-7156-g33579b59aaf02eb7
Known to fail| |10.2.0
Known to work| |11.0
Priority|P3 |P2
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar.
next prev parent reply other threads:[~2021-03-22 13:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 13:48 [Bug c/99694] New: gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os haoxintu at gmail dot com
2021-03-22 8:14 ` [Bug middle-end/99694] [9/10/11 Regression] gcc: fatal error: Killed signal terminated program cc1 under -O2 to -Os since r9-7156-g33579b59aaf02eb7 marxin at gcc dot gnu.org
2021-03-22 8:32 ` jakub at gcc dot gnu.org
2021-03-22 9:05 ` rguenth at gcc dot gnu.org
2021-03-22 13:37 ` cvs-commit at gcc dot gnu.org
2021-03-22 13:38 ` rguenth at gcc dot gnu.org [this message]
2021-03-24 14:26 ` [Bug middle-end/99694] [9/10 " cvs-commit at gcc dot gnu.org
2021-03-28 3:27 ` [Bug middle-end/99694] [9 " haoxintu at gmail dot com
2021-03-30 7:31 ` marxin at gcc dot gnu.org
2021-04-12 11:23 ` cvs-commit at gcc dot gnu.org
2021-04-12 11:24 ` rguenth at gcc dot gnu.org
2021-08-04 8:31 ` haoxintu at gmail dot com
2021-08-04 8:45 ` marxin at gcc dot gnu.org
2021-08-04 8:50 ` haoxintu at gmail dot com
2021-08-04 11:37 ` rguenth at gcc dot gnu.org
2021-08-04 11:51 ` jakub at gcc dot gnu.org
2021-08-04 12:42 ` marxin at gcc dot gnu.org
2021-08-04 13:19 ` haoxintu 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-99694-4-O26w4dj0vg@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).