public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: Handle internal functions in is_tm_pure_call
Date: Fri, 06 Nov 2015 19:31:00 -0000	[thread overview]
Message-ID: <563D0027.2020609@redhat.com> (raw)
In-Reply-To: <87k2pvrlbp.fsf@e105548-lin.cambridge.arm.com>

On 11/06/2015 12:15 PM, Richard Sandiford wrote:
> The upcoming changes to use internal functions for things like sqrt
> caused a failure in gcc.dg/tm/20100610.c, because we were trying to get
> call flags from the null gimple_call_fn of an IFN_SQRT call.  We've been
> making fairly heavy use of internal functions for a while now so I think
> this might be latent.
>
> Tested on x86_64-linux-gnu, aarch64-linux-gnu and arm-linux-gnueabi.
> OK to install?
>
> Thanks,
> Richard
>
>
> gcc/
> 	* trans-mem.c (is_tm_pure_call): Use gimple_call_flags for
> 	internal functions.
OK.
jeff

      reply	other threads:[~2015-11-06 19:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 19:15 Richard Sandiford
2015-11-06 19:31 ` Jeff Law [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=563D0027.2020609@redhat.com \
    --to=law@redhat.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).