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]

Re: x*alloc optimizations


| Michael Meissner <meissner@cygnus.com> writes:
|
| > I as supplier of compiler binaries then would have my releases not
| > work, if I built the compiler on one revision, and had users on the
| > other revision tried to use the compiler.  Depending on a configure
| > test for malloc/realloc behavior is utterly dangerous for providers
| > of binary software.
|
| Come on!  This is no arbitrary test.  This is the test for ISO C
| compliance and no vendor will dare to make an compliant library
| suddenly uncompliant.

There are loads of uncomplaint systems.  Also ISO C has two different
behaviors (return NULL or return a unique pointer).  If you test for one, a
system vendor may change his/her implementation to do the other behavior
without breaking ISO C conformance.


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