public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110148] New: TSVC s242 regression between g:c0df96b3cda5738afbba3a65bb054183c5cd5530 and g:e4c986fde56a6248f8fbe6cf0704e1da34b055d8 Date: Tue, 06 Jun 2023 20:33:19 +0000 [thread overview] Message-ID: <bug-110148-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110148 Bug ID: 110148 Summary: TSVC s242 regression between g:c0df96b3cda5738afbba3a65bb054183c5cd5530 and g:e4c986fde56a6248f8fbe6cf0704e1da34b055d8 Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: hubicka at gcc dot gnu.org Target Milestone: --- Seen here: https://lnt.opensuse.org/db_default/v4/CPP/graph?plot.0=171.854.0 (benzen) https://lnt.opensuse.org/db_default/v4/CPP/graph?plot.0=463.854.0 (helene) https://lnt.opensuse.org/db_default/v4/CPP/graph?plot.0=283.854.0 (lntzen3) So it seems to affect both intel (Helene) and zens TSVC/s1244 is also regressing same day but only on zens
next reply other threads:[~2023-06-06 20:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-06 20:33 hubicka at gcc dot gnu.org [this message] 2023-06-06 21:02 ` [Bug middle-end/110148] " pinskia at gcc dot gnu.org 2023-06-09 6:36 ` [Bug middle-end/110148] [14 Regression] " rguenth at gcc dot gnu.org 2023-06-09 11:11 ` lili.cui at intel dot com 2023-06-25 5:56 ` lili.cui at intel dot com 2023-06-25 20:01 ` hubicka at gcc dot gnu.org 2023-06-29 9:31 ` cvs-commit at gcc dot gnu.org 2023-09-23 10:32 ` jamborm at gcc dot gnu.org 2023-09-26 1:55 ` lili.cui at intel dot com 2023-09-26 15:04 ` jamborm 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-110148-4@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: linkBe 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).