public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/60134] runtime_unmarkspan panics with "unaligned pointer"
Date: Wed, 12 Feb 2014 00:37:00 -0000	[thread overview]
Message-ID: <bug-60134-4-UMLVlGJFE2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60134-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Ian Lance Taylor from comment #1)
> I don't know which repository your git commit ID refers to.  The gofrontend
> uses Mercurial and GCC uses Subversion.

The git commit ID referenced is the official git which uses git-svn:
http://gcc.gnu.org/git/?p=gcc.git;a=commit;h=e63988cca99cbbf6e5c459379309fe3359fe7c09

> 
> I suspect this problem was fixed by revision 205940 in the GCC Subversion
> repository, committed 2013-12-12,
> http://gcc.gnu.org/ml/gcc-patches/2013-12/msg01202.html .
> 
> Do the sources you are building include that patch?



which corresponds to revision 205617 which is before the revision you said it
was fixed in.

Thanks,
Andrew Pinski


  parent reply	other threads:[~2014-02-12  0:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 12:39 [Bug go/60134] New: " vogt at linux dot vnet.ibm.com
2014-02-12  0:34 ` [Bug go/60134] " ian at airs dot com
2014-02-12  0:37 ` pinskia at gcc dot gnu.org [this message]
2014-02-12  1:10 ` ian at airs dot com
2014-02-12  7:26 ` vogt at linux dot vnet.ibm.com
2014-02-14 12:21 ` vogt at linux dot vnet.ibm.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-60134-4-UMLVlGJFE2@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).