9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go tip build fails
Date: Wed,  1 May 2013 13:46:03 -0700	[thread overview]
Message-ID: <CAKzdPgxdjQA9x4ZzH3h7J6jkoePkv+0fJNYPjpEv=L+ABxDKuw@mail.gmail.com> (raw)
In-Reply-To: <02C52704-4155-474C-A722-45B2EC877927@gmail.com>

The patch was not abandoned; that message was a codereview glitch.
It's checked in.

We need to find where the bogus relocation is coming from. It *is*
bogus, but the error catching it is new. To make progress, feel free
to comment out the code that prints the error. I'm pretty sure you'll
be fine. But I would like to understand where the bad relocation value
is coming from. It's caused by something like a -4 becoming
0xFFFFFFFC, which doesn't matter when everything's 32 bits but is
caught by the error checking code that's using 64 bits.

-rob



  parent reply	other threads:[~2013-05-01 20:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 17:55 Skip Tavakkolian
2013-05-01 18:11 ` Rob Pike
2013-05-01 18:20   ` Jacob Todd
2013-05-01 18:31   ` Skip Tavakkolian
2013-05-01 18:54     ` Rob Pike
2013-05-01 19:14       ` Skip Tavakkolian
2013-05-01 19:25         ` Skip Tavakkolian
2013-05-01 19:59           ` Matthew Veety
2013-05-01 20:46             ` Russ Cox
2013-05-01 20:49               ` Jacob Todd
2013-05-01 20:58               ` Skip Tavakkolian
2013-05-01 21:32                 ` Rob Pike
2013-05-01 20:46             ` Rob Pike [this message]
2013-05-01 19:18       ` David du Colombier
2013-05-01 18:30 ` David du Colombier
2013-05-01 18:56   ` Skip Tavakkolian
2013-05-01 22:41 ` Rob Pike
2013-05-01 18:26 sl

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='CAKzdPgxdjQA9x4ZzH3h7J6jkoePkv+0fJNYPjpEv=L+ABxDKuw@mail.gmail.com' \
    --to=robpike@gmail.com \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).