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 c++/21672] Loses temporary in complex expression Date: Thu, 19 May 2005 23:35:00 -0000 [thread overview] Message-ID: <20050519233506.12267.qmail@sourceware.org> (raw) In-Reply-To: <20050519212022.21672.igodard@pacbell.net> ------- Additional Comments From gdr at integrable-solutions dot net 2005-05-19 23:35 ------- Subject: Re: Loses temporary in complex expression "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes: | Here is another example where we don't know for sure it shows how the compiler uses operators in | C++: | template<class T> const | T& g(T t1, const T& t2) { return t1.h(t2); } | | struct f{ f &h(const f&);}; | f i; | f j; | | f h = g(i , j); | | h is the operator for |= and g is the operator for |. And we can construct more. But it does not rule out the fact that we should handle the simple cases. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21672
next prev parent reply other threads:[~2005-05-19 23:35 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-19 21:20 [Bug c++/21672] New: " igodard at pacbell dot net 2005-05-19 21:22 ` [Bug c++/21672] " igodard at pacbell dot net 2005-05-19 21:22 ` igodard at pacbell dot net 2005-05-19 22:56 ` pinskia at gcc dot gnu dot org 2005-05-19 23:12 ` igodard at pacbell dot net 2005-05-19 23:19 ` pinskia at gcc dot gnu dot org 2005-05-19 23:21 ` pinskia at gcc dot gnu dot org 2005-05-19 23:27 ` gdr at integrable-solutions dot net 2005-05-19 23:31 ` gdr at integrable-solutions dot net 2005-05-19 23:35 ` gdr at integrable-solutions dot net [this message] 2005-05-19 23:40 ` pinskia at gcc dot gnu dot org 2005-05-19 23:42 ` pinskia at gcc dot gnu dot org 2005-05-19 23:42 ` igodard at pacbell dot net 2005-05-19 23:46 ` pinskia at gcc dot gnu dot org 2005-05-19 23:54 ` igodard at pacbell dot net 2005-05-20 0:12 ` gdr at integrable-solutions dot net 2005-05-20 0:15 ` gdr at integrable-solutions dot net
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=20050519233506.12267.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: 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).