This is the mail archive of the gcc-bugs@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]

[Bug fortran/78822] [cleanup] replace static char buffers by std:string


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78822

--- Comment #2 from janus at gcc dot gnu.org ---
(In reply to Jakub Jelinek from comment #1)
> You would need to make sure it uses a xmalloc based allocator first or at
> least calls xmalloc_failed upon allocation failure, otherwise it will be a
> serious regression.

Could you please elaborate in which respect it would be a regression?

To be honest I'm not extremely familiar with the memory management principles
in GCC. Basically any dynamical allocation of memory should use xmalloc instead
of the standard malloc, right? (Could you remind me why that is so?)

Apparently std::string is not used in the Fortran front end up to now, but
indeed it is being used in other parts of GCC (e.g. it appears extensively in
the Go front end). Doesn't your comment apply there, or are they actually doing
what you describe?

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