Hello!
On 6/2/21 9:48 PM, John Paul Adrian Glaubitz wrote:
> Just built gccrs revision 59b417323b25072aff2662f1f54f417f7b7ded61 on Debian
> unstable s390x.
>
> The testsuite fails with the following failures. Attaching the log file.
As expected, the recent patch by Michael Karcher [1] has fixed
On 07/08/2021 00:08, Mark Wielaard wrote:
> Hi Philip,
>
> On Fri, Aug 06, 2021 at 03:58:24PM +0100, Philip Herron wrote:
>> Great patch, this file has been neglected. This is now being merged
>> https://github.com/Rust-GCC/gccrs/pull/610
>>
>> Its not 100% clear but is the compiler driver here aut
On 06/08/2021 23:39, Mark Wielaard wrote:
> Hi Philip,
>
> On Fri, Aug 06, 2021 at 03:31:07PM +0100, Philip Herron wrote:
>>> Is it possible to make bors check all commits in a series? Or can we
>>> somehow connect the buildbot workers to the bors checks?
>> I think the build-bot checks for every c
On 06/08/2021 16:55, cohenarthur.dev wrote:
> On 21/08/06 03:31PM, Philip Herron wrote:
>> On 04/08/2021 21:25, Mark Wielaard wrote:
>>> Hi,
>>>
>>> On Wed, Aug 04, 2021 at 03:15:00PM +, build...@builder.wildebeest.org
>>> wrote:
The Buildbot has detected a new failure on builder gccrust-
On 07/08/2021 02:01, Mark Wielaard wrote:
> On Fri, Aug 06, 2021 at 04:23:27PM +0100, Philip Herron wrote:
>> On 05/08/2021 20:37, Mark Wielaard wrote:
>>> Hi,
>>>
>>> On Fri, Jul 30, 2021 at 03:03:13AM +0200, Mark Wielaard wrote:
That variant is attached and can also be found here:
https
Hi!
On Sun, Aug 08, 2021 at 09:03:44AM +0200, John Paul Adrian Glaubitz wrote:
> On 6/2/21 9:48 PM, John Paul Adrian Glaubitz wrote:
> > Just built gccrs revision 59b417323b25072aff2662f1f54f417f7b7ded61 on
> > Debian unstable s390x.
> >
> > The testsuite fails with the following failures. Attac
On Sun, Aug 08, 2021 at 12:51:47PM +0100, Philip Herron wrote:
> I would be interested in seeing 32bit build bots since this patch has
> been merged: https://github.com/Rust-GCC/gccrs/pull/614
>
> Which thanks to Adrian who has been testing it out.
>
> Do you have access to 32bit machines? I have
On 07/08/2021 16:45, Mark Wielaard wrote:
> Zero characters (codepoints) are acceptable in strings. The current
> Lexer::parse_string skipped such zero codepoints by accidents. The
> zero codepoint was also used as error/skip indicator, but that is only
> true if the third argument of utf8_escape_p
Hello!
On 6/8/21 1:51 PM, John Paul Adrian Glaubitz wrote:
> Testsuite fails, errors seem to indicate the same issue with floating numbers
> as it
> has been observed on 32-bit x86 and s390x [1].
As expected, Michael's patch [1] also fixed the testsuite on m68k.
Attaching the log file.
Adrian
Hi Philip
On Sun, Aug 08, 2021 at 01:36:21PM +0100, Philip Herron wrote:
> This patch looks good to go but the clang-format check is failing:
> https://github.com/Rust-GCC/gccrs/pull/615
>
> The error seems to be that it moves the extra check onto a new line.
> https://github.com/Rust-GCC/gccrs/p
Hello
On 6/7/21 10:33 PM, John Paul Adrian Glaubitz wrote:
> Just built revision 325ef69b132819b824ae757695d9724e503f7256 on Debian
> unstable hppa.
>
> Testsuite passes without any issues, attaching the full log.
Just as for x86, s390x and m68k, the fix by Michael Karcher [1] has fixed
the tes
11 matches
Mail list logo
