public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "colomar.6.4.3 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/109335] -Wanalyzer-malloc-leak false positives and false negatives Date: Fri, 05 May 2023 11:13:25 +0000 [thread overview] Message-ID: <bug-109335-4-2UBpOQn4Wd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109335-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109335 Alejandro Colomar <colomar.6.4.3 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |colomar.6.4.3 at gmail dot com --- Comment #1 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> --- I can still reproduce it with GCC-13 and glibc 2.36: $ cat glibc.c #include <stdio.h> int main(void) { printf("glibc version: %d.%d\n", __GLIBC__, __GLIBC_MINOR__); } $ gcc-13 -Wall -Wextra glibc.c $ ./a.out glibc version: 2.36 $ gcc-13 --version gcc-13 (Debian 13.1.0-1) 13.1.0 Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next prev parent reply other threads:[~2023-05-05 11:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-29 14:03 [Bug analyzer/109335] New: " colomar.6.4.3 at gmail dot com 2023-05-05 11:13 ` colomar.6.4.3 at gmail dot com [this message] 2024-05-15 7:16 ` [Bug analyzer/109335] " alx at kernel dot org 2024-05-15 7:42 ` alx at kernel dot org 2024-05-15 13:58 ` alx at kernel dot 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-109335-4-2UBpOQn4Wd@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).