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 6FD6A3858C52; Thu, 21 Sep 2023 06:57:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6FD6A3858C52
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1695279450;
	bh=0T21gDUsnkPKPUOhF0BALc0PsQfCvuN/lv0Az7RaYZ0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=N7OKq4u6XjAmvglabWLESM8/wXeRRZYmcY518VJV7B5WJ0VnzaxT/NTBGMX1gK8wD
	 hxXSV3cDphmJ+Kyt+w8pXIJ7PJSlQHZJ6KVHxZfsaDjsCxFv3VIzvNeeJAo1s7cUPk
	 6f1pPWw4GCUh2khvZx/X8ocibNfKVZZX3bo41yhU=
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111367] Error: operand out of range (0x1391c is not
 between 0xffffffffffff8000 and 0x7fff)
Date: Thu, 21 Sep 2023 06:57:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-111367-4-8djTsoHlMR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111367-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111367-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=3D111367

--- Comment #13 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Michael Meissner from comment #12)
> Basically I did not consider the case.  IIRC, you only need the stack
> protect DI mode case if the stack is large enough (more than 32K).  I don=
't
> think 32-bit programs could have a large enough stack that would force th=
em
> to use prefixed instructions.
>=20
> But it should be simple enough to use the :P iterator to catch both SI and
> DI cases.

Thanks for the explanation. This reported test case has an array with 10000
long long type element, the corresponding stack size is 80080 bytes and the
canary word is put at +80060 which can leverage prefixed insn.=