Re: [PING][PATCH] config/rs6000/t-float128: Don't encode full build paths into headers

2025-07-10 Thread Segher Boessenkool
Hi! On Thu, Jul 10, 2025 at 12:10:16PM +, Sadineni, Harish wrote: > Ping for [1]https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599882.html. > > This patch avoids embedding full build paths into generated headers by using > only the basename of the source file. This helps to improve bui

[PING][PATCH] config/rs6000/t-float128: Don't encode full build paths into headers

2025-07-10 Thread Sadineni, Harish
Hi all, Ping for https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599882.html. This patch avoids embedding full build paths into generated headers by using only the basename of the source file. This helps to improve build reproducibility, particularly in environments where build paths vary

Re: [PATCH] config/rs6000/t-float128: Don't encode full build paths into headers

2022-11-02 Thread Richard Purdie via Gcc-patches
On Wed, 2022-08-17 at 13:10 +0100, Richard Purdie via Gcc-patches wrote: > Avoid encoding full build paths into headers, just use the basename of the > file. > This aids build reproducibility where the build paths vary and source is saved > for debugging purposes. > > libgcc/ChangeLog: > > *

[PATCH] config/rs6000/t-float128: Don't encode full build paths into headers

2022-08-17 Thread Richard Purdie via Gcc-patches
Avoid encoding full build paths into headers, just use the basename of the file. This aids build reproducibility where the build paths vary and source is saved for debugging purposes. libgcc/ChangeLog: * config/rs6000/t-float128: Don't encode full build paths into headers Signed-off-by: Rich