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

2025-07-18 Thread Harish Sadineni
Hi Segher, On 7/18/2025 1:36 PM, Segher Boessenkool wrote: CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi! On Fri, Jul 18, 2025 at 01:29:07PM +0530, Harish Sadineni wrote

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

2025-07-18 Thread Harish Sadineni
...@windriver.com wrote: From: Harish Sadineni Avoid encoding full build paths into file headers; use only the basename of the source file. Line way too long. Commit message lines are 72 character positions wide. (The semicolon should be a colon btw. Or just a full stop reads nicer there). This

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

2025-07-18 Thread Harish . Sadineni
From: Harish Sadineni Avoid encoding full build paths into file headers, use only the basename of the source file. This improves build reproducibility, particularly in environments where build paths vary and source files are saved for debugging. For example, in addkf3-sw.c the file header

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

2025-07-17 Thread Harish . Sadineni
From: Harish Sadineni Avoid encoding full build paths into file headers; use only the basename of the source file. This improves build reproducibility, particularly in environments where build paths vary or where source files are saved for debugging. For example, in addkf3-sw.c, the file