From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13533 invoked by alias); 26 Sep 2009 11:51:28 -0000 Received: (qmail 13482 invoked by uid 48); 26 Sep 2009 11:51:18 -0000 Date: Sat, 26 Sep 2009 11:51:00 -0000 Message-ID: <20090926115118.13481.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/25140] aliases, including weakref, break alias analysis In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "geoffk 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-09/txt/msg02405.txt.bz2 ------- Comment #7 from geoffk at gcc dot gnu dot org 2009-09-26 11:51 ------- I looked up 'weakref' in the GCC documentation because I'd forgotten exactly what it was supposed to do, and noticed that it's actually documented as applying only to functions. So, maybe we could just say that this attribute is only allowed for functions, and produce an error on line 3. Alexandre's original mail proposing the extension, , suggests the attribute for both variables and functions, but the explanation of why you'd want this feature only talks about functions. The weakref documentation does specifically talk about the case where the function is referenced both via the weakref and directly through the original symbol, and I think the typical use cases actually do this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25140