From: Bryce McKinlay <bmckinlay@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
Hans Boehm <hans_boehm@hp.com>
Subject: Re: [boehm-gc] Use thr_stksegment to determine Solaris stack base
Date: Wed, 06 Mar 2013 14:30:00 -0000 [thread overview]
Message-ID: <CALUNu-rt71gpRMmhnO=KcTyESBXVreZSL=xJ6qkUn1MoC7fz9Q@mail.gmail.com> (raw)
In-Reply-To: <yddfw08bw8j.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
On Wed, Mar 6, 2013 at 11:31 AM, Rainer Orth
<ro@cebitec.uni-bielefeld.de> wrote:
> This patch fixes the failures by backporting the use of thr_stksegment
> from gc 7.2c.
>
> Bootstrapped without regressions on i386-pc-solaris2.{9,10,11} and
> sparc-sun-solaris2.{9,10,11}, fixes the i386-pc-solaris2.11 failures.
>
> Ok for mainline?
Yes, thanks. Though of course, we really ought to update the entire GC tree!
Bryce
prev parent reply other threads:[~2013-03-06 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 11:31 Rainer Orth
2013-03-06 14:30 ` Bryce McKinlay [this message]
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='CALUNu-rt71gpRMmhnO=KcTyESBXVreZSL=xJ6qkUn1MoC7fz9Q@mail.gmail.com' \
--to=bmckinlay@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hans_boehm@hp.com \
--cc=java-patches@gcc.gnu.org \
--cc=ro@cebitec.uni-bielefeld.de \
/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).