From: Chris Metcalf <cmetcalf@tilera.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>, <libc-ports@sourceware.org>,
"Ryan S. Arnold" <rsa@us.ibm.com>,
Carlos O'Donell <carlos_odonell@mentor.com>,
Richard Henderson <rth@twiddle.net>,
Kaz Kojima <kkojima@rr.iij4u.or.jp>,
Thomas Schwinge <thomas@codesourcery.com>,
Andreas Krebbel <Andreas.Krebbel@de.ibm.com>,
"H.J. Lu" <hongjiu.lu@intel.com>,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: ABI test baseline status
Date: Sun, 13 May 2012 12:15:00 -0000 [thread overview]
Message-ID: <4FAFA5D6.4020704@tilera.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1205131001470.23868@digraph.polyomino.org.uk>
On 5/13/2012 6:42 AM, Joseph S. Myers wrote:
> * tile needs data added (probably three baselines - tilepro, tilegx32,
> tilegx64). In addition, other changes to tile and linux-generic are
> needed to bring them up to date with libc changes since those ports were
> added. (If you are maintaining a port, you really need to follow
> glibc-cvs, watch out for libc changes relevant to the port and try to get
> it updated within days unless you're away at the time. We should also try
> to make clear in patch postings if they are relevant to ports, but
> following glibc-cvs is a good idea as well.) Specifically, the
> linux-generic bits/typesizes.h (and the alpha one) doesn't seem to have
> been updated for
I have all the changes queued up in my git tree, plus other optimization,
etc., changes that have been added to our 2.12 branch for our CentOS
6.1-compatible release. I am just struggling with the abilist stuff over
this weekend and should have the whole patch series out on Monday.
I'll have some further questions to ask about the ulps-generating stuff,
though. I hacked the examples to work around the missing exception
#defines on tile to generate some plausible ulps data, but as things stand
the presence of all the FE_xxx tests means the tests don't compile.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2012-05-13 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 10:42 Joseph S. Myers
2012-05-13 12:15 ` Chris Metcalf [this message]
2012-05-14 5:05 ` Mike Frysinger
2012-05-15 10:27 ` Joseph S. Myers
2012-05-16 4:45 ` Mike Frysinger
2012-05-16 10:34 ` Joseph S. Myers
2012-05-16 5:09 ` [PATCH] ia64: update pthread_attr_t handling in bits/siginfo.h Mike Frysinger
2012-05-23 10:22 ` Joseph S. Myers
2012-05-24 2:45 ` Mike Frysinger
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=4FAFA5D6.4020704@tilera.com \
--to=cmetcalf@tilera.com \
--cc=Andreas.Krebbel@de.ibm.com \
--cc=carlos_odonell@mentor.com \
--cc=hongjiu.lu@intel.com \
--cc=joseph@codesourcery.com \
--cc=kkojima@rr.iij4u.or.jp \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=rsa@us.ibm.com \
--cc=rth@twiddle.net \
--cc=thomas@codesourcery.com \
--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).