From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8CE043858D20; Fri, 3 Feb 2023 17:33:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8CE043858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675445584; bh=Ao3+C1pm3yFGfaJ48+bwYZrPCy8e/XdmvhyCUy3BLBw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kEG3xVEv/AEyWVZxoPJM7Vq+DpH3L/zrmOjyp7KlhNLx8h1cfCh+WtFCeq4PSjd4e qHD4DfotZLArVttdvCqKyuJrCHVib3QCWv0jzKMBGBumv9hJeN3j7BUsFdAoR532kX n0mcMgN3wrpQD1TUrhH4nAkQ1LzW+uyisUtS43Bc= From: "jdx at o2 dot pl" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/108644] Format string warnings related to longs under MigW-W64/MSYS2 on Windows 10 Date: Fri, 03 Feb 2023 17:33:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: internal-improvement X-Bugzilla-Severity: normal X-Bugzilla-Who: jdx at o2 dot pl 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=3D108644 --- Comment #5 from Jan Dubiec --- Andrew, as per your wish, preprocessed lto-plugin\lto-plugin.c is in the attachment. It was produced using the following command: gcc -DHAVE_CONFIG_H -I. -I../../../gcc/lto-plugin -I../../../gcc/lto-plugin/../include -DHAVE_CONFIG_H -Wall -DBASE_VERSION=3D\"13.0.1\" -E -g3 -O2 ../../../gcc/lto-plugin/lto-plugin.c= =20 -DDLL_EXPORT -DPIC -o lto-plugin-preprocessed.c Regarding gcc/ira-conflicts.cc, I think you are probably right, parentheses should fix the issue. But I am not able to understand (without looking into docs) how without the parentheses the expressions are promoted to unsigned = long long int instead of just long int. And why the warning does not appear on Linux. Regarding gcc/config/h8300/h8300.cc, I will file a separate report soon.=