public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "geoffreydgr at icloud dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/109190] GCC Static Analyzer cannot handle the initialization of an array with a for loop
Date: Sat, 08 Apr 2023 14:44:24 +0000 [thread overview]
Message-ID: <bug-109190-4-G7a8HSTFxM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109190-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109190
--- Comment #3 from Geoffrey <geoffreydgr at icloud dot com> ---
(In reply to Xi Ruoyao from comment #2)
> With -O0 GCC does not attempt to analyze any loops. I doubt if "-O0
> -fanalyzer" really makes sense. Maybe we should just emit a warning when
> -fanalyzer is used with -O0.
Could you explain why GCC does not attempt to analyze any loops with -O0 ?
Because it depends some optimization passes to help handling loops?
next prev parent reply other threads:[~2023-04-08 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 8:57 [Bug analyzer/109190] New: " geoffreydgr at icloud dot com
2023-04-03 12:59 ` [Bug analyzer/109190] " geoffreydgr at icloud dot com
2023-04-03 13:39 ` xry111 at gcc dot gnu.org
2023-04-08 14:44 ` geoffreydgr at icloud dot com [this message]
2023-04-10 20:18 ` StevenSun2021 at hotmail dot com
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-109190-4-G7a8HSTFxM@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).