public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/50661] std::equal should use more efficient version for arrays of pointers
Date: Tue, 11 Oct 2011 11:55:00 -0000	[thread overview]
Message-ID: <bug-50661-4-PzR71HGL7Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50661-4@http.gcc.gnu.org/bugzilla/>

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011-10-11
                 CC|                            |bernds at codesourcery dot
                   |                            |com
     Ever Confirmed|0                           |1

--- Comment #17 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-10-11 11:53:45 UTC ---
Ah, thanks for the very complete information, Andreas. Thus, I say, let's add
in CC also a person knowledgeable about ARM, and take a final decision whether
we want to apply this change for 4.7.0 unconditionally.

Bernd, can you tell us whether it would be safe to compare ARM pointers with
memcmp?


  parent reply	other threads:[~2011-10-11 11:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 23:16 [Bug libstdc++/50661] New: " emil at wojak dot eu
2011-10-07 23:48 ` [Bug libstdc++/50661] " paolo.carlini at oracle dot com
2011-10-08  7:36 ` jakub at gcc dot gnu.org
2011-10-08  8:13 ` paolo.carlini at oracle dot com
2011-10-08  8:51 ` marc.glisse at normalesup dot org
2011-10-08  9:28 ` paolo.carlini at oracle dot com
2011-10-08 11:00 ` marc.glisse at normalesup dot org
2011-10-08 11:19 ` paolo.carlini at oracle dot com
2011-10-08 11:35 ` jakub at gcc dot gnu.org
2011-10-08 11:44 ` paolo.carlini at oracle dot com
2011-10-08 11:57 ` paolo.carlini at oracle dot com
2011-10-08 12:22 ` jakub at gcc dot gnu.org
2011-10-08 12:58 ` paolo.carlini at oracle dot com
2011-10-08 13:10 ` jakub at gcc dot gnu.org
2011-10-08 13:49 ` vincenzo.innocente at cern dot ch
2011-10-11 11:05 ` paolo.carlini at oracle dot com
2011-10-11 11:42 ` krebbel at gcc dot gnu.org
2011-10-11 11:55 ` paolo.carlini at oracle dot com [this message]
2011-10-11 12:04 ` bernds at gcc dot gnu.org
2011-10-11 12:10 ` paolo.carlini at oracle dot com
2011-10-11 12:40 ` paolo.carlini at oracle dot com
2011-10-11 12:41 ` paolo at gcc dot gnu.org
2011-10-11 16:13 ` vincenzo.innocente at cern dot ch
2011-10-11 19:02 ` pcarlini at gmail dot com
2011-10-11 19:11 ` paolo.carlini at oracle 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-50661-4-PzR71HGL7Q@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).