> 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 with why the standard cross build procedures don't work for nptx. > I think I'll defer to my mentors Thomas and Tobias for an explanation regarding this.
I'm a new contributor to GCC and am currently working on a GSoC project for implementing a simple VRAM file system on an offload target device (nvptx-none) for running OpenMP/OpenACC related tests, along with modifying the stub syscalls in newlib to interface with this file system. Building the offload compiler requires newlib to be present in the GCC source tree root. My work would mainly be in newlib, so I thought adding newlib to gitignore would be a good idea in case new test cases for GCC might need to be added. In that case, I would need to remove and re-add the newlib symlink for every GCC patch submitted. This is my understanding. Please correct me if I'm wrong. Arijit On Mon, Jun 2, 2025 at 7:47 PM Jeff Law <jeffreya...@gmail.com> wrote: > > > > 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 above. Changes made in newlib > > shouldn't affect GCC, so I think we should include newlib in this case. > 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 with why the standard cross build procedures don't work for nptx. > > jeff >
