public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.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, 27 Jun 2014 04:33:00 -0000 [thread overview]
Message-ID: <bug-59850-4-KGxqxvw9LQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59850-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
--- Comment #21 from Tom Tromey <tromey at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #20)
> BTW if you want to try it out I have a branch:
> https://github.com/tromey/gcc/tree/add-sparse-attributes
This still needs a bit of work.
I rebased it to be more patchlike and wrote some ChangeLog
entries, but I still need to verify that all the behavior
is correct (I forgot a lot of state...) and also write the
documentation.
That said, recently I've been wondering whether this could
be better done as a plugin. I started down the road of
simply patching gcc due, I think, to the designated_init
attribute, which can't really be done as a plugin.
But it seems that perhaps noderef/force/address_space could
be; and perhaps also bitwise and nocast.
In the "pro" column, as a plugin it could be maintained elsewhere.
That might be interesting.
In the "con" column, it's a pain if multiple projects want to
use these checks. Then it's just one more thing to fetch.
I'm curious to hear your thoughts on the subject.
next prev parent reply other threads:[~2014-06-27 4:33 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
2014-02-21 14:58 ` tromey at gcc dot gnu.org
2014-06-27 4:33 ` tromey at gcc dot gnu.org [this message]
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-KGxqxvw9LQ@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).