From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2121 invoked by alias); 5 May 2006 17:10:50 -0000 Received: (qmail 2101 invoked by uid 48); 5 May 2006 17:10:43 -0000 Date: Fri, 05 May 2006 17:10:00 -0000 Message-ID: <20060505171043.2100.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/27445] create_tmp_var_raw (gimplify.c) inadventently asserts 'volatile' on temps In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia at gcc dot gnu dot org" 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-05/txt/msg00538.txt.bz2 List-Id: ------- Comment #8 from pinskia at gcc dot gnu dot org 2006-05-05 17:10 ------- (In reply to comment #7) > Consider the following: > > volatile int j; > void p() > { > ++j; > } > > Gimplify in its present form might transform the statement above into > something like the following: It will never get the wrong type. because create_tmp_from_val uses TYPE_MAIN_VARIANT. Your issue with ++j not using incr is not related to the gimplifier at all as it also happens in every compiler version since at least 2.95.3. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27445