Re: [PATCH 2/2] libcpp: Avoid remapping filenames within directives

2022-11-02 Thread Richard Purdie via Gcc-patches
On Tue, 2022-11-01 at 13:32 -0600, Jeff Law wrote: > On 8/17/22 06:15, Richard Purdie via Gcc-patches wrote: > > Code such as: > #include __FILE__ > > > > can interact poorly with file-prefix-map options when cross compiling. In > > general you're after to remap filenames for use in target

Re: [PATCH 2/2] libcpp: Avoid remapping filenames within directives

2022-11-01 Thread Jeff Law via Gcc-patches
On 8/17/22 06:15, Richard Purdie via Gcc-patches wrote: Code such as: #include __FILE__ can interact poorly with file-prefix-map options when cross compiling. In general you're after to remap filenames for use in target context but the local paths should be used to find include files at

Re: [PATCH 2/2] libcpp: Avoid remapping filenames within directives

2022-08-17 Thread Richard Purdie via Gcc-patches
On Wed, 2022-08-17 at 13:15 +0100, Richard Purdie via Gcc-patches wrote: > Code such as: > > can interact poorly with file-prefix-map options when cross compiling. In > general you're after to remap filenames for use in target context but the > local paths should be used to find include files at

[PATCH 2/2] libcpp: Avoid remapping filenames within directives

2022-08-17 Thread Richard Purdie via Gcc-patches
Code such as: can interact poorly with file-prefix-map options when cross compiling. In general you're after to remap filenames for use in target context but the local paths should be used to find include files at compile time. Ingoring filename remapping for directives is one way to avoid such