Re: CFT: snmalloc as libc malloc
- In reply to: Mark Millard : "Re: CFT: snmalloc as libc malloc"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 13 Feb 2023 10:45:56 UTC
On 12/02/2023 22:32, Mark Millard wrote: > I'll note that include/c++/v1/stddef.h uses: > > #include_next <stddef.h> > > That in turn causes a stddef.h to be found that is > from later in the search list (not earlier or the > same file again). > > As for the include ordering, this leads to > . . ./include/c++/v1 needing to be before the > directory for the matching normal C header(s) that > C++ is(are) trying to include. > > There are implications for recursive include > handling during #include_next processing (just the > tail of the search list is used as I understand). I hit a problem with this related to the msun headers, which was fixed in the diff by changing the include from libc to: CFLAGS+= --include-directory-after ${SRCTOP}/lib/msun/src This may also be necessary for other headers if the way that the libc / libc++ headers are included has changed. David