Re: [PATCH] Add newlib to gitignore

2025-06-06 Thread Arijit Kumar Das
Hi everyone, Thank you so much for your support, it really means a lot to me. I look forward to contributing much more meaningfully beyond this small gitignore update. Best regards, Arijit On Sat, Jun 7, 2025 at 3:49 AM Sam James wrote: > > Thomas Schwinge writes: > > > Hi! > > > > On 2025-06

Re: [PATCH] Add newlib to gitignore

2025-06-06 Thread Sam James
Thomas Schwinge writes: > Hi! > > On 2025-06-02T22:01:44+0530, Arijit Kumar Das > wrote: >>> Umm, I don't think so. I've been building crosses with gcc for decades. >>> It should not be necessary, though it may sometimes be convenient. > > Right. Similarly to how it's, for example, documented

Re: [PATCH] Add newlib to gitignore

2025-06-06 Thread Jeff Law
On 6/5/25 4:17 PM, Thomas Schwinge wrote: Hi! On 2025-06-02T22:01:44+0530, Arijit Kumar Das wrote: Umm, I don't think so. I've been building crosses with gcc for decades. It should not be necessary, though it may sometimes be convenient. Right. Similarly to how it's, for example, docu

Re: [PATCH] Add newlib to gitignore

2025-06-05 Thread Thomas Schwinge
Hi! On 2025-06-02T22:01:44+0530, Arijit Kumar Das wrote: >> Umm, I don't think so. I've been building crosses with gcc for decades. >> It should not be necessary, though it may sometimes be convenient. Right. Similarly to how it's, for example, documented on

Re: [PATCH] Add newlib to gitignore

2025-06-02 Thread Arijit Kumar Das
> Umm, I don't think so. I've been building crosses with gcc for decades. > It should not be necessary, though it may sometimes be convenient. > > If you feel there's a strong need, then you're going to have to make a > better case than what you've done above. Specifically you'd need to > start wi

Re: [PATCH] Add newlib to gitignore

2025-06-02 Thread Jeff Law
On 6/2/25 3:01 AM, Arijit Kumar Das wrote: Hi, When compiling GCC for targets like nvptx-none that require newlib, we need to put newlib-cygwin/newlib in the root directory of the source tree (either a copy or a symlink), which is then built by GCC when targeting offload devices like the a

Re: [PATCH] Add newlib to gitignore

2025-06-02 Thread Arijit Kumar Das
Hi, When compiling GCC for targets like nvptx-none that require newlib, we need to put newlib-cygwin/newlib in the root directory of the source tree (either a copy or a symlink), which is then built by GCC when targeting offload devices like the above. Changes made in newlib shouldn't affect GCC,

Re: [PATCH] Add newlib to gitignore

2025-06-01 Thread Jeff Law
On 6/1/25 1:40 PM, Arijit Kumar Das wrote: newlib sources are not a part of GCC so should be ignored, if present. Signed-off-by: Arijit Kumar Das --- .gitignore | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.gitignore b/.gitignore index 7150fc3b29c..5ae6a5a08d6 100644 --- a/.giti

[PATCH] Add newlib to gitignore

2025-06-01 Thread Arijit Kumar Das
newlib sources are not a part of GCC so should be ignored, if present. Signed-off-by: Arijit Kumar Das --- .gitignore | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.gitignore b/.gitignore index 7150fc3b29c..5ae6a5a08d6 100644 --- a/.gitignore +++ b/.gitignore @@ -74,3 +74,6 @@ stamp-*