From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5F538385482D; Wed, 8 Mar 2023 05:11:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5F538385482D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678252266; bh=Ai1IAfLzADZLI49oxna8QmOYm8V2Fa0A4r8PhzdA5Ig=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XIYDrp8z1A9OvTLJwfRsPcWcSACmboniyHeqWiiFYiBqZ9mEpf32JbEONnpLUpVZw VLeg9qRcq88F70+8xTv+3XoKKOVbqqDZHpEQzKlGOlibbeboc3cMybKbE5O3UMWw0B 7/o5XlvV/rqP204yOs29kVp7fi8PieLWUI0lfCao= From: "ishikawa at yk dot rim.or.jp" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyB0cmVlLW9wdGltaXphdGlvbi8xMDkwNDFdIEJvZ3VzIGNv?= =?UTF-8?B?bXBpbGUgdGltZSBjaGVjayBieSBfX2J1aWx0aW5fbWVtc2V0PyBlcnJvcjog?= =?UTF-8?B?4oCYX19idWlsdGluX21lbXNldOKAmSB3cml0aW5nIDQgYnl0ZXMgaW50byBh?= =?UTF-8?B?IHJlZ2lvbiBvZiBzaXplIDAgb3ZlcmZsb3dzIHRoZSBkZXN0aW5hdGlvbiBb?= =?UTF-8?B?LVdlcnJvcj1zdHJpbmdvcC1vdmVyZmxvdz1d?= Date: Wed, 08 Mar 2023 05:11:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 11.3.0 X-Bugzilla-Keywords: diagnostic, needs-reduction X-Bugzilla-Severity: normal X-Bugzilla-Who: ishikawa at yk dot rim.or.jp 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: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109041 --- Comment #4 from ishikawa,chiaki --- Right, when I replaced gcc-11 with gcc-12 in my script, I got the following warnings. One of them was there before, the other is new. /tmp/sqlite3-preprocessed-2.c: In function =E2=80=98posixUnlock=E2=80=99: /tmp/sqlite3-preprocessed-2.c:22632:42: error: self-comparison always evalu= ates to true [-Werror=3Dtautological-compare] 22632 | sqlite3PendingByte+1=3D=3D(sqlite3PendingByte+= 1) | ^~ /tmp/sqlite3-preprocessed-2.c: In function =E2=80=98vtabCallConstructor=E2= =80=99: /tmp/sqlite3-preprocessed-2.c:121095:4: error: the comparison will always evaluate as =E2=80=98true=E2=80=99 for the address of =E2=80=98pVtabCtx=E2= =80=99 will never be NULL [-Werror=3Daddress] 121095 | ) ? (void) (0) : __assert_fail ( | ^ /tmp/sqlite3-preprocessed-2.c:5226:12: note: =E2=80=98pVtabCtx=E2=80=99 dec= lared here 5226 | VtabCtx *pVtabCtx; | ^~~~~~~~ cc1: all warnings being treated as errors The latter one is a new one. Not sure why it was not triggered with gcc-11. Anyway, actually, I have found out that there is a runtime assertion trigge= red by thunderbird mail client when it is compiled with gcc-12, and not with gcc-10|gcc-11. So, I wanted to check the source code as much as possible with -Werror befo= re I dive into runtime code generation issues. "-Werror" signals so many dubious constructs, and it has been an uphill bat= tle to make the code compile. I found a missing "break" statement (implicit fallthrough), and strange size check (3rd argument to strncpy) already, but I am close to being able to compile mozilla source tree with more compile time check right now. Thank you again for making advanced compiler available free of charge.=