public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wwwhhhyyy333 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98176] Loop invariant memory could not be hoisted when nonpure_call in loop body
Date: Thu, 08 Jul 2021 05:25:09 +0000	[thread overview]
Message-ID: <bug-98176-4-T8pgvWQveC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98176-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98176

--- Comment #9 from Hongyu Wang <wwwhhhyyy333 at gmail dot com> ---
(In reply to Richard Biener from comment #8)

> I'm failing to reproduce with the sincos example since sincos is transformed
> to __builtin_cexpi for me.  When using

I always generate sincosf with g++ -Ofast -fopenmp-simd -std=c++11, perhaps it
is related to libm? I'm using RHEL8 with glibc 2.28.

> so I don't think it buys us anything to handle calls yet.  sincos would
> also be considered as possibly not returning.
> 

Perhaps, since the sincosf case could only be vectorized with #pragma omp simd.
But I think it is better to allow those functions with libmvec implementation
if the input params are proved to be safe (such as local variables).

      parent reply	other threads:[~2021-07-08  5:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 13:57 [Bug tree-optimization/98176] New: " wwwhhhyyy333 at gmail dot com
2020-12-07 14:18 ` [Bug tree-optimization/98176] " rguenth at gcc dot gnu.org
2020-12-08  2:19 ` wwwhhhyyy333 at gmail dot com
2020-12-08  7:09 ` rguenth at gcc dot gnu.org
2020-12-08  8:29 ` wwwhhhyyy333 at gmail dot com
2020-12-08  9:25 ` rguenth at gcc dot gnu.org
2020-12-08 10:36 ` wwwhhhyyy333 at gmail dot com
2020-12-15  9:13 ` wwwhhhyyy333 at gmail dot com
2021-07-07 12:34 ` rguenth at gcc dot gnu.org
2021-07-08  5:25 ` wwwhhhyyy333 at gmail dot com [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=bug-98176-4-T8pgvWQveC@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).