From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8711 invoked by alias); 9 Aug 2010 11:57:56 -0000 Received: (qmail 8656 invoked by uid 48); 9 Aug 2010 11:57:40 -0000 Date: Mon, 09 Aug 2010 11:57:00 -0000 Message-ID: <20100809115740.8655.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug rtl-optimization/45235] const volatile read moved out of order In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "bigotp at acm dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-08/txt/msg00642.txt.bz2 ------- Comment #1 from bigotp at acm dot org 2010-08-09 11:57 ------- Created an attachment (id=21441) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21441&action=view) fixes for assumption that readonly means constant The problem is caused by the same sort of test as was fixed in a different situation in #35729. In the attached patch, it is the change to rtanal.c:rtx_varies_p that fixes the problem. The remaining changes are plausible, but I don't know whether they're necessary. There are additional uses of MEM_READONLY_P that are also questionable, that I didn't get around to trying. I suggest a thorough review by somebody who, unlike me, knows GCC internals. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45235