Hi!
OK to push to newlib main branch the attached
"For GCC, newlib combined tree, newlib build-tree testing, use standard search
paths"
-- or is something else wrong here, or should this be done differently?
(I mean, I'm confused why this doesn't just work; I'm certainly not the
first person to b
On Sun, 1 Apr 2018, Sandra Loosemore wrote:
>> Our docs currently are about even and I think it would be good to
>> settle on one?
>>
>> % grep "filename" $GCC/gcc/doc/*.texi | wc -l
>> 92
>> % grep "file name" $GCC/gcc/doc/*.texi | wc -l
>> 103
>>
>> (Once
Snapshot gcc-11-20230414 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20230414/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
