From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 20A8F3858C56; Sun, 21 Jan 2024 08:36:12 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 20A8F3858C56
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705826173;
	bh=/ZTLHNrB64Iarcng6Iz4m6H+AvTFNQvOVY3CnumjJBE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=YcIomi4AnZtK9EirGp5kUnTCJ+Nog24qwe7mc95ikGFh4+GJdADihVH0w4PqxbZWt
	 eczlGqHmecIfbEnEpKsH7fE19evoHFFLI/SYbuQ/dR5bQr8EKpNTkjUyqE8svBAT1u
	 96GEy4beQ6msNuk/onJCncshD0FeEAErbrHWg4EA=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113528] gcc-13 meets PVS-studio
Date: Sun, 21 Jan 2024 08:36:06 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113528-4-8yr24yYgSl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113528-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113528-4@http.gcc.gnu.org/bugzilla/>
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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> Fragment N4

Is NOT an issue, based on all of the uses of add_char, the character is tes=
ted
before adding it ...

And there 256 can hold all values of signed char.

>Fragment N5

Is just a small codiing style issue and actually will be optimized directly=
 to
the same thing really in this case as ' ' and '+' test bit will be in the s=
ame
word (the second word/element).


>Fragment N7

Not a bug, was done on purpose, see r5-958-ga33ad58be16a52 (PR 61242 and
https://gcc.gnu.org/pipermail/gcc-patches/2014-May/389815.html).

> Fragment N8

This code is software generated and the length is 0 in the GTY marker:
  ctf_dvdef_t ** GTY ((length ("0"))) ctfc_vars_list;

So not a bug.

> Fragment N9

Looks to be a way to avoid a goto, maybe now we could use a lamdba instead.=
 So
just a coding style issue.


I have not looked into the other ones yet.=