On Linux/x86_64,
f31a019d1161ec78846473da743aedf49cca8c27 is the first bad commit
commit f31a019d1161ec78846473da743aedf49cca8c27
Author: Jose E. Marchesi
Date: Fri Nov 24 06:30:28 2023 +0100
Emit funcall external declarations only if actually used.
caused
FAIL: gcc.c-torture/compile/lib
That commit makes gcc.target/i386/libcall-1.c on darwin:
FAIL: gcc.target/i386/libcall-1.c scan-assembler globl\t__divti3
because the pattern is not found, the only mention of divti3 in the generated
assembly is:
LCFI0:
movabsq $_b@GOTOFF, %rdx
movabsq $___divti3@PLTOFF, %rax
Hi FX,
> On 1 Dec 2023, at 13:55, FX Coudert wrote:
>
> That commit makes gcc.target/i386/libcall-1.c on darwin:
>
> FAIL: gcc.target/i386/libcall-1.c scan-assembler globl\t__divti3
>
> because the pattern is not found, the only mention of divti3 in the generated
> assembly is:
>
> LCFI0:
>
> mcmodel=large s not supported (yet) on any Darwin arch [PR90698], so the test
> needs skipping or xfailing, I think (either way with a reference to the PR).
Pushed as
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b74981b5cf32ebf4bfffd25e7174b5c80243447a
FX
>> mcmodel=large s not supported (yet) on any Darwin arch [PR90698], so
> the test needs skipping or xfailing, I think (either way with a
> reference to the PR).
>
> Pushed as
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b74981b5cf32ebf4bfffd25e7174b5c80243447a
Thanks for fixing this.
>> Pushed as
>> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b74981b5cf32ebf4bfffd25e7174b5c80243447a
Somehow I pushed the wrong commit, we should skip the test and not xfail.
This showed up in
https://gcc.gnu.org/pipermail/gcc-testresults/2023-December/802839.html
So, new commit push as o
> On Linux/x86_64,
>
> f31a019d1161ec78846473da743aedf49cca8c27 is the first bad commit
> commit f31a019d1161ec78846473da743aedf49cca8c27
> Author: Jose E. Marchesi
> Date: Fri Nov 24 06:30:28 2023 +0100
>
> Emit funcall external declarations only if actually used.
>
> caused
>
> FAIL: gcc
On Wed, Nov 29, 2023 at 07:51:15AM +0100, Jose E. Marchesi wrote:
> > FAIL: gcc.c-torture/compile/libcall-2.c -O1 (test for excess errors)
> > FAIL: gcc.c-torture/compile/libcall-2.c -O2 -flto
> > -fno-use-linker-plugin -flto-partition=none (test for excess errors)
> > FAIL: gcc.c-torture/compil
> On Wed, Nov 29, 2023 at 07:51:15AM +0100, Jose E. Marchesi wrote:
>> > FAIL: gcc.c-torture/compile/libcall-2.c -O1 (test for excess errors)
>> > FAIL: gcc.c-torture/compile/libcall-2.c -O2 -flto
>> > -fno-use-linker-plugin -flto-partition=none (test for excess errors)
>> > FAIL: gcc.c-tortur
On Wed, Nov 29, 2023 at 09:20:55AM +0100, Jose E. Marchesi wrote:
> OK to the patch below?
>
> >From a697f9e9442d96d3eda228b825dd8e8e06206c03 Mon Sep 17 00:00:00 2001
> From: "Jose E. Marchesi"
> Date: Wed, 29 Nov 2023 09:16:48 +0100
> Subject: [PATCH] testsuite: move gcc.c-torture/compile/libcal
> On Wed, Nov 29, 2023 at 09:20:55AM +0100, Jose E. Marchesi wrote:
>> OK to the patch below?
>>
>> >From a697f9e9442d96d3eda228b825dd8e8e06206c03 Mon Sep 17 00:00:00 2001
>> From: "Jose E. Marchesi"
>> Date: Wed, 29 Nov 2023 09:16:48 +0100
>> Subject: [PATCH] testsuite: move gcc.c-torture/comp
11 matches
Mail list logo