public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/53024] New: Power of 2 requirement on vector_size not documented Date: Tue, 17 Apr 2012 20:40:00 -0000 [thread overview] Message-ID: <bug-53024-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53024 Bug #: 53024 Summary: Power of 2 requirement on vector_size not documented Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: marc.glisse@normalesup.org Hello, typedef float VEC __attribute__ ((__vector_size__ (12))); fails to compile with the message: error: number of components of the vector not a power of two This is quite clear, and I guess it makes sense. However, http://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html says: "Specifying a combination that is not valid for the current architecture will cause GCC to synthesize the instructions using a narrower mode." so I was expecting gcc to handle it somehow. Could we add a sentence, anywhere in that page, that makes the requirement that the size is a power of 2 explicit? Or if the requirement can be lifted... (I don't care so much about 3 float, I can just store 4 and ignore the last, but I do care about 12 double and don't want to store 16 until we get 512bit vectors)
next reply other threads:[~2012-04-17 20:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-17 20:40 marc.glisse at normalesup dot org [this message] 2012-04-18 10:16 ` [Bug c/53024] " rguenth at gcc dot gnu.org 2012-09-27 10:06 ` glisse at gcc dot gnu.org 2012-09-27 10:14 ` glisse at gcc dot gnu.org 2012-11-16 16:06 ` [Bug middle-end/53024] Support vector_size that is not a power of 2 glisse at gcc dot gnu.org 2012-11-16 18:18 ` pinskia at gcc dot gnu.org 2012-11-16 20:03 ` glisse 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-53024-4@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).