From: "Gabriel F. T. Gomes" <gftg@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Fix arg used as litteral suffix in tst-strfrom.h
Date: Mon, 12 Dec 2016 19:50:00 -0000 [thread overview]
Message-ID: <20161212175036.31e99e25@keller> (raw)
In-Reply-To: <1478716612-2570-1-git-send-email-gftg@linux.vnet.ibm.com>
Ping.
On Wed, 9 Nov 2016 16:36:52 -0200
"Gabriel F. T. Gomes" <gftg@linux.vnet.ibm.com> wrote:
> The macro ENTRY in tst-strfrom.h is used to generate the input values for
> each floating-point type (float, double, long double). It should append
> the parameter LSUF (Literal suffix) to the floating-point number, but is
> using CSUF (C function suffix). This patch fixes it.
>
> Tested for powerpc64le and x86_64.
>
> 2016-10-28 Gabriel F. T. Gomes <gftg@linux.vnet.ibm.com>
>
> * stdlib/tst-strfrom.h (ENTRY): Replace use of CSUF with LSUF.
> ---
> stdlib/tst-strfrom.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/stdlib/tst-strfrom.h b/stdlib/tst-strfrom.h
> index 31a6492..75be55f 100644
> --- a/stdlib/tst-strfrom.h
> +++ b/stdlib/tst-strfrom.h
> @@ -36,7 +36,7 @@
> #define STRUCT_FOREACH_FLOAT_FTYPE GEN_TEST_STRTOD_FOREACH (FTYPE_MEMBER)
>
> #define ENTRY(FSUF, FTYPE, FTOSTR, LSUF, CSUF, ...) \
> - CONCAT (__VA_ARGS__, CSUF),
> + CONCAT (__VA_ARGS__, LSUF),
> /* This is hacky way around the seemingly unavoidable macro
> * expansion of the INFINITY or HUGE_VAL like macros in the
> * above. It is assumed the compiler will implicitly convert
next prev parent reply other threads:[~2016-12-12 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 18:37 Gabriel F. T. Gomes
2016-12-12 19:50 ` Gabriel F. T. Gomes [this message]
2016-12-13 5:07 ` Rajalakshmi Srinivasaraghavan
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=20161212175036.31e99e25@keller \
--to=gftg@linux.vnet.ibm.com \
--cc=libc-alpha@sourceware.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).