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/114956] [11/12/13 Regression] Segmentation fault with -fsanitize=address -fsanitize=null -O2 when attribute no_sanitize_address is enabled since r9-5742
Date: Tue, 07 May 2024 19:32:27 +0000	[thread overview]
Message-ID: <bug-114956-4-REhvQAqb7B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114956-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[11/12/13/14/15 Regression] |[11/12/13 Regression]
                   |Segmentation fault with     |Segmentation fault with
                   |-fsanitize=address          |-fsanitize=address
                   |-fsanitize=null -O2 when    |-fsanitize=null -O2 when
                   |attribute                   |attribute
                   |no_sanitize_address is      |no_sanitize_address is
                   |enabled since r9-5742       |enabled since r9-5742

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 14.2 and later for now.

  parent reply	other threads:[~2024-05-07 19:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  3:37 [Bug sanitizer/114956] New: Segmentation fault with -fsanitize=address -fsanitize=null -O2 when attribute no_sanitize_address is enabled iamanonymous.cs at gmail dot com
2024-05-06  7:21 ` [Bug sanitizer/114956] [11/12/13/14/15 regression] " sjames at gcc dot gnu.org
2024-05-06  8:04 ` [Bug sanitizer/114956] [11/12/13/14/15 Regression] Segmentation fault with -fsanitize=address -fsanitize=null -O2 when attribute no_sanitize_address is enabled since r9-5742 jakub at gcc dot gnu.org
2024-05-06  8:58 ` jakub at gcc dot gnu.org
2024-05-07 19:29 ` cvs-commit at gcc dot gnu.org
2024-05-07 19:31 ` cvs-commit at gcc dot gnu.org
2024-05-07 19:32 ` jakub at gcc dot gnu.org [this message]
2024-05-09  4:26 ` [Bug sanitizer/114956] [11/12/13 " cvs-commit at gcc dot gnu.org
2024-05-09  8:18 ` [Bug sanitizer/114956] [11/12 " jakub at gcc dot gnu.org
2024-06-11 10:38 ` cvs-commit at gcc dot gnu.org
2024-06-11 10:53 ` [Bug sanitizer/114956] [11 " jakub at gcc dot gnu.org
2024-06-20 13:23 ` cvs-commit at gcc dot gnu.org
2024-06-20 13:44 ` 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-114956-4-REhvQAqb7B@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).