[PING][PATCH][gcc-14] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-04-16 Thread Yash . Shinde
relying on precise code coverage and debugging information. Tested x86_64-linux. libcpp/ChangeLog: PR preprocessor/108900 * files.cc (_cpp_stack_file): Do not decrement highest_location across distinct maps. Signed-off-by: Jeremy Bettis Signed-off-by: Yash Shinde

Re: [PATCH v5] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-04-04 Thread Yash Shinde
) Regards, Yash. libcpp/ChangeLog:   PR preprocessor/108900   * files.cc (_cpp_stack_file): Do not decrement highest_location   across distinct maps. Signed-off-by: Jeremy Bettis Signed-off-by: Yash Shinde ---   libcpp/files.cc | 9 +   1 file changed, 9 insertions(+) diff --git

[PATCH][gcc-14] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-04-04 Thread Yash . Shinde
relying on precise code coverage and debugging information. Tested x86_64-linux. libcpp/ChangeLog: PR preprocessor/108900 * files.cc (_cpp_stack_file): Do not decrement highest_location across distinct maps. Signed-off-by: Jeremy Bettis Signed-off-by: Yash Shinde

[PATCH v5] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-03-28 Thread Yash . Shinde
relying on precise code coverage and debugging information. libcpp/ChangeLog: PR preprocessor/108900 * files.cc (_cpp_stack_file): Do not decrement highest_location across distinct maps. Signed-off-by: Jeremy Bettis Signed-off-by: Yash Shinde --- libcpp/files.cc | 9

[PATCH v4] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-03-14 Thread Yash . Shinde
relying on precise code coverage and debugging information. libcpp/ChangeLog: * files.cc (_cpp_stack_file): Do not decrement highest_location across distinct maps. Signed-off-by: Jeremy Bettis Signed-off-by: Yash Shinde --- libcpp/files.cc | 8 1 file changed, 8

[PATCH v3] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-03-11 Thread Yash . Shinde
From: Yash Shinde This patch addresses an issue in the C preprocessor where incorrect line number information is generated when processing files with a large number of lines. The problem arises from improper handling of location intervals in the line map, particularly when locations exceed

Re: [PING 2][PATCH v2] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-03-11 Thread Yash Shinde
On 11-03-2025 15:30, Jonathan Wakely 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. On 03/03/25 03:05 -0800, yash.shi...@windriver.com wrote: From: Yash Shinde This

[PING 2][PATCH v2] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-03-03 Thread Yash . Shinde
From: Yash Shinde This patch addresses an issue in the C preprocessor where incorrect line number information is generated when processing files with a large number of lines. The problem arises from improper handling of location intervals in the line map, particularly when locations exceed

[PING][PATCH v2] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-02-17 Thread Yash . Shinde
From: Yash Shinde This patch addresses an issue in the C preprocessor where incorrect line number information is generated when processing files with a large number of lines. The problem arises from improper handling of location intervals in the line map, particularly when locations exceed

[PING][PATCH v2] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-02-16 Thread Yash . Shinde
From: Yash Shinde This patch addresses an issue in the C preprocessor where incorrect line number information is generated when processing files with a large number of lines. The problem arises from improper handling of location intervals in the line map, particularly when locations exceed

[PATCH v2] libcpp: Fix incorrect line numbers in large files [PR108900]

2025-01-22 Thread Yash . Shinde
From: Yash Shinde This patch addresses an issue in the C preprocessor where incorrect line number information is generated when processing files with a large number of lines. The problem arises from improper handling of location intervals in the line map, particularly when locations exceed

[PATCH] Search target sysroot gcc version specific dirs with multilib.

2023-04-06 Thread Yash Shinde via Gcc-patches
32/../lib64/ /lib32/ /usr/lib32/ Signed-off-by: Khem Raj Signed-off-by: Yash Shinde --- gcc/gcc.cc | 29 - 1 file changed, 28 insertions(+), 1 deletion(-) diff --git a/gcc/gcc.cc b/gcc/gcc.cc index 16bb07f2cdc..4e5e3079804 100644 --- a/gcc/gcc.cc +++ b/gcc/

[PATCH] Add ssp_nonshared to link commandline for musl targets

2023-04-06 Thread Yash Shinde via Gcc-patches
the needed symbols are already present in libc_nonshared library therefore we do not need any library helper on glibc based systems but musl needs the libssp_noshared from gcc Signed-off-by: Khem Raj Signed-off-by: Yash Shinde --- gcc/config/linux.h | 7 +++ gcc/config/rs6000/linux.h

[PATCH] Pass CXXFLAGS_FOR_BUILD to avoid build failure errors.

2023-02-22 Thread Yash Shinde
Purdie Signed-off-by: Yash Shinde --- Makefile.in | 2 ++ Makefile.tpl | 2 ++ 2 files changed, 4 insertions(+) diff --git a/Makefile.in b/Makefile.in index 06a9398e172..4b0069b257c 100644 --- a/Makefile.in +++ b/Makefile.in @@ -178,6 +178,7 @@ BUILD_EXPORTS = \ # built for the build system to

[PATCH] libgcc_s: Use alias for __cpu_indicator_init instead of symver

2023-02-22 Thread Yash Shinde
gcc/Changelog: 2015-05-11 Szabolcs Nagy * config/i386/i386-expand.c (ix86_expand_builtin): Make __builtin_cpu_init call __cpu_indicator_init_local instead of __cpu_indicator_init. Signed-off-by: Khem Raj Signed-off-by: Yash Shinde --- gcc/config/i386/i386-expand.cc | 4 ++--

[PATCH] Share work directories

2023-02-22 Thread Yash Shinde
From: Khem Raj Fix configure and Makefile files to read the defaults.hand t-oe from build directory, so that the source can be shared between gcc-cross-initial, gcc-cross-intermediate, gcc-cross, gcc-runtime, and also the sdk build which use a separate build directory compared to source direct