On Sat, 21 Jan 2023, Tobias Burnus wrote: > On the technical side, the newer newlib version is not yet required. But > it looks as if it soon makes a lot of sense to have it: : > As nvptx/amdgcn is (mostly) about offloading code, newlib is compiled > usually alongside GCC (e.g. in SUSE, Debian/Ubuntu, ...); additionally, > there is static linking such that mixing old vs. new libraries is less > likely. Hence, requiring the newest version of newlib together with the > newest compiler shouldn't be a problem in my opinion.
That sounds like a convincing argument. >> And, this predates your patch, in one instance we refer to Newlib >> (upper case9, in the other to newlib (lower case). Would it make >> sense to converge to one? > Maybe, but the question is what to use? The project's webpage has on the > first page: "patch submissions to Newlib" and "automate the testing of > newlib". I also dug into the newlib web page and other sources and - while my personal preference slightly leans towards Newlib - believe newlib is more established overall. For the web pages, it's clearer than for our *.texi ones you dug into: ~/src/wwwdocs/htdocs> grep -r newlib . | wc -l 15 ~/src/wwwdocs/htdocs> grep -r Newlib . | wc -l 3 > Thoughts? Let's go for newlib (lowercase) I'd say; if you agree I can take care of wwwdocs Cheers, Gerald
