public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/114956] [11/12/13/14/15 regression] Segmentation fault with -fsanitize=address -fsanitize=null -O2 when attribute no_sanitize_address is enabled Date: Mon, 06 May 2024 07:21:23 +0000 [thread overview] Message-ID: <bug-114956-4-sEmVyqGQXX@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 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Segmentation fault with |[11/12/13/14/15 regression] |-fsanitize=address |Segmentation fault with |-fsanitize=null -O2 when |-fsanitize=address |attribute |-fsanitize=null -O2 when |no_sanitize_address is |attribute |enabled |no_sanitize_address is | |enabled --- Comment #1 from Sam James <sjames at gcc dot gnu.org> --- testing on godbolt gives.. gcc 8.2: ``` <source>:2:37: warning: always_inline function might not be inlinable [-Wattributes] __attribute__((always_inline)) int *c() { ^ <source>: In function 'd': <source>:2:37: error: inlining failed in call to always_inline 'c': function attribute mismatch <source>:6:61: note: called from here __attribute__((no_sanitize_address)) static char d() { *a = c(); } ^~~ Compiler returned: 1 ``` gcc 8.3: ``` <source>:2:37: warning: always_inline function might not be inlinable [-Wattributes] __attribute__((always_inline)) int *c() { ^ during GIMPLE pass: sanopt <source>: In function 'd': <source>:6:50: internal compiler error: Segmentation fault __attribute__((no_sanitize_address)) static char d() { *a = c(); } ^ Please submit a full bug report, with preprocessed source if appropriate. See <https://gcc.gnu.org/bugs/> for instructions. Compiler returned: 1 ``` so a regression in that we ICE.
next prev parent reply other threads:[~2024-05-06 7:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-06 3:37 [Bug sanitizer/114956] New: " iamanonymous.cs at gmail dot com 2024-05-06 7:21 ` sjames at gcc dot gnu.org [this message] 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 ` [Bug sanitizer/114956] [11/12/13 " jakub at gcc dot gnu.org 2024-05-09 4:26 ` 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-sEmVyqGQXX@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).