public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Brooks Moses <bmoses@google.com>
To: Steve Ellcey <sellcey@mips.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, libc-ports@sourceware.org
Subject: Re: [patch, mips] Improved memset for MIPS
Date: Fri, 06 Sep 2013 18:57:00 -0000	[thread overview]
Message-ID: <CAOxa4KoxtrtaupLv5nyjccFyxhhSOFhfeFUcr9UCy-oS2tRtEA@mail.gmail.com> (raw)
In-Reply-To: <1378489387.5770.335.camel@ubuntu-sellcey>

On Fri, Sep 6, 2013 at 10:43 AM, Steve Ellcey <sellcey@mips.com> wrote:
> On Fri, 2013-09-06 at 16:59 +0000, Joseph S. Myers wrote:
>>> The "undefined reference to `__libc_global_ctors'" has just shown up
>>> again in a parallel build, but it seems to go away when I rebuild.  I am
>>> still trying to understand what is going on with this.
>
>> Since it seems to be about parallel builds and linkobj/libc.so, try with
>> Brooks's patch
>> <https://sourceware.org/ml/libc-alpha/2013-08/msg00597.html>?  (Which, if
>> it works OK on master for a while, should probably be backported to 2.18
>> branch.)

Joseph is correct that this is related -- that error message is
exactly the one we were getting that sent me on the path of debugging
the circular reference and writing that patch.  The compile
instruction that causes that error message is consistent with the
implicit rule that my patch fixes.

- Brooks

  reply	other threads:[~2013-09-06 18:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 17:06 Steve Ellcey 
2013-09-06  0:40 ` Mike Frysinger
2013-09-06 15:42   ` Steve Ellcey
2013-09-06  4:18 ` Carlos O'Donell
2013-09-06 16:03   ` Steve Ellcey
2013-09-06 17:12     ` Carlos O'Donell
2013-09-06 23:33       ` Steve Ellcey
2013-09-07  2:38         ` Carlos O'Donell
2013-09-10 20:31           ` Steve Ellcey
2013-09-10 21:01             ` Carlos O'Donell
2013-09-10 21:14               ` Steve Ellcey
2013-09-10 22:35                 ` Carlos O'Donell
2013-09-10 22:38                   ` Carlos O'Donell
2013-09-07  5:46         ` Andreas Schwab
2013-09-06 14:31 ` Joseph S. Myers
2013-09-06 15:58   ` Steve Ellcey
2013-09-06 16:09     ` Joseph S. Myers
2013-09-06 16:50       ` Steve Ellcey
2013-09-06 16:59         ` Joseph S. Myers
2013-09-06 17:43           ` Steve Ellcey
2013-09-06 18:57             ` Brooks Moses [this message]
2013-09-18 17:41           ` Steve Ellcey
2013-09-19 15:25             ` Carlos O'Donell
2013-09-19 17:02               ` Steve Ellcey
2013-09-20 16:43             ` Joseph S. Myers
2013-09-20 17:32               ` Steve Ellcey
2013-12-12 22:19                 ` Andrew Pinski
2013-12-13  0:01                   ` Carlos O'Donell
2013-12-13  0:14                     ` Steve Ellcey
2013-12-13  0:22                       ` Andrew Pinski
2013-12-13  4:40                       ` Carlos O'Donell
2013-09-06 16:59       ` Steve Ellcey

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=CAOxa4KoxtrtaupLv5nyjccFyxhhSOFhfeFUcr9UCy-oS2tRtEA@mail.gmail.com \
    --to=bmoses@google.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=sellcey@mips.com \
    /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).