From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A429738582AB; Wed, 23 Nov 2022 06:10:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A429738582AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669183832; bh=S81THSKc2ElJ10I8HwbM7+BCuPlLJoEPRTWYjTRCZMs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SjbHt2EKBQiAky0s9DqN6PNbAa+8+CHPzKOfqOc6sHCu+XJrnZtoUlavy8lj1Lh1q 0cMmNHBjUhWk4mbp7SGMGo+gcAxCWEg9TuavCYW2HEU9wJfZMVaolUJq8oWIb5eC1h /nIAXpI1lgc32hEMflfr/7XThtGvFckkngadwyRo= From: "adam.f.badura at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107802] -Wsuggest-attribute=format ignores [[gnu::format(...)]] Date: Wed, 23 Nov 2022 06:10:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: unknown X-Bugzilla-Keywords: diagnostic, ice-checking, ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: adam.f.badura at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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=3D107802 --- Comment #3 from Adam Badura --- Why is this marked as a duplicate of bug 98487? I have seen bug 98487 before reporting it. Furthermore, I experienced it while trying my code sample on = the trunk version to see if the problem still exists. However, since trunk version breaks completely with the same code it is not possible to determine if the problem reported here exists there or not. Aft= er preventing the compiler from crashing we may very well start to observe the problem reported here. Or is bug 98487 intended to solve the problem reported here as well along t= he way?=