public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ddesics at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/54978] Add ability to provide vectorized functions Date: Fri, 19 Oct 2012 16:14:00 -0000 [thread overview] Message-ID: <bug-54978-4-iPHHJkS5JA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54978-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54978 --- Comment #3 from Daniel Davis <ddesics at gmail dot com> 2012-10-19 16:14:36 UTC --- Obviously, it would be nice if gcc can build the functions if they are pure functions. But that would require somehow knowing that those functions should be built and having access to the code, which may not be the case for something like a library. On second thought, the attribute would best go with declaration of the vectorized function. So, to rewrite my example, double fx(double x); v2df fx_v2df(v2df x) __attribute__((vectorized_alias(fx,double,16))); v4df fx_v4df(v4df x) __attribute__((vectorized_alias(fx,double,32))); That would let the compiler know exactly what could be replaced, although it should be able to figure out the argument types from the declarations. So I see two potential optimizations here. The first is a way to let the compiler know that vectorized functions are available. The second would be to let the auto-vectorizer create vectorized forms of functions.
next prev parent reply other threads:[~2012-10-19 16:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-18 17:51 [Bug tree-optimization/54978] New: " ddesics at gmail dot com 2012-10-19 8:46 ` [Bug tree-optimization/54978] " rguenth at gcc dot gnu.org 2012-10-19 10:01 ` jakub at gcc dot gnu.org 2012-10-19 16:14 ` ddesics at gmail dot com [this message] 2021-08-16 4:44 ` pinskia at gcc dot gnu.org
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-54978-4-iPHHJkS5JA@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: linkBe 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).