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
...@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
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
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
From: Harish Sadineni
When gcc build with --enable-deafult-pie the following tests
were getting failed:
FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+40
FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+32
FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+24
From: Harish Sadineni
When gcc build with --enable-deafult-pie the following tests
were getting failed:
FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+40
FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+32
FAIL: gcc.target/i386/pr90579.c scan-assembler vaddsd\tr\\+24
