public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: snyder <snyder@fnal.gov>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9722: g++ 3.4: structure passing bug
Date: Tue, 18 Feb 2003 05:06:00 -0000	[thread overview]
Message-ID: <20030218050600.2747.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9722; it has been noted by GNATS.

From: snyder <snyder@fnal.gov>
To: Alan Modra <amodra@bigpond.net.au>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/9722: g++ 3.4: structure passing bug
Date: 17 Feb 2003 22:56:29 -0600

 hi Alan -
 
 >http://gcc.gnu.org/ml/gcc-patches/2003-02/msg00702.html has a good
 >chance of fixing this one.
 
 Indeed, with that patch, i get the correct results.
 
 However, i notice that instead of the call to memcpy,
 the structure is now copied by a loop moving one byte at a time.
 And that seems to be what emit_block_move will do in this
 case if memcpy takes its arguments on the stack.  Kind
 of sucky for large structures, though (though the original code
 where i ran into this was kind of stupid too, as it could have
 just as well passed the struct by const reference...).
 
 thanks!
 sss


             reply	other threads:[~2003-02-18  5:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18  5:06 snyder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-17 23:46 Alan Modra
2003-02-17 15:06 snyder

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=20030218050600.2747.qmail@sources.redhat.com \
    --to=snyder@fnal.gov \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).