From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12809 invoked by alias); 21 Feb 2014 04:19:33 -0000 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 Received: (qmail 12758 invoked by uid 48); 21 Feb 2014 04:19:29 -0000 From: "josh at joshtriplett dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59850] Support sparse-style pointer address spaces (type attributes) Date: Fri, 21 Feb 2014 04:19:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: josh at joshtriplett dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-02/txt/msg02176.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850 --- Comment #19 from Josh Triplett --- (In reply to Tom Tromey from comment #18) > (In reply to Tom Tromey from comment #17) > > It seems that "force" works on function parameters and casts > > but not direct assignments: > > It's also an error in conditional expressions and in a "return". > > I can implement this exactly but I'm curious whether it is intended. I brought this exact case up on linux-sparse, and Christopher Li's (quite reasonable) perspective was that it doesn't really make sense to put "force" on a variable to begin with (as opposed to a function parameter). Given that, I think one of two behaviors would be reasonable: either prohibit force entirely on non-parameter variable declarations, or allow it and treat it much like parameters (ignore extended type differences on assignment). I'm mildly inclined towards the latter. I don't, however, think it's sensible to reproduce sparse's behavior entirely here, allowing it but not having it take effect. Either prohibit it or give it a sensible semantic, preferably the latter.