public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51033] generic vector subscript and shuffle support was not added to C++
Date: Tue, 17 Apr 2012 12:16:00 -0000	[thread overview]
Message-ID: <bug-51033-4-47f65jYQcF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51033-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51033

--- Comment #13 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-17 12:13:02 UTC ---
(In reply to comment #12)
> On the other hand, here I am copying a small block of code in the middle of a
> function. Making just that paragraph common wouldn't make much sense imho.
> Factoring most of (cp_)build_array_ref might make sense, but requires someone
> with a better understanding of the FEs, because there are slight differences
> that may or may not be relevant.

Something is better than nothing. I respectfully disagree, there are more than
10 lines of code there. If some change is ever required in those and the code
is not shared, only one version will be changed. You can call the function
vector_to_underlying_pointer_type() or something like that. Then you don't even
need a comment.


  parent reply	other threads:[~2012-04-17 12:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 16:39 [Bug c++/51033] New: Partial vector extension support marc.glisse at normalesup dot org
2011-11-08 17:10 ` [Bug c++/51033] " rguenth at gcc dot gnu.org
2011-11-08 17:21 ` marc.glisse at normalesup dot org
2011-11-08 22:18 ` pinskia at gcc dot gnu.org
2011-11-08 22:19 ` marc.glisse at normalesup dot org
2011-11-08 22:31 ` [Bug c++/51033] [4.7 Regression] recent vector support was not added to C++ pinskia at gcc dot gnu.org
2011-11-08 22:34 ` marc.glisse at normalesup dot org
2011-11-09  9:41 ` [Bug c++/51033] generic vector subscript and shuffle " rguenth at gcc dot gnu.org
2011-11-09 10:42 ` jakub at gcc dot gnu.org
2011-12-29 10:32 ` paolo.carlini at oracle dot com
2012-04-17 10:23 ` marc.glisse at normalesup dot org
2012-04-17 10:56 ` manu at gcc dot gnu.org
2012-04-17 12:01 ` marc.glisse at normalesup dot org
2012-04-17 12:16 ` manu at gcc dot gnu.org [this message]
2012-04-17 13:10 ` marc.glisse at normalesup dot org
2012-04-17 13:26 ` manu at gcc dot gnu.org
2012-04-17 14:01 ` marc.glisse at normalesup dot org
2012-04-17 14:20 ` manu at gcc dot gnu.org
2012-04-17 16:47 ` marc.glisse at normalesup dot org
2012-04-22 10:32 ` marc.glisse at normalesup dot org
2012-04-22 13:22 ` marc.glisse at normalesup dot org
2012-04-22 14:57 ` manu at gcc dot gnu.org
2012-04-22 15:10 ` marc.glisse at normalesup dot org
2012-04-24 11:59 ` marc.glisse at normalesup dot org
2012-04-30 17:23 ` jason at gcc dot gnu.org
2012-06-13 15:15 ` ramana at gcc dot gnu.org
2012-06-14 11:23 ` ramana at gcc dot gnu.org
2012-06-15 16:44 ` ramana at gcc dot gnu.org
2012-06-27 14:20 ` ramana at gcc dot gnu.org
2012-08-11 11:27 ` glisse at gcc dot gnu.org
2013-02-17 14:42 ` linux at carewolf dot com
2013-02-17 15:04 ` glisse at gcc dot gnu.org
2013-02-17 15:24 ` linux at carewolf dot com

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-51033-4-47f65jYQcF@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).