public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@cavium.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, Szabolcs Nagy <szabolcs.nagy@arm.com>,
	nd <nd@arm.com>
Subject: Re: Obsolete matherr, _LIB_VERSION, libieee.a
Date: Thu, 24 Aug 2017 17:44:00 -0000	[thread overview]
Message-ID: <1503596671.28672.93.camel@cavium.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1708241722540.15952@digraph.polyomino.org.uk>

On Thu, 2017-08-24 at 17:24 +0000, Joseph Myers wrote:
> 
> TEST_COMPAT is plausible, but the patch does of course need to address the 
> malloc test as well (with the appropriate version for obsoletion named in 
> the TEST_COMPAT call), and I think returning 77 (UNSUPPORTED) rather than 
> 0 is appropriate in the fallback case, given that the (obsolete) feature 
> being tested *is* unsupported by the (new) port.

OK, I will submit a patch that includes tst-mallocstate.c and that
returns 77 for the fallback case.  One question, should I update
tst-mallocstate.c from using test-skeleton.c to test-driver.c as
part of this change or is that something that should be done in a
separate patch.

Steve Ellcey
sellcey@cavium.com

  reply	other threads:[~2017-08-24 17:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 21:30 Joseph Myers
2017-08-21 20:16 ` Adhemerval Zanella
2017-08-21 21:45   ` Joseph Myers
2017-08-21 20:32 ` Gabriel F. T. Gomes
2017-08-21 21:17   ` Joseph Myers
2017-08-23 20:21 ` Steve Ellcey
2017-08-24  9:27   ` Szabolcs Nagy
2017-08-24 12:32   ` Joseph Myers
2017-08-24 17:20     ` Steve Ellcey
2017-08-24 17:25       ` Joseph Myers
2017-08-24 17:44         ` Steve Ellcey [this message]
2017-08-24 18:08           ` Joseph Myers
2017-08-24 18:55       ` Florian Weimer
2017-08-24 21:06         ` 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=1503596671.28672.93.camel@cavium.com \
    --to=sellcey@cavium.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.com \
    --cc=szabolcs.nagy@arm.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).