public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: [PATCH] tree.h: Hide wi::from_mpz from GENERATOR_FILE
Date: Fri, 30 Jun 2023 10:50:37 +0200	[thread overview]
Message-ID: <CAFiYyc0v5jkvbrGDRbk9uz1_0Qq77TP2nQgov0pH+S81FaaxRQ@mail.gmail.com> (raw)
In-Reply-To: <743141ec-624e-0cab-f30e-54765c3c6b05@linux.ibm.com>

On Fri, Jun 30, 2023 at 7:20 AM Kewen.Lin <linkw@linux.ibm.com> wrote:
>
> Hi,
>
> Similar to r0-85707-g34917a102a4e0c for PR35051, the uses
> of mpz_t should be guarded with "#ifndef GENERATOR_FILE".
> This patch is to fix it and avoid some possible build
> errors.
>
> Bootstrapped and regress-tested on x86_64-redhat-linux,
> and powerpc64{,le}-linux-gnu.  And cross-build well on
> power for 40+ different ports.
>
> Is it ok for trunk?

OK.

> gcc/ChangeLog:
>
>         * tree.h (wi::from_mpz): Hide from GENERATOR_FILE.
> ---
>  gcc/tree.h | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/gcc/tree.h b/gcc/tree.h
> index 1854fe4a7d4..7e92a12f9cb 100644
> --- a/gcc/tree.h
> +++ b/gcc/tree.h
> @@ -6460,7 +6460,9 @@ namespace wi
>
>    wide_int min_value (const_tree);
>    wide_int max_value (const_tree);
> +#ifndef GENERATOR_FILE
>    wide_int from_mpz (const_tree, mpz_t, bool);
> +#endif
>  }
>
>  template <typename T>
> --
> 2.39.3

      reply	other threads:[~2023-06-30  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  5:20 Kewen.Lin
2023-06-30  8:50 ` Richard Biener [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=CAFiYyc0v5jkvbrGDRbk9uz1_0Qq77TP2nQgov0pH+S81FaaxRQ@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linkw@linux.ibm.com \
    --cc=richard.sandiford@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).