public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107997] [13 Regression] r13-4389-gfd8dd6c0384969 probably uncovered an issue building the Linux kernel
Date: Thu, 08 Dec 2022 17:41:18 +0000 [thread overview]
Message-ID: <bug-107997-4-Jh9CJ2sG3q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107997-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107997
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jan-Benedict Glaw from comment #0)
> I'll add the preprocessed sources.
Could you please? Without it there isn't much that can be done.
next prev parent reply other threads:[~2022-12-08 17:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 22:24 [Bug regression/107997] New: fd8dd6c03849691 " jbglaw@lug-owl.de
2022-12-07 0:08 ` [Bug tree-optimization/107997] [13 Regression] " pinskia at gcc dot gnu.org
2022-12-08 17:41 ` jakub at gcc dot gnu.org [this message]
2022-12-08 18:07 ` [Bug tree-optimization/107997] [13 Regression] r13-4389-gfd8dd6c0384969 " jbglaw@lug-owl.de
2022-12-08 18:47 ` jbglaw@lug-owl.de
2022-12-08 18:47 ` jbglaw@lug-owl.de
2022-12-08 18:55 ` jakub at gcc dot gnu.org
2022-12-08 19:18 ` jakub at gcc dot gnu.org
2022-12-08 19:22 ` [Bug tree-optimization/107997] [10/11/12/13 " pinskia at gcc dot gnu.org
2022-12-08 19:50 ` jakub at gcc dot gnu.org
2022-12-09 13:49 ` jakub at gcc dot gnu.org
2022-12-09 18:27 ` jbglaw@lug-owl.de
2022-12-10 15:51 ` cvs-commit at gcc dot gnu.org
2022-12-14 10:33 ` jbglaw@lug-owl.de
2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org
2023-02-10 17:58 ` jakub at gcc dot gnu.org
2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org
2023-05-03 9:33 ` jakub at gcc dot gnu.org
2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org
2023-05-04 7:22 ` jakub 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-107997-4-Jh9CJ2sG3q@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).