public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Derbyshire <pderbysh@usa.net>
To: egcs@egcs.cygnus.com
Subject: Question about compiler-supplied assignment and copy with egcs.
Date: Sun, 28 Feb 1999 22:53:00 -0000	[thread overview]
Message-ID: <3.0.6.32.19990224061953.008489d0@pop.globalserve.net> (raw)

Q: If egcs is allowed to supply the assignment operator and copy
constructor for a "plain old data" type, will they be generally more
efficient than user supplied versions?

I would expect so since the compiler should output code to use the
hardware's fastest block memory moves and should optimize temporaries and
copyings away aggressively since the compiler knows there are no side effects.

-- 
   .*.  "Clouds are not spheres, mountains are not cones, coastlines are not
-()  <  circles, and bark is not smooth, nor does lightning travel in a
   `*'  straight line."    -------------------------------------------------
        -- B. Mandelbrot  | http://surf.to/pgd.net
_____________________ ____|________     Paul Derbyshire     pderbysh@usa.net
Programmer & Humanist|ICQ: 10423848|

             reply	other threads:[~1999-02-28 22:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-28 22:53 Paul Derbyshire [this message]
     [not found] <pderbysh@usa.net's>
     [not found] ` <message>
     [not found]   ` <of>
     [not found]     ` <25>
     [not found]       ` <Feb>
     [not found]         ` <1999>
     [not found]           ` <22:35:01>
     [not found]             ` <-0800>
1999-02-24 16:27               ` Mike Stump
     [not found]                 ` < 199902250026.QAA04615@kankakee.wrs.com >
1999-02-25 22:31                   ` Paul Derbyshire
1999-02-28 22:53                     ` Paul Derbyshire
     [not found]                 ` <3.0.6.32.19990226013110.0083c530.cygnus.egcs@pop.globalserve.net>
1999-02-25 22:45                   ` Jason Merrill
     [not found]                     ` < u91zjdirxx.fsf@yorick.cygnus.com >
1999-02-27 21:01                       ` Paul Derbyshire
1999-02-28 22:53                         ` Paul Derbyshire
     [not found]                     ` <3.0.6.32.19990228000118.00923340.cygnus.egcs@pop.globalserve.net>
1999-02-27 23:55                       ` Jason Merrill
     [not found]                         ` < u9yalj7yin.fsf@yorick.cygnus.com >
1999-02-28  1:10                           ` Paul Derbyshire
1999-02-28  2:51                             ` Tudor Hulubei
     [not found]                               ` < 14041.8114.947193.298212@hal.ttlc.net >
1999-02-28  4:36                                 ` Paul Derbyshire
1999-02-28 22:53                                   ` Paul Derbyshire
1999-02-28 22:53                               ` Tudor Hulubei
1999-02-28 22:53                             ` Paul Derbyshire
1999-03-01  2:28                             ` Gerald Pfeifer
1999-03-31 23:46                               ` Gerald Pfeifer
1999-02-28 22:53                         ` Jason Merrill
1999-02-28 22:53                     ` Jason Merrill
1999-02-28 22:53                 ` Mike Stump

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=3.0.6.32.19990224061953.008489d0@pop.globalserve.net \
    --to=pderbysh@usa.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).