2013/3/14 Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
Isn't that just a porting issue?
Somewhere GCC stores that information, and it's usually right. Just not on
Haiku. IMO one should "simply" update GCC to know that strdup(), free(),
etc. accept NULL pointers.
The problem is that GCC applies the same attributes to both built-in
functions and their user defined version even if eventually the
built-in version is never used. Changing the attributes of GCC
built-in functions is trivial this [1] patch for GCC would do this for
strdup() and solve this particular problem. However, if anyone tried
to compile anything that uses built-in strdup() GCC would have wrong
information about it (and that may result in another problem).
