public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "torvald at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libitm/51855] New: improve calculation of stack bottom in libitm's undolog
Date: Fri, 13 Jan 2012 23:36:00 -0000	[thread overview]
Message-ID: <bug-51855-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51855

             Bug #: 51855
           Summary: improve calculation of stack bottom in libitm's
                    undolog
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: libitm
        AssignedTo: torvald@gcc.gnu.org
        ReportedBy: torvald@gcc.gnu.org
                CC: aldyh@gcc.gnu.org, rth@gcc.gnu.org


It would be good to improve how libitm calculates the bottom of the stack space
of the current thread.  It needs to do that to prevent rolling back
transactional writes to this space because this would corrupt the stack frames
of the transaction rollback functions.  For 4.7, we handle this with
__builtin_dwarf_cfa() and an additional buffer zone of 256 bytes to deal with
another __builtin_memcpy() call that we need during rollback and whose stack
frame size we can't measure at runtime.  For 4.8, we should think about
improving that, perhaps based on the existing boehm-gc code for this
(GC_get_stack_base() in os_dep.c).


             reply	other threads:[~2012-01-13 23:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 23:36 torvald at gcc dot gnu.org [this message]
2012-01-13 23:38 ` [Bug libitm/51855] " torvald at gcc dot gnu.org
2012-01-13 23:47 ` pinskia at gcc dot gnu.org
2012-01-13 23:53 ` torvald at gcc dot gnu.org
2013-03-22 14:45 ` jakub at gcc dot gnu.org
2013-05-31 11:01 ` jakub at gcc dot gnu.org
2013-10-16  9:51 ` jakub at gcc dot gnu.org
2015-06-22 14:25 ` rguenth 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-51855-4@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).