RE: [Linaro-TCWG-CI] gcc-15-4672-gdf4af89bc3e: Failure on arm

2024-11-04 Thread Li, Pan2
The docker multi-isa doesn't work well here, I will apply an account from 
compiler farm...

Pan

-Original Message-
From: Li, Pan2 
Sent: Wednesday, October 30, 2024 9:32 AM
To: Maxim Kuvyrkov 
Cc: Sam James ; gcc-regress...@gcc.gnu.org; Jeff Law 
; juzhe.zh...@rivai.ai; kito.ch...@gmail.com; Linaro 
ToolChain ; rd...@ventanamicro.com
Subject: RE: [Linaro-TCWG-CI] gcc-15-4672-gdf4af89bc3e: Failure on arm

Thanks, let me have a try first and will back to you if still cannot reproduce 
this.

Pan

-Original Message-
From: Maxim Kuvyrkov  
Sent: Wednesday, October 30, 2024 7:39 AM
To: Li, Pan2 
Cc: Sam James ; gcc-regress...@gcc.gnu.org; Jeff Law 
; juzhe.zh...@rivai.ai; kito.ch...@gmail.com; Linaro 
ToolChain ; rd...@ventanamicro.com
Subject: Re: [Linaro-TCWG-CI] gcc-15-4672-gdf4af89bc3e: Failure on arm

> On Oct 27, 2024, at 20:40, Li, Pan2  wrote:
> 
> I see, this error may require bootstrap build. There is no aarch64 machine 
> currently. Let me try to find one somewhere.
> 

You could use one of aarch64 machines in GCC's compiler farm.  If that doesn't 
work -- send me a private email and I'll create a docker container for you on 
one of Linaro machines.

--
Maxim Kuvyrkov
https://www.linaro.org

> Pan
> 
> -Original Message-
> From: Sam James  
> Sent: Sunday, October 27, 2024 3:37 PM
> To: Li, Pan2 
> Cc: gcc-regress...@gcc.gnu.org; jeffreya...@gmail.com; juzhe.zh...@rivai.ai; 
> kito.ch...@gmail.com; linaro-toolchain@lists.linaro.org; 
> rd...@ventanamicro.com
> Subject: RE: [Linaro-TCWG-CI] gcc-15-4672-gdf4af89bc3e: Failure on arm
> 
> It's not possible to do a profiledbootstrap via cross. It might be
> possible for the Linaro CI to extract the bad preprocessed source and
> share the options used to build it (options at least should be in the
> log) but that won't help if the compiler is miscompiled...
> ___
> linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
> To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org

___
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org


Re: [Linaro-TCWG-CI] gcc patch #99988: Failure on aarch64

2024-11-04 Thread Christophe Lyon
On Fri, 1 Nov 2024 at 15:31, Andi Kleen  wrote:
>
> On Fri, Nov 01, 2024 at 06:57:21AM +, ci_not...@linaro.org wrote:
> > Dear contributor, our automatic CI has detected problems related to your 
> > patch(es).  Please find some details below.  If you have any questions, 
> > please follow up on linaro-toolchain@lists.linaro.org mailing list, 
> > Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain 
> > developer on the usual project channel.
>
> All the logs seem to be truncated?
> What kind of failure is this? Is it a problem on the builder?
>
> Thanks,
> -Andi
>
Hi,

I opened the build logs from
https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/13759/artifact/artifacts/artifacts.precommit/
under 04-build_abe-gcc (which is the last "real" build step, where the
failure is) and in console.log, I noticed this:
make: *** No rule to make target 'f95*.fda', needed by
'/home/tcwg-build/workspace/tcwg_gnu_4/abe/builds/destdir/aarch64-unknown-linux-gnu/share/man/man1/gfortran.1'.
Stop.
make: Leaving directory
'/home/tcwg-build/workspace/tcwg_gnu_4/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/gcc-gcc.git~master-stage2/gcc'

HTH,

Christophe

>
> >
> > We understand that it might be difficult to find the necessary logs or 
> > reproduce the issue locally. If you can't get what you need from our CI 
> > within minutes, let us know and we will be happy to help.
> >
> > In gcc_build master-aarch64 after:
> >
> >   | gcc patch https://patchwork.sourceware.org/patch/99988
> >   | Author: Andi Kleen 
> >   | Date:   Thu Oct 31 16:19:16 2024 -0700
> >   |
> >   | [PATCH] Enable autofdo bootstrap for lto/fortran
> >   |
> >   | When autofdo bootstrap support was originally implemented there were
> >   | issues with the LTO bootstrap, that is why it wasn't enabled
> >   | for them. I retested this now and it works on x86_64-linux.
> >   | ... 10 lines of the commit log omitted.
> >   | ... applied on top of baseline commit:
> >   | f8ae2cce23fc Support Intel AMX-MOVRS
> >
> > Results changed to
> > # reset_artifacts:
> > -10
> > # true:
> > 0
> > # build_abe gcc:
> > # FAILED
> >
> > From
> > # reset_artifacts:
> > -10
> > # true:
> > 0
> > # build_abe gcc:
> > 1
> >
> > The configuration of this build is:
> > *CI config* tcwg_gcc_build master-aarch64
> > *configure and test flags:* --target aarch64-linux-gnu
> >
> > -8<--8<--8<--
> > The information below can be used to reproduce a debug environment:
> >
> > Current build   : 
> > https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/13759/artifact/artifacts
> > Reference build : 
> > https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2726/artifact/artifacts
> >
> > Warning: we do not enable maintainer-mode nor automatically update
> > generated files, which may lead to failures if the patch modifies the
> > master files.
>
> ___
> linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
> To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
___
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org