public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "josh at joshtriplett dot org" <gcc-bugzilla@gcc.gnu.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 [thread overview]
Message-ID: <bug-59850-4-UxACrwYtHl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59850-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #19 from Josh Triplett <josh at joshtriplett dot org> ---
(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.
next prev parent reply other threads:[~2014-02-21 4:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 5:05 [Bug c/59850] New: " hpa at zytor dot com
2014-01-17 8:03 ` [Bug c/59850] " josh at joshtriplett dot org
2014-02-01 5:26 ` tromey at gcc dot gnu.org
2014-02-01 18:39 ` josh at joshtriplett dot org
2014-02-03 8:20 ` tromey at gcc dot gnu.org
2014-02-05 14:45 ` tromey at gcc dot gnu.org
2014-02-05 15:55 ` josh at joshtriplett dot org
2014-02-05 16:50 ` hpa at zytor dot com
2014-02-05 17:51 ` tromey at gcc dot gnu.org
2014-02-05 18:11 ` tromey at gcc dot gnu.org
2014-02-05 20:06 ` josh at joshtriplett dot org
2014-02-05 20:07 ` josh at joshtriplett dot org
2014-02-05 20:08 ` josh at joshtriplett dot org
2014-02-05 20:12 ` tromey at gcc dot gnu.org
2014-02-06 0:08 ` josh at joshtriplett dot org
2014-02-06 4:44 ` hpa at zytor dot com
2014-02-21 3:09 ` tromey at gcc dot gnu.org
2014-02-21 3:37 ` tromey at gcc dot gnu.org
2014-02-21 4:19 ` josh at joshtriplett dot org [this message]
2014-02-21 14:58 ` tromey at gcc dot gnu.org
2014-06-27 4:33 ` tromey at gcc dot gnu.org
2014-06-27 11:24 ` manu at gcc dot gnu.org
2014-06-27 14:24 ` manu at gcc dot gnu.org
2014-06-29 2:26 ` tromey at gcc dot gnu.org
2014-07-03 20:36 ` tromey at gcc dot gnu.org
2014-07-03 20:48 ` josh at joshtriplett dot org
2014-07-03 21:03 ` tromey at gcc dot gnu.org
2014-07-09 14:10 ` tromey at gcc dot gnu.org
2014-07-09 14:31 ` tromey at gcc dot gnu.org
2014-07-30 23:24 ` tromey at gcc dot gnu.org
2014-08-08 16:10 ` tromey at gcc dot gnu.org
2022-09-26 22:47 ` dmalcolm at gcc dot gnu.org
2022-10-03 15:02 ` mpolacek at gcc dot gnu.org
2022-10-03 16:16 ` hpa at zytor dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-59850-4-UxACrwYtHl@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).