public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/9679] Strange behaviour of valarray::apply method
Date: Fri, 12 Feb 2010 00:20:00 -0000 [thread overview]
Message-ID: <20100212002043.2158.qmail@sourceware.org> (raw)
In-Reply-To: <bug-9679-4059@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
------- Comment #10 from gdr at integrable-solutions dot net 2010-02-12 00:20 -------
Subject: Re: Strange behaviour of valarray::apply method
On Thu, Feb 11, 2010 at 6:08 PM, paolo dot carlini at oracle dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
> ------- Comment #9 from paolo dot carlini at oracle dot com 2010-02-12 00:08 -------
> Gaby, any chance you can give me some guidance about this issue? What do you
> think should we do now? The PR remained in limbo for way too much time, in my
> opinion. Thanks in advance.
at the moment, I believe fixing this means throwing away the
current valarray implementation. I'm fine with that if someone
proposes a better implementation performance-wise.
Personal opinion: I do not think that the case submitted is
an examplar of the usage envisioned for valarray. If you want
to take address into a valarray object, create a valarray object.
Don't stick references into the middle temporaries.
But, that is - again - a personal opinion.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9679
next prev parent reply other threads:[~2010-02-12 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9679-4059@http.gcc.gnu.org/bugzilla/>
2010-02-12 0:08 ` paolo dot carlini at oracle dot com
2010-02-12 0:20 ` gdr at integrable-solutions dot net [this message]
2010-02-12 0:22 ` paolo dot carlini at oracle dot com
2010-02-12 10:43 ` paolo dot carlini at oracle dot com
2010-02-12 11:06 ` gdr at integrable-solutions dot net
[not found] <20030212221600.9679.dens@stl.sarov.ru>
2003-06-02 23:50 ` reichelt@gcc.gnu.org
2003-06-02 23:53 ` reichelt@gcc.gnu.org
2004-03-19 17:06 ` pcarlini at suse dot de
2004-03-19 17:32 ` Gabriel Dos Reis
2004-03-19 17:32 ` gdr at integrable-solutions dot net
2004-03-19 18:02 ` pcarlini at suse dot de
2004-03-19 18:11 ` pcarlini at suse dot de
2004-03-19 19:12 ` gdr at integrable-solutions dot net
2004-03-20 9:27 ` pcarlini at suse dot de
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=20100212002043.2158.qmail@sourceware.org \
--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).