On Tue, 26 Nov 2019, Eric S. Raymond wrote:
> Joseph Myers :
> > Thanks. We've accumulated a lot of merge requests on the gcc-conversion
> > repository, once those are merged I'll test a further change to remove
> > those tags.
>
> I just checked; a rebase button appeared on your MRs and I mer
Joseph Myers :
> Thanks. We've accumulated a lot of merge requests on the gcc-conversion
> repository, once those are merged I'll test a further change to remove
> those tags.
I just checked; a rebase button appeared on your MRs and I merged all
three, but no rebase option occurs on Richard Ear
Every now and then I see test suite failures in my builds that
I can't reproduce when I then execute the tests individually
via a make check target. In the test log there often (always?)
are the following messages around those failures:
&"warning: GDB: Failed to set controlling terminal: Operati
On Tue, 26 Nov 2019, Eric S. Raymond wrote:
> Joseph Myers :
> > A further note: in a previous run of the conversion I didn't see any
> > emptycommit-* tags. In my most recent conversion run, I see 4070 such
> > tags. How do I tell reposurgeon never to create such tags? Or should I
> > add a
On 11/25/19 2:43 PM, Andrew Dean via gcc wrote:
>> I get errors like this:
>>
>> aarch64-glibc-linux-gnu-gcc: fatal error: cannot read spec file
>> 'rdimon.specs': No such file or directory
>>
>> I can see that the rdimon.specs flag is added based on this line
>> in aarc
Joseph Myers :
> A further note: in a previous run of the conversion I didn't see any
> emptycommit-* tags. In my most recent conversion run, I see 4070 such
> tags. How do I tell reposurgeon never to create such tags? Or should I
> add a tag deletion command for them in gcc.lift, once tag de
On Mon, 25 Nov 2019, Eric S. Raymond wrote:
> I knew there was a problem with those, but I have not diagnosed it
> yet. I know generally where it has to be and think it will be
> relatively easy to clean up once I've dealt with the more pressing
> issues.
>
> Please file issues about these bugs
