From: Jakub Jelinek <jakub@redhat.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] builtins: Guard builtins.cc against HUGE_VAL and NAN definitions
Date: Wed, 2 Nov 2022 10:27:35 +0100 [thread overview]
Message-ID: <Y2I4BwD7jxZzcycu@tucnak> (raw)
In-Reply-To: <yddv8nxiurb.fsf@CeBiTec.Uni-Bielefeld.DE>
On Wed, Nov 02, 2022 at 10:13:44AM +0100, Rainer Orth wrote:
> trunk bootstrap recently broke on Solaris like this:
>
> /vol/gcc/src/hg/master/local/gcc/builtins.cc:2104:8: error: pasting "CFN_BUILT_IN_" and "(" does not give a valid preprocessing token
> 2104 | case CFN_BUILT_IN_##MATHFN: \
> | ^~~~~~~~~~~~~
> /vol/gcc/src/hg/master/local/gcc/builtins.cc:2112:3: note: in expansion of macro 'CASE_MATHFN'
> 2112 | CASE_MATHFN(MATHFN) \
> | ^~~~~~~~~~~
> /vol/gcc/src/hg/master/local/gcc/builtins.cc:1967:5: note: in expansion of macro 'CASE_MATHFN_FLOATN'
> 1967 | CASE_MATHFN_FLOATN (HUGE_VAL) \
>
> and similarly for NAN.
>
> It turns out this happens because <math.h> is included at some point,
> which (in <iso/math_c99.h>) defines
>
> #define HUGE_VAL (__builtin_huge_val())
> #define NAN (__builtin_nanf(""))
>
> While this only happpens on Solaris right now, the same issue would be
> present on other targets when <math.h> gets included somehow.
>
> To avoid this, this patch #undef's both macros.
>
> Bootstrapped without regressions on i386-pc-solaris2.11 and
> sparc-sun-solaris2.11.
>
> Ok for trunk?
>
> Rainer
>
> --
> -----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University
>
>
> 2022-11-01 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
>
> gcc:
> * builtins.cc (mathfn_built_in_2): #undef HUGE_VAL, NAN.
LGTM, thanks.
Jakub
prev parent reply other threads:[~2022-11-02 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 9:13 Rainer Orth
2022-11-02 9:27 ` Jakub Jelinek [this message]
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=Y2I4BwD7jxZzcycu@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ro@cebitec.uni-bielefeld.de \
/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).