public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "shaohua.li at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/109330] New: ASAN since GCC-9 missed a stack-use-after-scope at -O3
Date: Wed, 29 Mar 2023 08:18:46 +0000	[thread overview]
Message-ID: <bug-109330-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109330
           Summary: ASAN since GCC-9 missed a stack-use-after-scope at -O3
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: shaohua.li at inf dot ethz.ch
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

For the following code, ASAN at -O3 since GCC-9 missed the use-after-scope.
I checked the code and found that `*f=*g` and `return *f` were not optimized
away by the compiler.

Compiler explorer: https://godbolt.org/z/c96a6jWrY

% cat a.c
int a, c, d;
char b, e;
int main() {
  int *f = &a, *g = &c;
h:
  &g;
  for (; 0;)
    goto h;
  d = 0;
  for (; d <= 3; d++) {
    int i = *f;
    b && (e = 1);
    f = &i;
  }
  *f = *g;
  return *f;
}
% gcc-tk -O3 -fsanitize=address a.c && ./a.out
%
% gcc-8 -O3 -fsanitize=address a.c && ./a.out
================================================================
==1==ERROR: AddressSanitizer: stack-use-after-scope on address 0x7ffd6b6b94d0
at pc 0x0000004008e1 bp 0x7ffd6b6b94a0 sp 0x7ffd6b6b9498
WRITE of size 4 at 0x7ffd6b6b94d0 thread T0
    #0 0x4008e0 in main /a.c:15
...
%

             reply	other threads:[~2023-03-29  8:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  8:18 shaohua.li at inf dot ethz.ch [this message]
2023-03-29 12:46 ` [Bug sanitizer/109330] " marxin 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-109330-4@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).