This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [ping] [rfa] const char *lbasename(const char *);
- To: ac131313 at cygnus dot com
- Subject: Re: [ping] [rfa] const char *lbasename(const char *);
- From: DJ Delorie <dj at redhat dot com>
- Date: Fri, 29 Jun 2001 14:11:37 -0400
- CC: gcc-patches at gcc dot gnu dot org
- References: <3B3CBDF4.3040108@cygnus.com>
> http://gcc.gnu.org/ml/gcc-patches/2001-06/msg00959.html
I suppose the people who read the mail and needed to reply didn't
realize it was for them. The libiberty patches are fine by me,
but the key part is this:
> A quick check of GCC indicates that this change will cause
> additional warnings in the GCC sources. What should I do about
> these? Can I also just check in the tweeks that fix these.
This affects cppfiles.c, dwarf2out.c, and mkdeps.c. If the
maintainers of those files could approve the needed tweaks to not warn
about const, the libiberty patch is approved.
It may help speed things up if you reposted the patch with the needed
tweaks to gcc.