public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "avieira at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
Date: Mon, 08 Feb 2021 16:08:56 +0000 [thread overview]
Message-ID: <bug-26163-4-3nw5piVbUv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 98974, which changed state.
Bug 98974 Summary: [11 Regression] ICE in vectorizable_condition after STMT_VINFO_VEC_STMTS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98974
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
next prev parent reply other threads:[~2021-02-08 16:08 UTC|newest]
Thread overview: 154+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-26163-4@http.gcc.gnu.org/bugzilla/>
2014-12-01 5:12 ` [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k " pinskia at gcc dot gnu.org
2014-12-01 5:18 ` pinskia at gcc dot gnu.org
2014-12-01 5:20 ` pinskia at gcc dot gnu.org
2020-03-20 15:33 ` [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k " marxin at gcc dot gnu.org
2020-03-20 15:34 ` marxin at gcc dot gnu.org
2020-03-27 20:43 ` jamborm at gcc dot gnu.org
2020-04-02 14:37 ` jamborm at gcc dot gnu.org
2020-04-02 14:40 ` jakub at gcc dot gnu.org
2020-04-03 11:50 ` linkw at gcc dot gnu.org
2020-04-09 7:50 ` rguenth at gcc dot gnu.org
2020-04-14 9:29 ` jakub at gcc dot gnu.org
2020-04-24 22:25 ` jakub at gcc dot gnu.org
2020-04-29 8:16 ` tkoenig at gcc dot gnu.org
2020-05-05 10:35 ` rguenth at gcc dot gnu.org
2020-05-12 0:42 ` luoxhu at gcc dot gnu.org
2020-05-18 18:54 ` anlauf at gcc dot gnu.org
2020-05-21 18:17 ` ubizjak at gmail dot com
2020-05-27 12:00 ` marxin at gcc dot gnu.org
2020-05-29 9:03 ` rguenth at gcc dot gnu.org
2020-06-16 7:31 ` kyukhin at gcc dot gnu.org
2020-06-16 7:32 ` kyukhin at gcc dot gnu.org
2020-06-24 11:00 ` rguenth at gcc dot gnu.org
2020-07-09 11:47 ` rguenth at gcc dot gnu.org
2020-07-09 17:54 ` rguenth at gcc dot gnu.org
2020-07-21 10:03 ` rsandifo at gcc dot gnu.org
2020-09-21 14:54 ` rguenth at gcc dot gnu.org
2020-10-09 9:28 ` rguenth at gcc dot gnu.org
2020-10-09 10:28 ` marxin at gcc dot gnu.org
2020-10-09 10:28 ` marxin at gcc dot gnu.org
2020-10-16 12:04 ` marxin at gcc dot gnu.org
2020-11-09 13:58 ` rguenth at gcc dot gnu.org
2020-11-16 9:27 ` rguenth at gcc dot gnu.org
2020-12-01 10:47 ` jamborm at gcc dot gnu.org
2020-12-07 12:04 ` jamborm at gcc dot gnu.org
2020-12-14 15:22 ` tnfchris at gcc dot gnu.org
2020-12-14 20:35 ` msebor at gcc dot gnu.org
2020-12-16 14:49 ` marxin at gcc dot gnu.org
2020-12-23 23:50 ` msebor at gcc dot gnu.org
2021-02-03 8:10 ` tnfchris at gcc dot gnu.org
2021-02-04 16:47 ` jamborm at gcc dot gnu.org
2021-02-04 17:23 ` jamborm at gcc dot gnu.org
2021-02-04 17:43 ` jamborm at gcc dot gnu.org
2021-02-08 16:08 ` avieira at gcc dot gnu.org [this message]
2021-02-15 15:34 ` rsandifo at gcc dot gnu.org
2021-02-21 17:45 ` ubizjak at gmail dot com
2021-02-25 9:50 ` ubizjak at gmail dot com
2021-05-14 10:59 ` jakub at gcc dot gnu.org
2021-06-11 12:33 ` rguenth at gcc dot gnu.org
2021-06-18 21:46 ` amacleod at redhat dot com
2021-06-22 5:08 ` marxin at gcc dot gnu.org
2021-06-23 14:31 ` amacleod at redhat dot com
2021-07-12 10:19 ` rguenth at gcc dot gnu.org
2021-08-04 10:17 ` rguenth at gcc dot gnu.org
2021-08-30 12:05 ` rguenth at gcc dot gnu.org
2021-09-02 19:56 ` pinskia at gcc dot gnu.org
2021-09-07 18:53 ` pinskia at gcc dot gnu.org
2021-09-08 10:12 ` marxin at gcc dot gnu.org
2021-09-08 12:14 ` marxin at gcc dot gnu.org
2021-09-15 15:57 ` marxin at gcc dot gnu.org
2021-09-15 15:58 ` marxin at gcc dot gnu.org
2021-10-01 16:03 ` mkuvyrkov at gcc dot gnu.org
2021-10-13 13:48 ` marxin at gcc dot gnu.org
2021-10-19 13:58 ` rsandifo at gcc dot gnu.org
2021-10-26 14:57 ` pinskia at gcc dot gnu.org
2021-11-02 13:33 ` tnfchris at gcc dot gnu.org
2021-11-03 8:11 ` marxin at gcc dot gnu.org
2021-11-06 15:36 ` aldyh at gcc dot gnu.org
2021-11-11 14:01 ` rguenth at gcc dot gnu.org
2021-11-12 13:56 ` rguenth at gcc dot gnu.org
2021-11-12 22:14 ` hubicka at gcc dot gnu.org
2021-11-13 23:50 ` hubicka at gcc dot gnu.org
2021-11-18 8:28 ` hubicka at gcc dot gnu.org
2021-11-19 11:47 ` aldyh at gcc dot gnu.org
2021-11-21 15:21 ` hubicka at gcc dot gnu.org
2021-11-28 18:56 ` hubicka at gcc dot gnu.org
2021-11-30 15:58 ` meissner at gcc dot gnu.org
2021-12-02 12:32 ` rguenth at gcc dot gnu.org
2021-12-03 11:28 ` hubicka at gcc dot gnu.org
2021-12-03 11:44 ` hubicka at gcc dot gnu.org
2021-12-06 15:17 ` rguenth at gcc dot gnu.org
2022-01-10 14:52 ` rsandifo at gcc dot gnu.org
2022-01-12 15:18 ` rguenth at gcc dot gnu.org
2022-01-18 14:15 ` rguenth at gcc dot gnu.org
2022-01-20 8:51 ` admin at levyhsu dot com
2022-02-18 7:51 ` rguenth at gcc dot gnu.org
2022-02-22 8:01 ` rguenth at gcc dot gnu.org
2022-03-08 15:01 ` rguenth at gcc dot gnu.org
2022-03-11 14:04 ` rguenth at gcc dot gnu.org
2022-03-11 14:05 ` rguenth at gcc dot gnu.org
2022-03-23 8:51 ` rguenth at gcc dot gnu.org
2022-05-06 11:37 ` rguenth at gcc dot gnu.org
2022-05-20 3:56 ` crazylht at gmail dot com
2022-05-24 16:12 ` vineet.gupta at linux dot dev
2022-07-26 12:42 ` rguenth at gcc dot gnu.org
2022-07-26 13:27 ` rguenth at gcc dot gnu.org
2022-07-27 1:18 ` lili.cui at intel dot com
2022-08-02 11:03 ` mkuvyrkov at gcc dot gnu.org
2022-08-12 11:38 ` rguenth at gcc dot gnu.org
2022-09-02 13:01 ` rsandifo at gcc dot gnu.org
2022-09-22 6:47 ` rguenth at gcc dot gnu.org
2022-09-26 13:00 ` redi at gcc dot gnu.org
2022-10-17 13:11 ` rguenth at gcc dot gnu.org
2022-10-18 8:41 ` rguenth at gcc dot gnu.org
2022-10-19 10:11 ` rguenth at gcc dot gnu.org
2022-10-27 14:45 ` marxin at gcc dot gnu.org
2022-11-11 9:32 ` tnfchris at gcc dot gnu.org
2022-12-01 13:13 ` wilco at gcc dot gnu.org
2023-01-18 13:40 ` jamborm at gcc dot gnu.org
2023-01-18 15:45 ` jamborm at gcc dot gnu.org
2023-01-18 16:57 ` jamborm at gcc dot gnu.org
2023-01-18 17:17 ` jamborm at gcc dot gnu.org
2023-01-18 17:41 ` jamborm at gcc dot gnu.org
2023-01-31 11:26 ` jamborm at gcc dot gnu.org
2023-02-01 9:31 ` rguenth at gcc dot gnu.org
2023-03-22 16:06 ` jamborm at gcc dot gnu.org
2023-03-30 7:52 ` marxin at gcc dot gnu.org
2023-05-08 7:39 ` pinskia at gcc dot gnu.org
2023-05-12 6:01 ` pinskia at gcc dot gnu.org
2023-05-12 16:45 ` ubizjak at gmail dot com
2023-05-19 7:44 ` pinskia at gcc dot gnu.org
2023-06-02 4:53 ` pinskia at gcc dot gnu.org
2023-06-07 7:02 ` sjames at gcc dot gnu.org
2023-06-20 10:35 ` linkw at gcc dot gnu.org
2023-07-26 13:28 ` rguenth at gcc dot gnu.org
2023-07-31 7:39 ` hubicka at gcc dot gnu.org
2023-08-04 17:26 ` pinskia at gcc dot gnu.org
2023-08-15 13:03 ` hubicka at gcc dot gnu.org
2023-08-29 9:28 ` rguenth at gcc dot gnu.org
2023-10-04 11:38 ` fkastl at suse dot cz
2023-10-30 17:41 ` jamborm at gcc dot gnu.org
2023-11-15 18:12 ` jamborm at gcc dot gnu.org
2023-11-21 13:29 ` tnfchris at gcc dot gnu.org
2023-11-23 9:41 ` fkastl at suse dot cz
2023-12-15 19:54 ` pinskia at gcc dot gnu.org
2024-01-05 13:18 ` tnfchris at gcc dot gnu.org
2024-01-12 12:09 ` jamborm at gcc dot gnu.org
2024-01-12 15:36 ` tnfchris at gcc dot gnu.org
2024-01-19 3:23 ` vineetg at gcc dot gnu.org
2024-01-24 16:07 ` law at gcc dot gnu.org
2024-01-24 18:29 ` pinskia at gcc dot gnu.org
2024-02-03 22:04 ` sjames at gcc dot gnu.org
2024-02-13 10:13 ` pheeck at gcc dot gnu.org
2024-02-23 14:17 ` rsandifo at gcc dot gnu.org
2024-02-23 14:17 ` rsandifo at gcc dot gnu.org
2024-03-08 10:08 ` xry111 at gcc dot gnu.org
2024-03-08 13:41 ` rguenth at gcc dot gnu.org
2024-03-08 14:03 ` rguenth at gcc dot gnu.org
2024-03-12 12:48 ` pheeck at gcc dot gnu.org
2024-03-19 12:15 ` rguenth at gcc dot gnu.org
2024-03-21 9:22 ` pheeck at gcc dot gnu.org
2024-03-22 12:47 ` law at gcc dot gnu.org
2024-03-28 7:04 ` rguenth at gcc dot gnu.org
2024-03-28 12:12 ` pheeck at gcc dot gnu.org
2024-04-15 13:29 ` 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-26163-4-3nw5piVbUv@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).