From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21609 invoked by alias); 12 Apr 2004 15:17:38 -0000 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 Received: (qmail 21399 invoked by alias); 12 Apr 2004 15:17:06 -0000 Date: Mon, 12 Apr 2004 15:40:00 -0000 Message-ID: <20040412151705.21398.qmail@sources.redhat.com> From: "aweiner at lsil dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040408225018.14896.aweiner@lsil.com> References: <20040408225018.14896.aweiner@lsil.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c/14896] Fails to generate code for structure field assignment when assigning first field and assignment is within an infinite loop X-Bugzilla-Reason: CC X-SW-Source: 2004-04/txt/msg00980.txt.bz2 List-Id: ------- Additional Comments From aweiner at lsil dot com 2004-04-12 15:17 ------- Subject: RE: Fails to generate code for structure field assi gnment when assigning first field and assignment is within an infinite lo op That's plausible, but why does the compiler not exhibit consistent behavior across all fields of the structure? It only seems exhibits this behavior for the first element of the structure; it compiles assignments for all subsequent elements. -----Original Message----- From: pinskia at gcc dot gnu dot org [mailto:gcc-bugzilla@gcc.gnu.org] Sent: Thursday, April 08, 2004 4:07 PM To: aweiner@lsil.com Subject: [Bug c/14896] Fails to generate code for structure field assignment when assigning first field and assignment is within an infinite loop ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-04-08 23:06 ------- This is invalid, you should use volatile keyword to keep the store in there. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14896 ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14896