On Mon, Jun 17, 2024 at 07:01 PM, Randy MacLeod wrote:
>
> Yash and Sundeep have updated and tested 1.76, 1.77, 1.78, 1.79 locally
> and have not seen any problems. As you know, the situation is...
Rust 1.79 released recently and we've not yet updated that. Until 1.78 release
we've tested.
We
bject file names containing a unique hashmap id.
The hashmap addition to generated files is reverted here.
Signed-off-by: Sundeep KOKKONDA
Signed-off-by: Yash Shinde
---
...epro-issue-fix-with-cc-crate-hashmap.patch | 59 +++
meta/recipes-devtools/rust/rust-source.inc| 1 +
On 03-Jun-24 20:37, Sundeep KOKKONDA via lists.openembedded.org wrote:
On 03-Jun-24 20:20, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the
sender and know the content is safe.
Wait, did
-r0_amd64.deb is generated and the binaries are
identical.
Alex
On Mon, 3 Jun 2024 at 16:46, Sundeep KOKKONDA via
lists.openembedded.org
wrote:
From: Sundeep KOKKONDA
The rustdoc binaries are differed on their .llvm. suffixes between the
builds.
This is a test patch to verify the PGO effect
From: Sundeep KOKKONDA
The rustdoc binaries are differed on their .llvm. suffixes between the
builds.
This is a test patch to verify the PGO effect on rustdoc binaries. The issue
discussion is here:
https://internals.rust-lang.org/t/rustdoc-binary-is-not-reproducible/20027
Signed-off
On 01-Jun-24 15:57, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Fri, 31 May 2024 at 15:28, Richard Purdie via
lists.openembedded.org
wrote:
Regression testing is done and below are the results:
Before glibc update:
-
Recipe | Passed | Failed | Skipped |
-
glibc | 5037 | 123 | 156 |
glibc-user | 4858
Regression testing is done and below are the results:
Before glibc update:
-
Recipe | Passed | Failed | Skipped |
-
glibc | 5041 | 123 | 156 |
glibc-user | 4854
Regression testing is done and no regressions found.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199520):
https://lists.openembedded.org/g/openembedded-core/message/199520
Mute This Topic: https://lists.openembedded.org/mt/106156829/21656
Group
Regression testing is done and no regressions found.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199519):
https://lists.openembedded.org/g/openembedded-core/message/199519
Mute This Topic: https://lists.openembedded.org/mt/106156744/21656
Group
From: Sundeep KOKKONDA
c7c3f5bf80 LoongArch: Fix undefined `__memset_aligned` reference in ld.so
linking.
32969a2b36 socket: Add new test for connect
2db79c96ba libsupport: Add xgetpeername
ab4ef4421f x86_64: Fix missing wcsncat function definition without multiarch
(x86-64-v4)
97bb89668d
From: Sundeep KOKKONDA
Below commits on binutils-2.42 stable branch are updated.
6224493e457 Re: PR26978, Inconsistency for strong foo@v1 and weak foo@@v1
d125f967537 hppa: Implement PA 2.0 symbolic relocations for long displacements
884fb5373a1 x86/APX: Remove KEYLOCKER and SHA promotions from
From: Sundeep KOKKONDA
Below commits on glibc-2.39 stable branch are updated.
c7c3f5bf80 LoongArch: Fix undefined `__memset_aligned` reference in ld.so
linking.
32969a2b36 socket: Add new test for connect
2db79c96ba libsupport: Add xgetpeername
ab4ef4421f x86_64: Fix missing wcsncat function
From: Sundeep KOKKONDA
Below commits on binutils-2.42 stable branch are updated.
6224493e457 Re: PR26978, Inconsistency for strong foo@v1 and weak foo@@v1
d125f967537 hppa: Implement PA 2.0 symbolic relocations for long displacements
884fb5373a1 x86/APX: Remove KEYLOCKER and SHA promotions from
From: Sundeep KOKKONDA
Patch updated with upstream fix.
https://github.com/rust-lang/rust/pull/121959/commits/a9a979839bbdfec48c75d618ab0dce8a953589b8
Signed-off-by: Sundeep KOKKONDA
---
.../files/repro-issue-fix-with-v175.patch | 37 +--
1 file changed, 25 insertions
On Tue, Jan 2, 2024 at 02:54 PM, Alex Kiernan wrote:
>
> Closing this off - for whatever reason the buildpaths check wasn't
> getting run when I was testing stuff, so what I thought was a fix,
> wasn't.
Hello Alex,
Are you working on fixing this issue?
Thanks,
Sundeep K.
Testing done with arm, arm64, x86 & x86_64 arch's.
Below combinations are tested.
- Tested the issue by reproducing and fixing it with the patch,
- with oe-selftest,
- Builds b/w different commits,
- with shared sstate b/w the builds.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent
From: Sundeep KOKKONDA
The PGO (Profile-guided Optimization) collect data about the typical execution
of a program and then use this data to inform optimizations such as inlining,
machine-code layout, register allocation, etc.
This optimization is by default disabled in rust sources
Testing is done and no regressions found.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192358):
https://lists.openembedded.org/g/openembedded-core/message/192358
Mute This Topic: https://lists.openembedded.org/mt/103167965/21656
Group Owner:
From: Sundeep KOKKONDA
Below commits on binutils-2.41 stable branch are updated.
eb49941e7e1 Gold/MIPS: Add targ_extra_size=64 for mips32 triples
c27eff41737 Gold/MIPS: Use EM_MIPS instead of EM_MIPS_RS3_LE for little endian
7fe76f02413 x86-64: fix suffix-less PUSH of symbol address
Signed-off
Testing is done and no regressions found.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192355):
https://lists.openembedded.org/g/openembedded-core/message/192355
Mute This Topic: https://lists.openembedded.org/mt/103167941/21656
Group Owner:
From: Sundeep KOKKONDA
Below commits on glibc-2.38 stable branch are updated.
44f757a636 LoongArch: Delete excessively allocated memory.
bf5aa419cb elf: Fix wrong break removal from 8ee878592c
63dbbc5c52 sysdeps: sem_open: Clear O_CREAT when semaphore file is expected to
exist [BZ #30789
From: Sundeep KOKKONDA
Below commits on glibc-2.38 stable branch are updated.
1e04dcec49 Revert "elf: Move l_init_called_next to old place of l_text_end in
link map"
719866ab2f Revert "elf: Always call destructors in reverse constructor order
(bug 30785)"
e0b6c9706c Revert
Testing is done and no regressions found.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#191247):
https://lists.openembedded.org/g/openembedded-core/message/191247
Mute This Topic: https://lists.openembedded.org/mt/102823529/21656
Group Owner:
sed l_text_end field from struct link_map"
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-core/glibc/glibc-version.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc-version.inc
b/meta/recipes-core/glibc/glibc-version.inc
index 19b98bc11a
Testing is done and no regressions found.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#191245):
https://lists.openembedded.org/g/openembedded-core/message/191245
Mute This Topic: https://lists.openembedded.org/mt/102823484/21656
Group Owner:
Below commits on binutils-2.41 stable branch are updated.
eb49941e7e1 Gold/MIPS: Add targ_extra_size=64 for mips32 triples
c27eff41737 Gold/MIPS: Use EM_MIPS instead of EM_MIPS_RS3_LE for little endian
7fe76f02413 x86-64: fix suffix-less PUSH of symbol address
Signed-off-by: Sundeep KOKKONDA
The 'rustdoc' is moved to a separate 'rust-rustdoc' package. This is a
workaround to make rust build is reproducible.
Signed-off-by: Sundeep KOKKONDA
---
meta/lib/oeqa/selftest/cases/reproducible.py | 2 +-
meta/recipes-devtools/rust/rust_1.70.0.bb| 4 +++-
2 files changed, 4 insertions
Hi Alex,
You can find the rust 1.73.0 upgrade here -
https://lists.openembedded.org/g/openembedded-core/message/189512
Thanks,
Sundeep K.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#189570):
Hi Alex,
We may look into rust oe-selftest issues during coming week.
FYI... We did rust upgrade to 1.73.0 and we could still see the "-Z nightly
build flag" failure issue (which was initially observed with rust 1.72.0
upgrade). We will send the patch by tomorrow and you can consider that for
Yocto bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=15231 raised for
failures cases analysis.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188985):
https://lists.openembedded.org/g/openembedded-core/message/188985
Mute This Topic:
I looked briefly into the issue 15090 (zvariant recipe) description and as per
me it should be tested before removing EXCLUDE_FROM_WORLD to ensure the builds
are reproducible.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188961):
in the form of compressed metadata and this makes the build
output dependent on the folder structure of the computer it's compiled on.
So, for reproducible builds, use the configuration option 'remap-debuginfo =
true' along with the '--remap-path-prefix'.
Signed-off-by: Sundeep KOKKONDA
---
meta
Hello Khem,
There are 393 New Test Cases added with this update (Refer the attachment). Out
of those,
88 Failed cases: Mostly from gcc.c-torture, gcc.dg, gcc.target, c-c++-common
modules
13 Unsupported cases: All from gcc.dg module
and other 292 Passed.
We are currently working on glibc
Regression testing is done and below are the results.
*
gcc test summary: v11.3 v11.4*
# of expected passes 126552 126842
# of unexpected failures 24295 24383
# of unexpected successes 77 77
#
error with Boost.Filesystem
105725 gcc c++ FIXE[ICE] segfault with `-Wmismatched-tags`
105920 gcc target FIXE__builtin_cpu_supports ("f16c") should
check AVX
Signed-off-by: Sundeep KOKKONDA
---
.../gcc/{gcc-11.3.inc => gcc-11.4.inc}| 6
From: Alex Kiernan
Sent: 19 July 2023 17:28
To: Richard Purdie
Cc: Alexandre Belloni ; Shinde, Yash
; openembedded-core
; MacLeod, Randy
; Kokkonda, Sundeep
; Gowda, Naveen
Subject: Re: [OE-core] Rust Oe-Selftest implementation V15 Testing
CAUTION: This
][PATCH] gcc : upgrade to v12.3
Add Khem since he may want to test meta-oe with the updated toolchain.
On 2023-06-23 12:40, Sundeep KOKKONDA wrote:
gcc stable version upgraded from v12.2 to v12.3
Below is the bug fix list for v12.3
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED
gcc stable version upgraded from v12.2 to v12.3
Below is the bug fix list for v12.3
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED=FIXED_milestone=12.3
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/gcc/{gcc-12.2.inc => gcc-12.3.inc}| 6 +++---
...cc-cr
Hello Richard,
Thank you for review, testing and confirming that oe-selftest is passed. We've
worked on the regressions caused with the patch and fixed the issue.
The rust builds (bitbake rust/nativesdk-rust) were not part of our regular
oe-selftest so we've not tested those earlier. From now
Hello Richard,
We've (re)tested and reviewed the results of this patch on our local setup and
those are "PASSED".
We will discuss further with Randy and get back to community.
Thanks,
Sundeep K.
From: Richard Purdie
Sent: 30 May 2023 19:29
To: Yash Shinde ;
I still did not get this reproduced on rust sources (Since it is occurring only
on 32-bit builds, the rust build is giving some unknown errors which are yet to
be analyzed...).
Until then, to avoid DEBUG_BUILD failures this workaround is sent.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
Cargo build is failing on 32-bit machines with a 'signal: 11, SIGSEGV: invalid
memory reference error'.
This is a workaround to disable the Debug builds for 32-bit machines.
Signed-off-by: Sundeep KOKKONDA
---
meta/classes-recipe/cargo.bbclass | 5 +
1 file changed, 5 insertions(+)
diff
Hello Richard,
On the latest rust-1.69.0 sources by adding the '--remap-path-prefix' command
(as in attached remap-path.patch file) the generated binaries from different
path are identical.
So, I've taken the same solution and applied on Yocto but it introduced many
more binary differences
Hello Steve,
When this patch is planned to take into Kirkstone?
Thanks,
Sundeep K.
From: openembedded-core@lists.openembedded.org
on behalf of Sundeep KOKKONDA via
lists.openembedded.org
Sent: 02 April 2023 20:58
To: openembedded-core@lists.openembedded.org
to this cve and so added to excluded list.
Signed-off-by: Sundeep KOKKONDA
---
meta/conf/distro/include/cve-extra-exclusions.inc | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/conf/distro/include/cve-extra-exclusions.inc
b/meta/conf/distro/include/cve-extra-exclusions.inc
index
All the 3 ' gcc g++ binutil ' are required to run rust on target.
>
> Without binutils getting error 'cannot find ld ' and
>
without g++ getting below error:
>
> root@qemux86-64:~# rustc -o hello main.rs
> error: linking with `x86_64-poky-linux-gcc` failed: exit status: 1
> |
> = note:
[YOCTO #14975]
rust files are not linking on target due to missing dependencies and observed
below error.
error: linker `x86_64-poky-linux-gcc` not found
Added the required dependencies to run rust on target machine.
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/rust/rust_1.67.1
Hello,
I tried to copy the libLTO.so to ${D}. But this shows ERROR:
rust-llvm-1.67.0-r0 do_package_qa: QA Issue: -dev package rust-llvm-dev
contains non-symlink .so '/usr/lib/llvm-rust/lib/libLTO.so' [dev-elf] and I had
a look into symlink where it points... The libLTO.so files RPATH in ${D} &
Additional object files link (if needed) -> https://we.tl/t-RvgWukdcFB
poky/build-llvm-A/tmp/work/x86_64-linux/rust-native/ -> rust-native-A-obj.tar
poky/build-llvm-B/tmp/work/x86_64-linux/rust-native/ -> rust-native-B-obj.tar
poky/build-llvm-A/tmp/work/x86_64-linux/rust-llvm-native/ ->
Hello Alex,
files are here... https://we.tl/t-ijJJZnBvKh
Thanks,
Sundeep K.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177559):
https://lists.openembedded.org/g/openembedded-core/message/177559
Mute This Topic:
Hello,
The rust builds are not reproducible when the build path is changed. The issue
details are in https://bugzilla.yoctoproject.org/show_bug.cgi?id=14875.
After debugging several ways, we tried to find at what build stage the Yocto
build artifacts are deviating with rust sources generated
Hello Richard,
As we discussed, I checked the build by removing the variables (RUST_BUILD_SYS,
RUST_HOST_SYS & RUST_TARGET_SYS) from BB_BASEHASH_IGNORE_VARS in
meta/conf/bitbake.conf file but this doesn't solve the issue, still 2 rmeta
files generated.
So, I did a re-check of my analysis
Hello Alex,
I am working on Yocto bug 14965. There is a build failure happening during
rust build because of 2 rmeta files with different hashes are generated.
I found that the changes with below commit id causing the 2nd rmeta file
(libcore-c5fc82c620226960.rmeta) generation.
e33afcd0dc
json file to the image.
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/rust/files/target.json | 39
meta/recipes-devtools/rust/rust.inc | 9 +
meta/recipes-devtools/rust/rust_1.65.0.bb| 2 +
3 files changed, 50 insertions(+)
create mode 100644 me
gcc stable version upgraded from v9.3 to v9.5
Below is the bug fix list for v9.5
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED=FIXED_milestone=9.5
Signed-off-by: Sundeep KOKKONDA
---
...-PR-tree-optimization-97236-fix-bad-.patch | 119
...ight-Line-Speculation-SLS
x86: Fix __wcsncmp_avx2 in strcmp-avx2.S [BZ# 28755]
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-core/glibc/glibc-version.inc | 2 +-
.../glibc/glibc/CVE-2021-33574_1.patch| 26 ---
2 files changed, 12 insertions(+), 16 deletions(-)
diff --git a/meta/recipes
infinite loop
0318fc4e18e Adjust PR25355 testcase
40bfb976274 Re: PR24511, nm should not mark symbols in .init_array as "t"
42b2380cdce Don't call lto-wrapper for ar and ranlib
acc4a8b8ac8 PR25585, PHDR segment not covered by LOAD segment
Signed-off-by: Sundeep KOKKONDA
---
.../binutils/bin
Regression test are performed and below is test summary.
Test summary *after* glibc updates:
204 FAIL
4341 PASS
41 UNSUPPORTED
12 XFAIL
6 XPASS
Test summary *before* glibc updates:
200 FAIL
4343 PASS
41 UNSUPPORTED
12 XFAIL
6 XPASS
There are 4 tests added newly and 2 are removed with latest
is NULL [BZ: 29265]
813a8d0171 Update syscall lists for Linux 5.19
e200127c6c riscv: Update rv64 libm test ulps
8c172a6cb0 dlfcn: Pass caller pointer to static dlopen implementation (bug
29446)
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-core/glibc/glibc-version.inc | 2 +-
1 file changed, 1
Hello,
I am planning to take the gcc, glibc & binutils updates to Kirkstone. I found
only the glibc-2.35 branch is having a few updates (given below).
f8ad66a4ca nscd: Fix netlink cache invalidation if epoll is used [BZ #29415]
9e960717e1 Apply asm redirections in wchar.h before first use
LD_LIBRARY_PATH
that way.
Signed-off-by: Sundeep KOKKONDA
---
.../rust/files/target-rust-ccld.c | 21 +++
.../rust/rust-cross-canadian.inc | 20 +++---
2 files changed, 38 insertions(+), 3 deletions(-)
create mode 100644 meta/recipes-devtools/rust/files
Hello Richard,
Using CC args causing linker error " unknown executable format " so I called
linker directly.
Also, I wrote my initial code without any hardcoded symbols and that test code
works in my local machine but when the same code executed in Yocto build
environment SIGSEGV faults are
Hello,
Since the issue " https://bugzilla.yoctoproject.org/show_bug.cgi?id=14892 " is
sporadically appearing at autobuilder, I could not completely test it on my
local machine. This patch is posted here to test it on YP AB machine.
I ensured the test is passed at my local machine.
>
> SDK
[Yocto #14892]
This is a fix for YOCTO #14878 patch. When sheband is more than 128 characters
the default shell /bin/sh is used to execute the linker instead of SDK shell,
which causes problems with LD_LIBRARY_PATH.
With this patch shell usage is avoided.
Signed-off-by: Sundeep KOKKONDA
Hello,
Since the issue " https://bugzilla.yoctoproject.org/show_bug.cgi?id=14892 " is
sporadically appearing at autobuilder, I could not completely test it on my
local machine. This patch is posted here to test it on YP AB machine.
I ensured the test is passed at my local machine.
>
> SDK
[Yocto #14892]
This is a fix for YOCTO #14878 patch. When sheband is more than 128 characters
the default shell /bin/sh is used instead of SDK shell, which causes problems
with LD_LIBRARY_PATH.
With this patch shell usage is avoided.
Signed-off-by: Sundeep KOKKONDA
---
.../rust/files/target
Is there a fix available for this issue and was it taken to glibc branches? I
checked glibc 2.35 branch now could not see any new commits available.
If there is any fix/workaround required then it should be patched in '
meta/recipes-core/glibc/ ' OR if it is a bug in glibc then it should be
Hello,
Regression tests are performed. Below is the test summary.
>
> Summary of test results *before update* of glibc:
> 146 FAIL
> 4395 PASS
> 2 UNRESOLVED
> 41 UNSUPPORTED
> 12 XFAIL
> 6 XPASS
>
> Summary of test results *after update* of glibc:
> 150 FAIL
> 4393 PASS
> 41 UNSUPPORTED
> 12
mq_timereceive check for 32 bit fallback code (BZ 29304)
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-core/glibc/glibc-version.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc-version.inc
b/meta/recipes-core/glibc/glibc-version.inc
index
Hello,
Regression testing with binutils testing is performed and no regressions found.
Thanks,
Sundeep K.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168691):
https://lists.openembedded.org/g/openembedded-core/message/168691
Mute This Topic:
: fix linking together multiple objects derived from the same
source
97dd8079feb PowerPC64: fix assertion in ppc_build_one_stub with -Os code
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/binutils/binutils-2.38.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 26-07-2022 14:30, Richard Purdie wrote:
On Tue, 2022-07-26 at 00:51 -0700, Sundeep KOKKONDA wrote:
I tried a few tests with new rust patches and found below issues.
1. I build the 'master-next' with 'bitbake core-image-minimal -cpopulate_sdk' for qemuarm64 machine. The build has
Hello Richard,
I tried a few tests with new rust patches and found below issues.
1. I build the 'master-next' with 'bitbake core-image-minimal -cpopulate_sdk'
for qemuarm64 machine. The build has no issues and sdk installed successfully
but, rustc in the installed sdk is showing below error.
Hello Otavio,
Are there any build/test issues with previous implementation? Can you let me
know what are the regression caused by below commits. I want to understand the
reason for the changes in this patch.
Fixes: ef566af964 ("rust: fix issue building cross-canadian tools for aarch64
on
Below commits on binutils-2.38 development branch are updated.
e1ea1dafff6 x86: Properly handle IFUNC function pointer reference
ffc7aa903b9 AArch64: Enable FP16 by default for Armv9-A.
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/binutils/binutils-2.38.inc | 2 +-
1 file changed
Do not use rtld_active () to determine ld.so state (bug 29078)
e5cf8ccca6 INSTALL: Rephrase -with-default-link documentation
c8ee1c85c0 misc: Fix rare fortify crash on wchar funcs. [BZ 29030]
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-core/glibc/glibc-version.inc | 2 +-
1 file changed, 1 inser
> -Original Message-
> From: Randy MacLeod
> Sent: 05 July 2022 19:23
> To: Sundeep KOKKONDA ; openembedded-
> c...@lists.openembedded.org
> Cc: rwmacl...@gmail.com; umesh.kalap...@gmail.com;
> pgowda@gmail.com; shiv...@gmail.com
> Subject: Re: [OE-core]
Hello,
Binutils regression test is performed and no regressions found. Test summary
attached.
Thanks,
Sundeep K.
TestSummary_Binutils.xlsx
Description: MS-Excel 2007 spreadsheet
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#167665):
Below commits on Binutils-2.38 development branch are updated.
binutils:
e1ea1dafff6 x86: Properly handle IFUNC function pointer reference
ffc7aa903b9 AArch64: Enable FP16 by default for Armv9-A.
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/binutils/binutils-2.38.inc | 2 +-
1
rflow case [BZ #28896]
a30807b7db string: Add a testcase for wcsncmp with SIZE_MAX [BZ #28755]
f055faf801 linux: Use socket-constants-time64.h on tst-socket-timestamp-compat
491f2ef1f0 linux: fix accuracy of get_nprocs and get_nprocs_conf [BZ #28865]
Signed-off-by: Sundeep KOKKONDA
---
meta/re
Hello Richard,
> -Original Message-
> From: Richard Purdie
> Sent: 04 July 2022 14:20
> To: Sundeep KOKKONDA ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [kirkstone] Binutils, Glibc: Updated with latest
> commits
>
> On Mon, 2022-07
rflow case [BZ #28896]
a30807b7db string: Add a testcase for wcsncmp with SIZE_MAX [BZ #28755]
f055faf801 linux: Use socket-constants-time64.h on tst-socket-timestamp-compat
491f2ef1f0 linux: fix accuracy of get_nprocs and get_nprocs_conf [BZ #28865]
Signed-off-by: Sundeep KOKKONDA
---
meta/re
update in version.in
ffc7aa903b9 AArch64: Enable FP16 by default for Armv9-A.
f20245c35f2 Automatic date update in version.in
39c6088537b Automatic date update in version.in
6a8f2255438 Automatic date update in version.in
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/binutils
The regression test for Binutils and Glibc is performed.
1) Binutils test shows no regression after update.
2) Glibc test result:
Test summary *before* glibc update on Kirkstone:
204 FAIL
4320 PASS
43 UNSUPPORTED
12 XFAIL
6 XPASS
Test summary *after* glibc update on Kirkstone:
204 FAIL
4339
can you help us out please with it? :)
Also I'm starting to wonder if we should patch rust with a workaround
from the ticket instead?
Alex
On Wed, 22 Jun 2022 at 08:24, Sundeep KOKKONDA
wrote:
Hi,
In Yocto, the Rust upgrade from 1.60.0 -> 1.61.0 enables a dependency on the
libstdc++-stati
Hi,
In Yocto, the Rust upgrade from 1.60.0 -> 1.61.0 enables a dependency on
the libstdc++-static library for rust-llvm. With this upgrade build is
aborted for 'bitbake core-image-minimal -cpopulate_sdk' with below error.
=== Error Text ===
| error: could not compile `rustc_llvm` due
Hello Randy,
On 16-06-2022 19:49, Randy MacLeod wrote:
On 2022-06-15 22:19, Sundeep KOKKONDA wrote:
Hello,
GCC regression test performed on /Kirkstone/ with gcc-11.3 &
gcc-11.2. The results are *NOT* identical. Below is test summary.
*gcc-11.3:*
/ === gcc Sum
Hello Steve,
I am planning to do a regression test on gcc-11.3 and cloned the repo from
given link ' git://git.openembedded.org/openembedded-core-contrib
stable/kirkstone-nut ' but I did not get these patches included in the cloned
repository. I could still see gcc-11.2 cloned. Also, I
On 24-05-2022 16:34, richard.pur...@linuxfoundation.org wrote:
On Tue, 2022-05-24 at 03:21 -0700, Sundeep KOKKONDA wrote:
Hello Richard,
The patch you sent in rust-common.bbclass fixing the 'oe-selftest -r
sstatetests.SStateTests.test_sstate_allarch_samesigs' test issue but
the regression test
Hello Richard,
The patch you sent in rust-common.bbclass fixing the ' oe-selftest -r
sstatetests.SStateTests.test_sstate_allarch_samesigs' test issue but the
regression test shows that the
'sstatetests.SStateTests.test_sstate_32_64_same_hash' is getting failed. So, I
think this change is not
Hello,
On 14-05-2022 12:46, richard.pur...@linuxfoundation.org wrote:
On Thu, 2022-05-12 at 22:59 -0700, Sundeep KOKKONDA wrote:
[Yocto bug #14742]
The build shows below error while building for arm machines.
Exception: TypeError: int() argument must be a string, a bytes-like object
g the change 'arm-eabi' to 'arm' fixed the issue.
The 'rust_gen_targets' Task added with its dependent variable list.
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/rust/rust-common.inc | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-devtools
Hello Richard,
On 05/05/22 19:02, Richard Purdie wrote:
On Thu, 2022-05-05 at 16:41 +0530, Sundeep KOKKONDA wrote:
Hello Richard,
On 19-04-2022 13:10, Richard Purdie wrote:
On Sun, 2022-04-10 at 23:00 -0700, Sundeep KOKKONDA wrote:
The build shows below error while building for arm
Hello Richard,
On 19-04-2022 13:10, Richard Purdie wrote:
On Sun, 2022-04-10 at 23:00 -0700, Sundeep KOKKONDA wrote:
The build shows below error while building for arm machines.
Exception: TypeError: int() argument must be a string, a bytes-like object or a
number, not 'NoneType'
Detailed
Hello,
In which release this patch will be considered?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#164614):
https://lists.openembedded.org/g/openembedded-core/message/164614
Mute This Topic: https://lists.openembedded.org/mt/90389343/21656
st_gen_target for aarch64::
tspec['data-layout'] = aarch64-unknown-linux-gnu, Type of tspec['data-layout']
=
tspec['max-atomic-width'] = 128, Type of tspec['max-atomic-width'] =
Reason for changing arm-eabi to arm: The previous change introduced this bug,
so reverting the change 'arm-eabi' to
.
=
Khem Raj
4:14am #164094 (
https://lists.openembedded.org/g/openembedded-core/message/164094 )
On Wed, Apr 6, 2022 at 11:00 AM Sundeep KOKKONDA < sundeep.kokkonda@... > wrote:
>
> The build shows below error wh
Hello,
The initial patch includes changes for armv7 also (
https://lists.openembedded.org/g/openembedded-core/message/163881 )
But, this causes build issues for target 'core-image-sato' with
'beaglebone-yocto' machine. (
https://lists.openembedded.org/g/openembedded-core/message/163954 )
So,
dictionary are generted as
NoneType. The changes will fix this issue.
Signed-off-by: Sundeep KOKKONDA
---
meta/recipes-devtools/rust/rust-common.inc | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-devtools/rust/rust-common.inc
b/meta/recipes-devtools
1 - 100 of 116 matches
Mail list logo
