This is the mail archive of the gcc-patches@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] |
Thank you.Is there a guide, anywhere, of what stuff is "upstream" and what stuff is "gcc"? From my perspective, I have access to
It's described at the end of codingconventions.html.
MAXPATHLEN isnt a standards-mandated manifest define, AFAIK. Its a BSD-ism. How else do you propose I fix it except to ensure its defined before its use?
Dynamic allocation, as required for systems such as GNU HURD with no path length limit, is the proper fix. (Failing that, PATH_MAX is the POSIX name, but POSIX allows it not to be defined because there may be no limit or it may differ for different filesystems.)
Then the fix to define MAXPATHLEN if not previously defined is both easier and more portable. Otherwise, I would have to change code to dynamically create an array rather than using a stack based local, and that code would have to use some much-more-likely-to-be-non-portable mechanism for determining the real maximum path length for the specific filesystem.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |