[PATCH] D24917: Resolve response file names relative to including file

Serge Pavlov via llvm-commits llvm-commits at lists.llvm.org
Wed Sep 28 01:25:37 PDT 2016


sepavloff added a comment.

According to MSDN, nested response files are not allowed, so no compatibility problems appear https://msdn.microsoft.com/en-us/library/3te4xt0y.aspx:

  It is not possible to specify the @ option from within a response file. That is, a response file cannot embed another response file.

As for libiberty, it allows nested response files and interprets text right after @ as file name. So files are searched relative to the cwd of compiler. It is not a problem if absolute file paths are used. It also is not a problem if including file is in the cwd. But if included file is specified by relative name and including file is not in cwd, the behavior would change.

It seems that this situation should not occur in practice because it means that response file must be written with particular cwd of compiler in mind, but some risk of compatibility issues is present.


https://reviews.llvm.org/D24917





More information about the llvm-commits mailing list