public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "julia.koval at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/67552] [meta] x86 interrupt attribute
Date: Mon, 14 Sep 2015 09:26:00 -0000	[thread overview]
Message-ID: <bug-67552-4-awOhW9qDAw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67552-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Yulia Koval <julia.koval at intel dot com> ---
Sorry, I don't understand why we shouldn't preserve the red zone. The function
"foo", executing before the interrupt was called, used its red zone. If the
interrupt does not adjust the stack pointer, who control that "foo" function's
red zone would not be overwritten?


  parent reply	other threads:[~2015-09-14  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 15:40 [Bug other/67552] New: " hjl.tools at gmail dot com
2015-09-11 15:41 ` [Bug other/67552] " hjl.tools at gmail dot com
2015-09-11 15:46 ` hjl.tools at gmail dot com
2015-09-11 17:43 ` hjl.tools at gmail dot com
2015-09-11 17:44 ` hjl.tools at gmail dot com
2015-09-14  9:26 ` julia.koval at intel dot com [this message]
2015-09-14 11:25 ` hjl.tools at gmail dot com
2015-09-19 22:35 ` hjl.tools at gmail dot com
2015-09-19 22:35 ` hjl.tools at gmail dot com
2015-09-29 13:39 ` hjl.tools at gmail dot com
2015-10-05 17:30 ` hjl.tools at gmail dot com
2015-10-12 12:48 ` hjl.tools at gmail dot com

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-67552-4-awOhW9qDAw@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).