On Mon, 23 Jan 2023, Tobias Burnus wrote:
> In any case, I concur that it would be nice to unify .texi/.xml and
> diagnostic
> output (twice in config/or1k/elf.opt) - and likewise the wwwdocs pages.
:
> ->adds this to the to-do list.
Let me help a litte and take care of wwwdocs. Pushed. :)
Gerald
On 22.01.23 02:45, Gerald Pfeifer wrote:
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 le
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/Ub
Hi Gerald,
On 21.01.23 12:58, Gerald Pfeifer wrote:
Is it maybe a little tough to bump the minimal requirement to something
only released yesterday? Or is this not an issue looking at the use cases?
(Genuine question. Maybe nothing to worry at all.)
On the technical side, the newer newlib vers
On Sat, 21 Jan 2023, Tobias Burnus wrote:
> A new newlib version has been realized yesterday: newlib-4.3.0 (yearly
> snapshot)
:
> Comments? Suggestions? – If there are none, I intent to commit the patch
> as obvious.
Is it maybe a little tough to bump the minimal requirement to something
only r
A new newlib version has been realized yesterday: newlib-4.3.0 (yearly snapshot)
https://sourceware.org/pipermail/newlib/2023/020141.html
https://sourceware.org/ftp/newlib/index.html → 2023-01-20:
newlib-4.3.0.20230120.tar.gz (8.8 MB)
For both nvptx and GCN, the new version is recommended - most
