public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom de Vries <Tom_deVries@mentor.com>
To: <gcc-patches@gcc.gnu.org>, <richard.sandiford@arm.com>
Subject: Re: Add gencfn-macros.c
Date: Wed, 18 Nov 2015 10:24:00 -0000	[thread overview]
Message-ID: <564C5195.7020802@mentor.com> (raw)
In-Reply-To: <87y4eaq95f.fsf@e105548-lin.cambridge.arm.com>

On 07/11/15 13:35, Richard Sandiford wrote:
> This patch automatically generates case macros such as:
>
>      CASE_CFN_SQRT
>
> for each {F,,L} floating-point built-in function and each {,L,LL,IMAX}
> integer built-in function.  The macros match the same built-in
> functions as CASE_FLT_FN and CASE_INT_FN but in addition include
> the associated internal function, if any.
>
> The idea is to make sure that users of combined_fn don't need to know
> which built-in functions have internal-function equivalents.  If we add
> a new function to internal-fn.def, all combined_fn users should pick it
> up automatically.
>
> The generator wants to use "hash_set <nofree_string_hash>",
> so the patch follows hash_map in using the types given by the
> traits as the key.  This is a no-op for current users of hash_set.
>
> Tested on x86_64-linux-gnu, aarch64-linux-gnu and arm-linux-gnueabi.

Hi,

this seems to have caused:

PR68406 - dbxout.c:2570:16: error: no matching function for call to 
'hash_set<tree_node*>::traverse(vec<tree_node*>*)'

Thanks,
- Tom

      parent reply	other threads:[~2015-11-18 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 12:36 Richard Sandiford
2015-11-09 22:36 ` Jeff Law
2015-11-18 10:24 ` Tom de Vries [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=564C5195.7020802@mentor.com \
    --to=tom_devries@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).