From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2776 invoked by alias); 18 Feb 2003 05:06:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 2752 invoked by uid 71); 18 Feb 2003 05:06:00 -0000 Date: Tue, 18 Feb 2003 05:06:00 -0000 Message-ID: <20030218050600.2747.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: snyder Subject: Re: c++/9722: g++ 3.4: structure passing bug Reply-To: snyder X-SW-Source: 2003-02/txt/msg00768.txt.bz2 List-Id: The following reply was made to PR c++/9722; it has been noted by GNATS. From: snyder To: Alan Modra 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