public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96377] [10/11 Regression] GCC 10.2/11 doesn't build Linux kernel anymore Date: Wed, 18 Nov 2020 16:56:38 +0000 [thread overview] Message-ID: <bug-96377-4-m6ttAW6Wed@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96377-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96377 rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |ASSIGNED --- Comment #15 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- The original problem is fixed for GCC 10 and the kernel manifestation is fixed for trunk. We still need to deal with the testcase in comment 8, which is another manifestation that affects trunk only.
next prev parent reply other threads:[~2020-11-18 16:56 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-29 16:04 [Bug target/96377] New: " jakub at gcc dot gnu.org 2020-07-29 16:04 ` [Bug target/96377] " jakub at gcc dot gnu.org 2020-07-29 16:18 ` jakub at gcc dot gnu.org 2020-07-29 16:40 ` jakub at gcc dot gnu.org 2020-07-29 16:48 ` jakub at gcc dot gnu.org 2020-07-29 17:40 ` rsandifo at gcc dot gnu.org 2020-07-30 14:06 ` rsandifo at gcc dot gnu.org 2020-07-30 14:09 ` rsandifo at gcc dot gnu.org 2020-07-30 15:41 ` jakub at gcc dot gnu.org 2020-07-30 15:58 ` rsandifo at gcc dot gnu.org 2020-07-30 17:08 ` rsandifo at gcc dot gnu.org 2020-07-30 19:55 ` joseph at codesourcery dot com 2020-08-01 11:42 ` cvs-commit at gcc dot gnu.org 2020-08-03 8:49 ` cvs-commit at gcc dot gnu.org 2020-09-10 17:21 ` rsandifo at gcc dot gnu.org 2020-11-18 14:33 ` jakub at gcc dot gnu.org 2020-11-18 16:56 ` rsandifo at gcc dot gnu.org [this message] 2021-01-27 9:28 ` 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-96377-4-m6ttAW6Wed@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).