https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084
--- Comment #15 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 31 Jan 2018, andrewjenner at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084 > > Andrew Jenner <andrewjenner at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |ASSIGNED > Assignee|unassigned at gcc dot gnu.org |andrewjenner at gcc > dot gnu.org > > --- Comment #14 from Andrew Jenner <andrewjenner at gcc dot gnu.org> --- > I've got most of the major chunks removed now as you can see from my > work-in-progress patch, but I'm still working through a long list of little > things I've noticed that need cleaning up. I'm not sure that the backend will > build with the changes in their current state so I haven't committed them yet, > but I expect to be able to do so by the end of the week. Thanks for your > patience! As said the most important part is to have user-facing things like config/powerpcspe/*.opt pruned from irrelevant stuff as well as a general update for user-facing documentation. Documentation updates could be as simple as duplicating any rs6000 specific documentation and pruning the duplicate from irrelevant parts. This may need re-surrecting removed doc parts (if there were any) and/or pruning SPE parts from rs6000 specific documentation sections. Esp. install.texi and invoke.texi should be audited in that respect. Whether you manage to prune all unreachable code-paths from the implementation is not so important for the GCC 8 release.
