From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Passing temprary by reference requires copy constructor in 3.4?
Date: Sat, 27 Nov 2004 18:16:00 -0000 [thread overview]
Message-ID: <41A83A55.4070100@lu.unisi.ch> (raw)
In-Reply-To: <416BE1A0-3FE6-11D9-941D-000A95D692F4@physics.uc.edu>
>> Indeed, however seems that std commitee is removing the restriction.
>> Hence I would like to see a flag to disable the error (if there is not one
>> already and I am just not aware of it). I am refering to the DR 391.
>
> Why, the DR is still active so GCC is correct as of right now.
> If and when the DR goes to defect, we will implement the needed
> change. But currently GCC is following the standard.
It could be material for -fpermissive. But surely not now that mainline
is stage3.
Paolo
prev parent reply other threads:[~2004-11-27 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 19:38 Peter Cech
2004-11-26 19:48 ` Andrew Pinski
2004-11-26 20:10 ` Mikael Kilpeläinen
2004-11-26 21:36 ` Andrew Pinski
2004-11-26 21:41 ` Mikael Kilpeläinen
2004-11-27 18:16 ` Paolo Bonzini [this message]
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=41A83A55.4070100@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
/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).