------- Comment #3 from charlet at gcc dot gnu dot org 2008-05-12 22:31 -------
I'd suggest updating your patch to latest sources, and submit it to
gcc-patches, that's the standard procedure.
Also, it would be useful to have some kind of commitment from either
"someone" or from soem identified group of people that these files will
be tested and maintained in the future, otherwise there's no much point
in doing a code drop, and then have the files break silently without
people noticing.
Arno
--
charlet at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34717
