From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10757 invoked by alias); 25 Jun 2009 10:28:32 -0000 Received: (qmail 10708 invoked by uid 48); 25 Jun 2009 10:28:20 -0000 Date: Thu, 25 Jun 2009 10:28:00 -0000 Message-ID: <20090625102820.10707.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/2462] "restrict" implementation bug In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rguenth at gcc dot gnu 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: 2009-06/txt/msg01836.txt.bz2 ------- Comment #7 from rguenth at gcc dot gnu dot org 2009-06-25 10:28 ------- With the new restrict implementation baz() works and all the rest would work as well if the calls to link_error () would not cause the malloced memory to be clobbered. The artifact here is that malloced memory is considered global (we are not allowed to remove stores to it). But this is all unrelated to restrict support which should be properly fixed now. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2462