From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13676 invoked by alias); 24 Oct 2006 16:10:04 -0000 Received: (qmail 13572 invoked by uid 48); 24 Oct 2006 16:09:50 -0000 Date: Tue, 24 Oct 2006 16:10:00 -0000 Message-ID: <20061024160950.13571.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/29582] Parameter pushed to stack too soon In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "oder at eleks dot lviv dot ua" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-10/txt/msg02110.txt.bz2 List-Id: ------- Comment #2 from oder at eleks dot lviv dot ua 2006-10-24 16:09 ------- (In reply to comment #1) > The evaluation order of function arguments is not specified. If you depend on > side effects to be carried out at a specific point you must make sure there is > a sequence point at the appropriate place. These are not the arguments of a single function. Given example is the sequence of method invocations for a class instance. Modification of lvalue occurs in 2nd method invocation and it is supposed to be passed to 4th method invocation. -- oder at eleks dot lviv dot ua changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29582