https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122411
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- I think treating an empty entry in COMPILER_PATH as meaning the current directory is correct, that's consistent with PATH (and the docs say COMPILER_PATH works that way). The docs for CPATH and C_INCLUDE_PATH are quite explicit that an empty component is treated as . It's also intentional that -isystem $dir/include is added for each dir in COMPILER_PATH I think the only bug here is that the docs for COMPILER_PATH don't mention that any dir named 'include' in one of those paths will be treated as a system include dir.
