public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@mips.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: <libc-ports@sourceware.org>
Subject: Re: [patch, mips] Improved memset for MIPS
Date: Fri, 06 Sep 2013 15:42:00 -0000	[thread overview]
Message-ID: <1378482079.5770.293.camel@ubuntu-sellcey> (raw)
In-Reply-To: <201309052041.00545.vapier@gentoo.org>

On Thu, 2013-09-05 at 20:40 -0400, Mike Frysinger wrote:
> On Thursday 05 September 2013 13:05:43 Steve Ellcey wrote:
> > --- a/ports/sysdeps/mips/memset.S
> > +++ b/ports/sysdeps/mips/memset.S
> > @@ -1,6 +1,5 @@
> > -/* Copyright (C) 2002-2013 Free Software Foundation, Inc.
> > +/* Copyright (C) 2013 Free Software Foundation, Inc.
> 
> err, that's not generally how it works ... we extend the years, but don't 
> delete them.

I am replaced the entire file.  While the diff makes it look like some
stuff is not replaced, the standard copyright text is about the only
thing not completely changed.  There are some blank lines and maybe a
couple of assembly language psuedo-ops that happen to match up by chance
but that is pure coincidence.

> 
> > -   Contributed by Hartvig Ekner <hartvige@mips.com>, 2002.
> 
> what'd he ever do to you ? :p

Nothing, but I didn't use any of the old code.

> > +#ifdef ANDROID_CHANGES
> 
> i wouldn't think we'd normally accept this kind of stuff, but i guess it's 
> already been done with the mips memcpy ...
> -mike

Yes, I am trying to have a common memset, memcpy, and maybe some other
routines between glibc, newlib, and android/bionic.

Steve Ellcey
sellcey@mips.com



  reply	other threads:[~2013-09-06 15:42 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 [this message]
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
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=1378482079.5770.293.camel@ubuntu-sellcey \
    --to=sellcey@mips.com \
    --cc=libc-ports@sourceware.org \
    --cc=vapier@gentoo.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).