public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "s_gccbugzilla at nedprod dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112339] ICE with clang::no_sanitize and -fsanitize=
Date: Wed, 08 Nov 2023 22:32:27 +0000	[thread overview]
Message-ID: <bug-112339-4-44UoYra07B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112339-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112339

--- Comment #3 from Niall Douglas <s_gccbugzilla at nedprod dot com> ---
Thanks for the patch. I've sent it on to the originator of the bug, if they
confirm it fixes their issue to me I'll let you know.

  parent reply	other threads:[~2023-11-08 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 18:37 [Bug c++/112339] New: ICE with namespaced attribute on function s_gccbugzilla at nedprod dot com
2023-11-01 18:45 ` [Bug sanitizer/112339] ICE with clang::no_sanitize and -fsanitize= pinskia at gcc dot gnu.org
2023-11-02  9:45 ` [Bug c/112339] " jakub at gcc dot gnu.org
2023-11-08 22:32 ` s_gccbugzilla at nedprod dot com [this message]
2023-11-09  8:07 ` cvs-commit at gcc dot gnu.org
2023-12-05 16:32 ` cvs-commit at gcc dot gnu.org
2023-12-16  0:37 ` cvs-commit at gcc dot gnu.org
2023-12-16  8:46 ` 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-112339-4-44UoYra07B@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).