From: "E. Robert Tisdale" <edwin@netwood.net>
To: egcs@egcs.cygnus.com
Subject: Re: Named Return Value Extension Proposal
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <36F7029D.F0EE48E8@netwood.net> (raw)
Message-ID: <19990331234600.CbiokZZJRxx_Vaq3litQCWGhRIgrnR1_Gplhc-lyEak@z> (raw)
Gabriel Dos Reis wrote:
> I don't know what will be decided,
> but let me throw my 0.02 euros in there.
> I certainly don't minimize the importance of compiler level optimizations.
> But it's my opinion that there are ISO C++ language features--
> not optimizations-- that need to be fixed or implemented in the compiler.
> That already is a lot of work to do. I'm not particularly interested
> in seeing a lot of work spent in implementing nonstandard features,
> that will probably badly interact with ISO C++,
> whereas there are more fundamental topics waiting to be addressed.
>
> So my proposal will be: let's first catch up the Standard,
> then we'll address optimizations issues.
>
> Just because a particular optimization is _permitted_
> doesn't mean that the compiler *should* implement it,
> particularly when the compiler is trying hard to get semantics right.
Gaby, You and I will both grow very old and die
before this compiler catches up with the standard.
I don't think that it is too unreasonable for me and other users
to expect the compiler to produce reasonably fast and efficient code
without hacking our source to work around a deficient optimizer.
It appears from the reply by Jason Merrill <jason@cygnus.com>
to the "elided copy constructors" thread that it will be a very long time
before the changes can be made to implement the optimizations
permitted by the standard. I am simply proposing a stop gap
to carry us through until it is possible to implement the optimizations.
I have taken some pain to ensure that the proposed extensions
will not interact badly with the ANSI/ISO C++ standard.
Please let us know if you see something wrong that I don't see.
> just my 0.02 euros.
I'll see your 0.02 euros and raise you $0.02
E. Robert Tisdale <edwin@netwood.net>
next reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-22 18:58 E. Robert Tisdale [this message]
[not found] ` < 36F7029D.F0EE48E8@netwood.net >
1999-03-22 19:14 ` Mark Mitchell
[not found] ` < 199903230316.TAA05276@adsl-206-170-148-33.dsl.pacbell.net >
1999-03-23 1:05 ` Martin v. Loewis
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` Mark Mitchell
1999-03-22 19:39 ` Gabriel Dos Reis
1999-03-31 23:46 ` Gabriel Dos Reis
1999-03-31 23:46 ` E. Robert Tisdale
-- strict thread matches above, loose matches on Subject: below --
1999-03-23 6:43 Mike Stump
1999-03-23 9:00 ` E. Robert Tisdale
1999-03-31 23:46 ` E. Robert Tisdale
1999-03-31 23:46 ` Mike Stump
1999-03-22 19:37 Mike Stump
1999-03-22 20:07 ` E. Robert Tisdale
1999-03-22 21:14 ` Bill Currie
1999-03-31 23:46 ` Bill Currie
1999-03-31 23:46 ` E. Robert Tisdale
1999-03-31 23:46 ` Mike Stump
1999-03-22 18:57 Mike Stump
1999-03-22 19:08 ` E. Robert Tisdale
1999-03-31 23:46 ` E. Robert Tisdale
1999-03-31 23:46 ` Mike Stump
1999-03-22 13:10 E. Robert Tisdale
1999-03-22 16:59 ` Gabriel Dos Reis
1999-03-31 23:46 ` Gabriel Dos Reis
1999-03-31 23:46 ` E. Robert Tisdale
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=36F7029D.F0EE48E8@netwood.net \
--to=edwin@netwood.net \
--cc=egcs@egcs.cygnus.com \
/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).