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 sanitizer/115172] Invalid -fsanitize=bool sanitization of variable from named address space
Date: Tue, 21 May 2024 21:08:06 +0000 [thread overview]
Message-ID: <bug-115172-4-8JYA1ZMfKk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115172-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115172
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Fedor Pchelkin from comment #6)
> (In reply to Uroš Bizjak from comment #5)
> > (In reply to Jakub Jelinek from comment #4)
> > > Created attachment 58261 [details]
> > > gcc15-pr115172.patch
> > >
> > > Full untested patch.
> >
> > I can confirm that this patch fixes boot for the kernel config from
> > PR115172#43.
>
> Yep. I may confirm, too. Thanks for the prompt fix!
>
> If all goes well, is it expected to land in 14.2 and 13.4?
If it is approved yes. 14.2 is expected likely in July this year, but 13.4
roughly in a year from now, as it just missed 13.3 (released today).
next prev parent reply other threads:[~2024-05-21 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 9:33 [Bug sanitizer/115172] New: " ubizjak at gmail dot com
2024-05-21 10:05 ` [Bug sanitizer/115172] " jakub at gcc dot gnu.org
2024-05-21 10:16 ` jakub at gcc dot gnu.org
2024-05-21 10:20 ` ubizjak at gmail dot com
2024-05-21 10:35 ` jakub at gcc dot gnu.org
2024-05-21 14:21 ` ubizjak at gmail dot com
2024-05-21 17:19 ` pchelkin at ispras dot ru
2024-05-21 21:08 ` jakub at gcc dot gnu.org [this message]
2024-05-22 7:13 ` cvs-commit at gcc dot gnu.org
2024-05-22 7:19 ` cvs-commit at gcc dot gnu.org
2024-05-22 7:35 ` cvs-commit at gcc dot gnu.org
2024-05-22 11:11 ` jakub at gcc dot gnu.org
2024-05-28 17:09 ` cvs-commit at gcc dot gnu.org
2024-05-28 17:09 ` cvs-commit at gcc dot gnu.org
2024-05-28 17:11 ` ubizjak 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-115172-4-8JYA1ZMfKk@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).