ci_not...@linaro.org writes:
> 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-toolch...@lists.linaro.org
> mailing list, Libera's #linaro-tcwg channel, or ping your favo
"Jiang, Haochen" writes:
> Ping for this thread.
>
> Any ideas? If no, I will change the generated info with command following
> if we take r15-1643 as example and see if it is clearer:
>
> head -26 makelog.r15-1643.x86_64.native | tail -7 > 1.log;
> grep -E "(error:|Error)" makelog.r15-1643.x86_
Hi!
For future reports, would it be possible to change the grep to something
like:
grep -E "(error:|Error)" or just grep -rsin "error" -w or something.
This would allow catching the actual compile error in libbacktrace if
it's not going to fit in the last N lines from make.
(Not needed here as
FAIL: gcc.dg/pr116003.c (test for excess errors)
Excess errors:
/home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:4:1:
sorry, unimplemented: '_BitInt(5)' is not supported on this target
/home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/g
This is https://gcc.gnu.org/PR117177 which has a patch posted by Jakub
already at https://inbox.sourceware.org/gcc-patches/ZxArjATvc%2FnI6YiO@tucnak/.
Christophe Lyon writes:
> On Sat, 26 Oct 2024 at 14:17, Sam James via Gcc-regression
> wrote:
>>
>> ci_not...@linaro.org writes:
>>
>> > Dear contributor, our automatic CI has detected problems related to
>> > your patch(es). Please find some deta
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...
ci_not...@linaro.org writes:
> 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-toolch...@lists.linaro.org
> mailing list, Libera's #linaro-tcwg channel, or ping your favo
"Li, Pan2" writes:
> No response from the compiler farm.
>
> But due to some more discussion for the simplification on SAT, this patch is
> reverted. Thus I bet this build error should be gone
> up to a point. Please feel free to ping me if any issues.
Take Maxim up on their offer, I think? It'
ci_not...@linaro.org writes:
> 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-toolch...@lists.linaro.org
> mailing list, Libera's #linaro-tcwg channel, or ping your favo
I filed PR116845 for this.
I think this testcase was accidentally included in
r15-5359-gcc33f880e553d1 but this problem can be ignored, as it is now
fixed by r15-5361-gaac5c57ee16723.
(TL;DR: just a git snafu and the problem is resolved AFAICT.)
This is https://sourceware.org/PR32366.
This is definitely https://gcc.gnu.org/PR118409 (indeed the ifcombine
change). We had PR118417 too which I suspect is the same.
This is being worked on at
https://inbox.sourceware.org/libc-alpha/328b6145af0d5c1d2c3fc5ef44cb7b747173d021.1736478704.git@gentoo.org/.
See also
https://inbox.sourceware.org/libc-alpha/fcdbc863-3ad7-de56-6076-85948d030...@redhat.com/.
thanks,
sam
"haochen.jiang" writes:
> On Linux/x86_64,
>
> e96e1bb69c7b46db18e747ee379a62681bc8c82d is the first bad commit
> commit e96e1bb69c7b46db18e747ee379a62681bc8c82d
> Author: Jason Merrill
> Date: Fri Feb 14 10:53:01 2025 +0100
>
> c++: extended temp cleanups [PR118856]
>
> caused
>
> FAIL: g
ci_not...@linaro.org writes:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find
> some details below.
>
> In arm-eabi cortex-m33 hard, after:
> | commit gcc-15-9030-g78e0cf06c81
> | Author: Sam James
> | Date: Sat Mar 29 21:09:25 2025 +
ci_not...@linaro.org writes:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find
> some details below.
>
> In gcc_check master-aarch64, after:
> | commit gcc-15-8956-ge90d6c2639c
> | Author: Sam James
> | Date: Thu Mar 27 00:21:43 2025 +0
"haochen.jiang" writes:
> On Linux/x86_64,
>
> de1c734a8ae034c92f485e7f58b7fcb1c921ecd2 is the first bad commit
> commit de1c734a8ae034c92f485e7f58b7fcb1c921ecd2
> Author: Martin Jambor
> Date: Mon Apr 14 14:21:15 2025 +0200
>
> ipa-cp: Make propagation of bits in IPA-CP aware of type conv
This builder uses --with-arch=native. The (a) difference starts at x86-64-v3:
$ diff -u <(gcc -O2 -fdump-tree-forwprop1-details=- -O2 gcc.dg/pr78408-3.c -c
-march=x86-64-v2) <(gcc -O2 -fdump-tree-forwprop1-details=- -O2
gcc.dg/pr78408-3.c -c -march=x86-64-v3)
--- /dev/fd/63 2025-04-19 01:27:31
20 matches
Mail list logo
