ter/glibc/sha1/620f0730f311635cd0e175a3ae4d0fc700c76366/tcwg_gnu_native_check_gdb/master-aarch64/reproduction_instructions.txt
Full commit :
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=620f0730f311635cd0e175a3ae4d0fc700c76366
--
Maxim Kuvyrkov
https://www.linaro.org
Hi Yury,
That's correct. And Peter Maydell has even posted a QEMU fix for this -- see
https://linaro.atlassian.net/browse/GNU-1642 .
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 28, 2025, at 20:35, Yury Khrustalev wrote:
>
> On Thu, Jul 24, 2025 at 10:42:41AM
naro.org <http://linaro.org/> servers to gitlab.com
<http://gitlab.com/>, but we haven't updated the links yet. Sorry!
>
>> Please let us know if you have a fix.
>
> I should have a fix: the attached
> "Adjust 'libgomp.c++/target-cdt
Hi Sam,
Thanks for looking into this.
Hi Adhemerval,
Would you please look into how glibc should handle this?
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jun 19, 2025, at 04:24, Sam James wrote:
>
> Could you file a glibc bug for this please? It needs some analysis to
sve_vls-lto-lld-bisect/176/artifact/artifacts/build-first_bad/00-sumfiles/ninja.log.xz
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On May 24, 2025, at 02:20, Slava Zakharin wrote:
>
> Hello,
>
> I think there was an error in bisecting these regressions. I can
-aarch64-Ofast-sve_vls-lto-lld-build/1756/artifact/artifacts/00-sumfiles/llvm-test-suite.1.json.xz/*view*/
--
Maxim Kuvyrkov
https://www.linaro.org
> On Mar 15, 2025, at 04:39, Ricardo Jesus wrote:
>
> Hi Maxim,
>
> Thank you very much for your offer, and sorry for the delay gettin
Hi Ricardo,
I can test your PR. Please send me the link.
Thanks,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Mar 10, 2025, at 21:50, Ricardo Jesus wrote:
>
> Hi Maxim,
>
> Thank you very much for confirming!
>
> I think I was able to identify the problem. I'
Hi Ricardo,
Thanks for looking into this!
The tests are run on AWS Graviton3 hardware (m7g AWS instance), which seems to
match -msve-vector-bits=256.
Let me know if you need any help in reproducing the failures.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Mar 8, 2025, at
0checklist
HTH,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 21, 2025, at 05:36, James K. Lowden wrote:
>
> On Thu, 20 Feb 2025 15:05:48 +1300
> Maxim Kuvyrkov wrote:
>
> Hi Maxim,
>
> Thank you kindly for your helpful reply. Despite running my own mailserv
st, this is where testsuite xfails would have been; need to
remove this link.
>
> Current build :
> https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/artifact/artifacts
> Reference build :
> https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3164
> On Feb 12, 2025, at 18:54, H.J. Lu wrote:
>
> On Wed, Feb 12, 2025 at 1:48 PM Maxim Kuvyrkov
> wrote:
>>
>> Hi H.J.,
>>
>> This particular CI pipeline builds glibc using system compiler in Ubuntu
>> 22.04 environment. So GCC version is GCC 11.4 .
Hi H.J.,
This particular CI pipeline builds glibc using system compiler in Ubuntu 22.04
environment. So GCC version is GCC 11.4 .
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 12, 2025, at 18:27, H.J. Lu wrote:
>
> On Wed, Feb 12, 2025 at 1:17 PM wrote:
>>
>
rm/arm.md:74
... to ...
>> | FAIL: gcc.dg/pr41123.c (internal compiler error: in gen_movsf, at
>> config/arm/arm.md:7450)
I don't see any immediate reason why your patch would cause a test to get
renamed, so we'll investigate.
--
Maxim Kuvyrkov
https://www.linaro.org
>
Hi Thiago,
Great job tracking down such an obscure bug!
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Dec 28, 2024, at 11:13, Thiago Jung Bauermann
> wrote:
>
> Thiago Jung Bauermann writes:
>
>> Maxim Kuvyrkov writes:
>>
>>> Thiago, would yo
Oh, and for AArch64 as well:
https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allyesconfig-build/218/artifact/artifacts/06-build_linux/console.log.xz
--
Maxim Kuvyrkov
https://www.linaro.org
> On Dec 20, 2024, at 17:57, Maxim Kuvyrkov wrote:
>
> Hi Nick,
>
> Yo
Hi Nick,
Your patch causes kernel build failure for 32-bit ARM. See build log at [1].
Is this expected?
Thanks!
[1]
https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-mainline-allnoconfig-build/183/artifact/artifacts/06-build_linux/console.log.xz
--
Maxim Kuvyrkov
https://www.linaro.org
Thanks,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Dec 19, 2024, at 12:44, Thiago Jung Bauermann
> wrote:
>
> Hello,
>
> Maxim Kuvyrkov writes:
>
>> Thiago, would you please investigate this?
>
> Ok, on it.
>
>> Start with confirming that the test
Hi Jan,
Sorry, this has slipped through cracks.
The failures are reproducible and are still present in the latest test run.
Thiago, would you please investigate this? Start with confirming that the
tests pass with current mainline with Jan's patch reverted.
Thank you!
--
Maxim Kuv
Hi Alexey,
It seems your patch below causes build failure of 654.roms_s for "-O3 -flto" on
aarch64-linux-gnu. Has this been reported already?
Let me know if not, and I'll help with the reporting and reproduction.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov
Hi Sergei,
It seems your patch below breaks build of several SPEC CPU2017 benchmarks on
32-bit ARM.
Could you please investigate? Please let me know if you need any assistance in
reproducing build failures.
Thanks,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov 21, 2024, at 20
-ld:
tmpdir/zlibbegin.o: final close failed: invalid operation
collect2: error: ld returned 1 exit status
Does this help?
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov 20, 2024, at 03:12, Jan Beulich wrote:
>
> On 19.11.2024 05:29, ci_not...@linaro.org wrote:
>> D
struction to reproduce the build :
https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/sha1/40c8938ff8447fc46bd2aa1605e3147cc38ffb8d/tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays/reproduction_instructions.txt
Full commit :
https://github.com/llvm/llvm-pr
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.g
Hi Abdul,
Sorry for the delay.
Indeed, the report seems wrong. I see the test failing in the baseline
results, but the xfails file generated from those results does not include the
test. We will investigate.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Oct 29, 2024, at 11
at -mcpu=unset has been added to the test name).
>
> That's not a regression, it's a simple FAIL->FAIL
Yes, that's correct.
Unfortunately, when a FAILed test is renamed, it appears as a new failure in
the result comparison, and it would be difficult to automatically ign
Hi Mark,
I believe this was caused by Christophe's binutils patch, which has now been
fixed.
Christophe, please correct me if I'm wrong.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Sep 12, 2024, at 00:34, Mark Wielaard wrote:
>
> Hi,
>
> ci_not...@l
tifacts/06-build_linux/console.log.xz
.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Sep 2, 2024, at 19:11, 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 an
Hi Julian,
Your patch below breaks Flang build [on aarch64]. Would you please investigate?
The interesting log is at
https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/174/artifact/artifacts/03-build_llvm/console.log.xz
.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
>
itsu-Fortran-0153_0237.test
> FAIL: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0234.test
> FAIL: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0235.test
>
> ... and 5 more entries
Please investigate, and let me know if you need any help in reproducing or
troublesho
.
Let me know if you need any assistance in troubleshooting this.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 29, 2024, at 11:37, Tobias Burnus wrote:
>
> Hi all,
>
> what should I do with this – I have no idea what artifacts are nor is it
> clear to me w
for excess errors)
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 28, 2024, at 09:28, 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,
> plea
Hi Christudasan,
Please ignore this report; it wasn't supposed to be posted publicly.
We are setting up additional testing of Flang, and this CI is in testing.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 26, 2024, at 23:02, ci_not...@linaro.org wrote:
>
> De
++.dg/musttail6.C (test for excess errors)
It wasn't included in the report due to typo in the scripts.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 26, 2024, at 19:38, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems r
Hi Jason,
The regression is ...
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: g++.dg/abi/arm_rtti1.C -std=gnu++26 scan-assembler _ZNKSt9type_infoeqERKS_
It wasn't included in the report due to typo in the scripts.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> O
f you need any assistance in troubleshooting the FAIL.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 27, 2024, at 20:19, Simon Marchi wrote:
>
> On 2024-07-27 03:34, ci_not...@linaro.org wrote:
>> Dear contributor, our automatic CI has detected problems related
problem is introduced and then fixed in the same patch series. My
understanding is that all GNU toolchain projects strive to be "correct" at
every revision. This, of course, is not an issue if you plan to squash your
changes before merging them.
Does this answer your question?
T
be guarded on the target supporting vectorization? I.e.,
maybe add
// { dg-require-effective-target vect_int }
?
[1] https://linaro.atlassian.net/browse/GNU-1265
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jun 21, 2024, at 19:03, Matthias Kretz via Gcc-regression
> wrote:
>
>
Hi David,
Your patch below breaks linux kernel build on 32-bit ARM -- see [1]. Would you
please investigate?
[1]
https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-build/144/artifact/artifacts/06-build_linux/console.log.xz
Thanks!
--
Maxim Kuvyrkov
https
post-commit and pre-commit tests with the same flags -- the default
ones. I'm guessing the -pedantic-errors is coming from
gcc/testsuite/gfortran.dg/dg.exp via DEFAULT_FFLAGS.
Does this answer your question?
King regards,
--
Maxim Kuvyrkov
https://www.linaro.org
les. Also, some patches
fail to apply to current mainline, so we skip them. See [2] for more details.
[1] https://patchwork.sourceware.org/project/gcc/list/?series=33005
[2] https://patchwork.sourceware.org/project/gcc/list/
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
>
> Qin
your question?
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Apr 22, 2024, at 17:33, Qing Zhao wrote:
>
> Hi,
>
> I am wondering why I got the following message?
>
> I only sent patch review request to
> gcc-patc...@gcc.gnu.org<mailto:gcc-patc...@gcc.gn
it~master-stage2/armv8l-unknown-linux-gnueabihf/./libatomic/.libs
-lm -o ./pr113363.exe
It should run on any stock ubuntu-22.04 rootfs for armhf architecture.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Apr 10, 2024, at 18:31, Paul Richard Thomas
> wrote:
>
> Hi ther
Hi Christina,
This is false-positive report -- see
https://sourceware.org/bugzilla/show_bug.cgi?id=31575 for details.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Mar 29, 2024, at 10:22, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems relate
Hi Kevin,
This is false-positive report -- see
https://sourceware.org/bugzilla/show_bug.cgi?id=31575 for details.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Mar 29, 2024, at 10:48, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems relate
Hi Abdul,
Hi Nils,
This is false-positive report -- see
https://sourceware.org/bugzilla/show_bug.cgi?id=31575 for details.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Mar 29, 2024, at 10:52, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems r
Hi Gustavo,
This is false-positive report -- see
https://sourceware.org/bugzilla/show_bug.cgi?id=31575 for details.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Mar 29, 2024, at 10:54, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems relate
Hi Richard,
Heads up, our benchmarking CI flagged your commit to cause 23% regression in
549.fotonik3d_r on Cortex-A57 at -O3.
Do you have internal benchmarks for this change?
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Mar 24, 2024, at 03:43, ci_not...@linaro.org wr
> On Mar 11, 2024, at 20:52, Jonathan Wakely wrote:
>
> On Mon, 11 Mar 2024 at 16:38, Maxim Kuvyrkov
> wrote:
>>
>>> On Jan 30, 2024, at 23:03, ci_not...@linaro.org wrote:
>>>
>>> Dear contributor, our automatic CI has detected problems rela
> On Mar 12, 2024, at 00:14, Tom Tromey wrote:
>
>>>>>> Maxim Kuvyrkov writes:
>
>>> | commit gdb-14-branchpoint-1356-g7737b133640
>>> | Author: Tom Tromey
>>> | Date: Tue Jan 9 11:47:17 2024 -0700
>>> |
>>> |
patch seems to regress the above 3 tests for all 32-bit ARM targets (see
[1]). Would you please check if the regressions can be avoided?
For reference, here are configure options we use for arm-linux-gnueabihf
cross-toolchain: [2].
[1] https://linaro.atlassian.net/browse/GNU-1140
[2]
https://c
_cat'
warning: RTTI symbol not found for class 'main::custom_cat'
got: $36 = warning: RTTI symbol not found for class 'main::custom_cat'
FAIL: libstdc++-prettyprinters/cxx11.cc print ecmiaow
===
Which way should I dig -- GDB or libstdc++? Does this look like libstdc++
te
sts now consistently failing across all 32-bit ARM
configurations that we track (see [1]).
As an example, our configure options for arm-linux-gnueabihf that show the
failure are at [2].
[1] https://linaro.atlassian.net/browse/GNU-1132
[2]
https://ci.linaro.org/job/tcwg_gcc_check--master-arm-bui
value => 126, another_value => 12, color => red)
(gdb) FAIL: gdb.ada/scalar_storage.exp: print V_BE
===
Any idea what can be causing this?
This failure happens in CI configurations where we track tip-of-trunk GCC.
[1]
https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch6
> On Feb 21, 2024, at 12:44, Tiezhu Yang wrote:
>
>
>
> On 02/21/2024 03:16 PM, Maxim Kuvyrkov wrote:
>>> On Feb 21, 2024, at 05:46, Tiezhu Yang wrote:
>>>
>>>
>>>
>>> On 02/21/2024 03:52 AM, ci_not...@linaro.org wrote:
>>&g
1]
https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/1725/artifact/artifacts/artifacts.precommit/sumfiles/xfails.xfail/*view*/
--
Maxim Kuvyrkov
https://www.linaro.org
___
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Hi Richard,
This is a false positive. We had a bit of instability in our CI yesterday, and
it should be all fixed now.
Thanks,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 23:00, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected
o
open tst-gnu2-tls2mod2.so
close tst-gnu2-tls2mod0.so
close tst-gnu2-tls2mod1.so
open tst-gnu2-tls2mod0.so
open tst-gnu2-tls2mod1.so
Didn't expect signal from child: got `Segmentation fault'
===
Let me know if you need any help investigating this.
Thanks!
--
Maxim Kuvyrkov
https://www.li
Hi Nathaniel,
We enabled guality tests in our CI setup yesterday, and this is part of the
fallout. Please ignore this report.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 09:55, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has
Hi H.J.,
We enabled guality tests in our CI setup yesterday, and this is part of the
fallout. Please ignore this report.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 09:36, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has
Hi Andrew,
We enabled guality tests in our CI setup yesterday, and this is part of the
fallout. Please ignore this report.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 09:39, Andrew Pinski (QUIC)
> wrote:
>
> This does not make sense at all. Th
Hi Robin,
Please ignore this report. We had a bit of instability in CI testing yesterday.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 09:11, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems related to your
> patch(es).
Hi Jakub,
Please ignore this. I'm going to investigate, but most likely this is due to
instability of guality tests.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 14, 2024, at 01:43, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems r
pr41447-1.c -O0 execution test
>
> Running gcc:gcc.dg/ipa/ipa.exp ...
> UNRESOLVED: gcc.dg/ipa/iinline-4.c scan-ipa-dump inline "hooray4[^\\n]*inline
> copy in test4"
> UNRESOLVED: gcc.dg/ipa/iinline-4.c scan-ipa-dump inline "hooray1[^\\n]*inline
> copy in test1&qu
Hi Richard,
Ack. Thanks for the follow up!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Feb 12, 2024, at 18:46, Richard Earnshaw
> wrote:
>
> I think all of these actually fall under
>
> "I suspect there are still some further issues to address here, since
&
Hi Arjun,
This is not a real regression. We have a problem in our CI that causes
container tests fail for 32-bit ARM. Therefore, any new container test shows
up as a regression.
We are working on fixing this.
Thanks,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jan 31, 2024, at 06
1.xz
.
Hi Thiago,
Would you please investigate whether ending up in pthread_join() is
expected/reasonable for 32-bit ARM? In other words, whether we have a GDB bug
exposed by staticthreads.exp or the testcase needs to be generalized a bit.
Thank you,
--
Maxim Kuvyrkov
https://www.linaro.or
> On Jan 25, 2024, at 19:04, Guinevere Larsen wrote:
>
> On 25/01/2024 10:10, Maxim Kuvyrkov wrote:
>>> On Jan 25, 2024, at 04:08, ci_not...@linaro.org wrote:
>>>
>>> Dear contributor, our automatic CI has detected problems related to your
>>> patch
0xf7eadb04 in ?? ()
7LWP 4764470xf7eadb04 in ?? ()
(gdb) FAIL: gdb.threads/threadcrash.exp: test_gcore: $thread_count == 7
===
Could you please look into fixing the testcase? [I assume "LWP" output is
expected, but I'm not an expert in GDB.]
Thanks!
--
Maxim
> On Jan 19, 2024, at 17:31, H.J. Lu wrote:
>
> On Thu, Jan 18, 2024 at 11:15 PM Maxim Kuvyrkov
> wrote:
>>
>> Hi H.J.,
>>
>> Did the email below made it to your inbox? I wonder if some of our
>> precommit CI emails are not reaching developer
Hi H.J.,
Did the email below made it to your inbox? I wonder if some of our precommit
CI emails are not reaching developers.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jan 10, 2024, at 02:24, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has
.
>
> Please let me know if the issue is something else and I can take
> another look.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
>
> Yours,
> Nathaniel.
>
> On Thu, Jan 18, 2024 at 07:12:12AM +, ci_not...@linaro.org wrote:
>> Dear contributor, our
Hi Ian,
[Apologies for late reply, your email got caught in moderation queue.]
Do you still need help in reproducing the build?
On our side we are working to include configure/make lines into reports to
simplify reproduction.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On
Hi Lehua,
[Apologies for late reply, your email got caught in moderation queue.]
Do you still need help in reproducing the build?
On our side we are working to include configure/make lines into reports to
simplify reproduction.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On
regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov 29, 2023, at 19:20, Rainer Orth wrote:
>
> 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
d.
> In this case, is GCC configured to include neon by default? If so then the
> testcase needs to be updated to add an option to disable neon.
Hi Andrew,
We'll soon have configure and make info in the report.
> If not, then someone else will need to look into why the tes
://linaro.atlassian.net/browse/GNU-1084).
Would you please investigate this? And don't hesitate to ask for our
assistance in reproducing this.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Dec 21, 2023, at 03:20, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic C
Hi kernel folks,
It seems a new gcc patch uncovered a potential problem in btrfs code, see the
warning/error below.
Does this look like a legit kernel problem?
--
Maxim Kuvyrkov
https://www.linaro.org
> On Dec 22, 2023, at 06:54, ci_not...@linaro.org wrote:
>
> Dear contrib
lated
> to my patch.
Hi Tamar,
Linaro benchmarking builds the whole sysroot with the "new" compiler, including
glibc. It may be interesting to double-check code-gen differences on glibc's
exp() and make sure they are no obvious bad choices.
--
Maxim Kuvyrkov
https://www.linaro.
> On Nov 1, 2023, at 22:22, Nick Desaulniers wrote:
>
> On Wed, Nov 1, 2023 at 11:02 AM Maxim Kuvyrkov
> wrote:
>>
>> Hi Nick,
>> Hi Nathan,
>>
>> I don't see mistakes from CI here. Are you using tip-of-trunk LLVM?
>>
>> This repor
-bootstrap_profiled/details.txt
Regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Nov 1, 2023, at 15:46, 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,
> plea
g_kernel--llvm-master-arm-mainline-allmodconfig-build/110/artifact/artifacts/06-build_linux/console.log.xz
[2]
https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-mainline-allmodconfig-build/111/artifact/artifacts/06-build_linux/console.log.xz
--
Maxim Kuvyrkov
https://www.linaro.org
> On N
.mcf_r:[.] price_out_impl
Both of these are for 32-bit ARM, but AArch64 also has code-speed and code-size
regressions.
Let me know if you need any assistance in reproducing these problems.
[1] https://linaro.atlassian.net/browse/LLVM-1001
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
Hi Arjun,
Please ignore this report. We had a new machine added to the testing pool, and
it behaved differently than the others.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Oct 4, 2023, at 22:30, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected
Hi Joe,
Please ignore this report. We had a new machine added to the testing pool, and
it behaved differently than the others.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Oct 4, 2023, at 22:32, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problem
Hi Siddhesh,
Please ignore this report. We had a new machine added to the testing pool, and
it behaved differently than the others.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Oct 4, 2023, at 22:33, ci_not...@linaro.org wrote:
>
> Dear contributor, our automatic CI has detected
Hi Ashu,
Go ahead, this is the right place to ask.
--
Maxim Kuvyrkov
https://www.linaro.org
> On Sep 19, 2023, at 11:32, Ashu Jain wrote:
>
> We are installing SDK we need some details regarding linaro toolchain
> ___
> linaro-toolcha
Cauldron presentation. "Green/Red" in patchwork mean the usual PASS/FAIL.
It's only in post-commit CI in jenkins interface green and red mean something
different.
--
Maxim Kuvyrkov
https://www.linaro.org
___
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Oh, I see this is tracked in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111544 .
--
Maxim Kuvyrkov
https://www.linaro.org
> On Sep 27, 2023, at 13:47, Maxim Kuvyrkov wrote:
>
> Hi Patrick,
>
> Did you already get any bug reports for gcc-14-4111-g6e92a6a2a72 ?
>
> I
Hi Patrick,
Did you already get any bug reports for gcc-14-4111-g6e92a6a2a72 ?
In our benchmarking we see that 483.xalancbmk (from SPEC CPU2006) fails to
build on 32-bit ARM. Let me know if you need any help in reproducing and
troubleshooting this.
Thanks!
--
Maxim Kuvyrkov
https
ew*/
[2] https://linaro.atlassian.net/browse/GNU-942
--
Maxim Kuvyrkov
https://www.linaro.org
>
> Thanks,
> Andrew
>
>>
>> Thanks,
>> Andrew
>>
>>
>> From: ci_not...@linaro.org
>> Sent: Saturd
ibc_check--master-aarch64-build/lastStableBuild/artifact/artifacts/sumfiles/xfails.xfail/*view*/
[3] https://git.linaro.org/ci/dockerfiles.git/tree/tcwg-base/Dockerfile.in
--
Maxim Kuvyrkov
https://www.linaro.org
> On Sep 15, 2023, at 10:16, Andreas Schwab wrote:
>
> On Sep 14 2023, S
> On Aug 25, 2023, at 21:02, Florian Weimer wrote:
>
> * Maxim Kuvyrkov:
>
>>> On Aug 25, 2023, at 19:18, ci_not...@linaro.org wrote:
>>>
>>> Dear contributor, our automatic CI has detected problems related to your
>>> patch.
>>>
ttps://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/597/artifact/artifacts/artifacts.precommit/00-sumfiles/tests.log.1.xz
.
Regards,
--
Maxim Kuvyrkov
https://www.linaro.org
>
> === Results Summary ===
>
>
>
> -8<--8&
Hi Richard,
Your patch below ICEs on aarch64-linux-gnu. Should reproduce easily on native
or cross aarch64-linux-gnu build.
Let me know if you need any assistance in reproducing this.
Thanks,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Aug 24, 2023, at 22:03, ci_not...@linaro.org wr
> On Aug 21, 2023, at 15:14, Julian Brown wrote:
>
> On Sat, 19 Aug 2023 10:47:45 +0400
> Maxim Kuvyrkov wrote:
>
>> Hi Julian,
>>
>> Your patch series causes regressions on aarch64-linux-gnu. Would you
>> please investigate?
>>
>> Let me k
--master-aarch64-precommit/1602/artifact/artifacts/artifacts.precommit/00-sumfiles/
--
Maxim Kuvyrkov
https://www.linaro.org
> On Aug 19, 2023, at 08:37, ci_not...@linaro.org wrote:
>
> [Linaro-TCWG-CI] FAIL: 6 regressions after gcc commit:
> basepoints/gcc-14-3331-gcddc26e0274 a
Hi Julian,
Your patch series causes regressions on aarch64-linux-gnu. Would you please
investigate?
Let me know if you need any assistance in reproducing these.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Aug 19, 2023, at 09:32, ci_not...@linaro.org wrote:
>
> [Linar
Hi Stamatis,
Let us know if you need any help in troubleshooting the failures in
https://patchwork.sourceware.org/project/gcc/list/?series=23558 .
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Aug 18, 2023, at 01:13, ci_not...@linaro.org wrote:
>
> [Linaro-TCWG-CI
Hi Aaron,
This email from April got caught in moderation. I believe the problem with
Linaro bots was already addressed.
I'll try to monitor moderation requests better.
Regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Apr 3, 2023, at 23:05, Aaron Ballman wrote:
>
>
Thanks, Andrzej!
Hi Antoine, would you please take a look at this?
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On May 15, 2023, at 22:55, Andrzej Warzynski
> wrote:
>
> Hi,
>
> Has anyone noticed that https://lab.llvm.org/buildbot/#/builders/198
> (
1 - 100 of 261 matches
Mail list logo
