public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-111367-4-8djTsoHlMR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111367-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111367

--- 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 them
> to use prefixed instructions.
> 
> 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.

  parent reply	other threads:[~2023-09-21  6:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 10:01 [Bug target/111367] New: " malat at debian dot org
2023-09-11 10:02 ` [Bug target/111367] " malat at debian dot org
2023-09-11 10:02 ` malat at debian dot org
2023-09-11 10:03 ` malat at debian dot org
2023-09-12  9:35 ` linkw at gcc dot gnu.org
2023-09-15  7:44 ` linkw at gcc dot gnu.org
2023-09-18  2:39 ` linkw at gcc dot gnu.org
2023-09-18  2:42 ` linkw at gcc dot gnu.org
2023-09-18 17:03 ` bergner at gcc dot gnu.org
2023-09-18 17:56 ` segher at gcc dot gnu.org
2023-09-19  2:15 ` linkw at gcc dot gnu.org
2023-09-19 15:19 ` segher at gcc dot gnu.org
2023-09-19 16:31 ` gnu@the-meissners.org
2023-09-21  6:57 ` linkw at gcc dot gnu.org [this message]
2023-10-12  5:06 ` cvs-commit at gcc dot gnu.org
2023-10-23  5:32 ` cvs-commit at gcc dot gnu.org
2023-10-23  5:35 ` cvs-commit at gcc dot gnu.org
2023-10-23  5:38 ` cvs-commit at gcc dot gnu.org
2023-10-23  6:22 ` linkw at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-111367-4-8djTsoHlMR@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).