From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EB856385B52E; Wed, 15 Feb 2023 18:03:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EB856385B52E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1676484204; bh=dUpEJEMBUN1MwP524Tuf3thIFaOYi4Sd4j2Bvn9c98I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kPChz3Y49X1DBiGxH0bV3UnUeC13jydRwZkV/fiEw169siACT41whyTA6CyPKlTvy ADccG5piV9P+F9oLGOeXfLD0y6jXIN5Ny8lVh/DnBW8bvbnenHeXV/7uoea5NfIaid jC6/eaUVV0bPUMsI9mfQBcnfZIIHwP2jdHClg7+U= From: "andrew.cooper3 at citrix dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/108799] Improper deprecation diagnostic for rsp clobber Date: Wed, 15 Feb 2023 18:03:24 +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: unknown X-Bugzilla-Keywords: documentation, inline-asm X-Bugzilla-Severity: normal X-Bugzilla-Who: andrew.cooper3 at citrix dot com 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=3D108799 --- Comment #2 from Andrew Cooper --- Adding a memory clobber doesn't make any difference that I can see, and I'm= not aware of any reason why it ought to make a difference. I suppose that my real request here is to figure out what is the correct wa= y to indicate that the redzone is clobbered, and to document it.=