From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 573AA388F057; Mon, 11 May 2020 16:25:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 573AA388F057 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1589214350; bh=JHBgxi5serb8/3+Ieq7C+a86/8N7ANlTXsnJRS4h3CE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=v+kmyE9FMSK7VlKvqvF3dS/wY7QZaw14DKo+JzeJdVMfAkoNatYp1Z99HdulbJxZk 2P7B5Obcu2loTTJxHETd6LGnkvzS9FlwjA8uHhXnG8AzXVszireauksvNbPwImQFdK HIKzAuv+p2qWPyOPXTDEpMmM3GmX3kCiEjGwI5as= From: "dmalcolm at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/95007] RFE: -fanalyzer should complain about writes to string literals Date: Mon, 11 May 2020 16:25:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: dmalcolm at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2020 16:25:50 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95007 --- Comment #2 from David Malcolm --- I guess I'm thinking about the case where a string literal has been exposed= as a non-const "char *": the RFE here is for -fanalyzer to be able to detect i= f we ever write to such a string (with interprocedural analysis etc etc).=