This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [libiberty] does anyone use regex.c with REGEX_MALLOC?


On 07/29/2016 05:34 AM, Aldy Hernandez wrote:
On 07/29/2016 07:30 AM, Aldy Hernandez wrote:
On 07/25/2016 06:30 PM, Manuel López-Ibáñez wrote:
On 25/07/16 21:16, Joseph Myers wrote:
On Mon, 25 Jul 2016, Jeff Law wrote:

I'll pre-approve removing those bits.  Alternately, you could look to
resync
with glibc, though that could prove painful after 15 years of
divergence.

The current glibc implementation is completely different; the libiberty
version was replaced in glibc many years ago.  Obsolete libiberty by
gnulib for all its users and you get a portable version of the current
glibc regex that way....

BTW, this is what Ayush is trying to do:

https://gcc.gnu.org/ml/gcc-patches/2016-07/msg01302.html

https://gcc.gnu.org/wiki/replacelibibertywithgnulib

It would be great if someone could review his patches. I cannot approve
them myself.

You could even ask him to look next at replacing the libiberty version
of regex.c with gnulib's in GCC. It is on his TODO list.

Well, if libiberty is going to be replaced en masse by gnulib, then
there's no sense in me cleaning up libiberty's regex.

BTW, does this libiberty replacement project also fix binutils and gdb,
or will these other libiberty users require independent patches for
their respective projects?
I think other users of libibery own the decision whether or not to switch from libiberty to gnulib and if they decide to switch they also own the mechanics of making the change.

Jeff


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]