This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/59850] Support sparse-style pointer address spaces (type attributes)
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 27 Jun 2014 11:24:28 +0000
- Subject: [Bug c/59850] Support sparse-style pointer address spaces (type attributes)
- Auto-submitted: auto-generated
- References: <bug-59850-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59850
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #22 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #21)
> 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.
* We could add plugins to the GCC repository for things that are considered
generally useful but we don't want to bloat standard gcc. I am sure the FSF
will be happier if plugins live in the GCC repository and they are assigned to
them than if not.
* A plugin living in the GCC repository will likely have a lower barrier for
acceptance than code added to GCC.