Re: [PATCH] [wwwdocs] Add a "Plugin issues" section to the GCC 6 porting guide

Hi David, On Thu, 11 Feb 2016, David Malcolm wrote: > I've (mostly) ported gcc-python-plugin to gcc 6. The attached patch > for the gcc website starts a new "Plugin issues" section, and covers > the biggest issue I ran into (FWIW the suggested compatibility typedef > is the one I committed to gcc

[PING^2] Re: [PATCH] [wwwdocs] Add a "Plugin issues" section to the GCC 6 porting guide

Ping On Thu, 2016-02-18 at 10:44 -0500, David Malcolm wrote: > Ping: > https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00765.html > > > On Thu, 2016-02-11 at 10:12 -0500, David Malcolm wrote: > > I've (mostly) ported gcc-python-plugin to gcc 6. The attached > > patch > > for the gcc website start

[PING] Re: [PATCH] [wwwdocs] Add a "Plugin issues" section to the GCC 6 porting guide

Ping: https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00765.html On Thu, 2016-02-11 at 10:12 -0500, David Malcolm wrote: > I've (mostly) ported gcc-python-plugin to gcc 6. The attached patch > for the gcc website starts a new "Plugin issues" section, and covers > the biggest issue I ran into (FWIW

[PATCH] [wwwdocs] Add a "Plugin issues" section to the GCC 6 porting guide

I've (mostly) ported gcc-python-plugin to gcc 6. The attached patch for the gcc website starts a new "Plugin issues" section, and covers the biggest issue I ran into (FWIW the suggested compatibility typedef is the one I committed to gcc-python-plugin). Validates. OK to commit?Index: htdocs/gcc-