from:"Sundeep KOKKONDA via lists.openembedded.org"

[OE-core] [PATCH] rust: rustdoc reproducibility issue fix

2024-07-26 Thread Sundeep KOKKONDA via lists.openembedded.org

From: Sundeep KOKKONDA 

The 'codegen-units' option split the crate into multiple compilation units for 
parallel compilation. Currently, this split is causing the rustdoc to generate 
differnt binary between the builds.
To fix this the codegen-units & the lto options are disabled.

More info about options:
https://doc.rust-lang.org/cargo/reference/profiles.html#codegen-units
https://doc.rust-lang.org/rustc/codegen-options/index.html#lto

Signed-off-by: Sundeep KOKKONDA 
---
 meta/lib/oeqa/selftest/cases/reproducible.py  |  2 --
 ...ue-fix-cargo-config-for-codegenunits.patch | 26 +++
 meta/recipes-devtools/rust/rust-source.inc|  1 +
 meta/recipes-devtools/rust/rust_1.75.0.bb |  1 +
 4 files changed, 28 insertions(+), 2 deletions(-)
 create mode 100644 
meta/recipes-devtools/rust/files/rustdoc-repro-issue-fix-cargo-config-for-codegenunits.patch

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 5460f158e5..3d3f30eebc 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -16,8 +16,6 @@ import os
 import datetime
 
 exclude_packages = [
-   'rust-rustdoc',
-   'rust-dbg'
]
 
 def is_excluded(package):
diff --git 
a/meta/recipes-devtools/rust/files/rustdoc-repro-issue-fix-cargo-config-for-codegenunits.patch
 
b/meta/recipes-devtools/rust/files/rustdoc-repro-issue-fix-cargo-config-for-codegenunits.patch
new file mode 100644
index 00..0aab8772eb
--- /dev/null
+++ 
b/meta/recipes-devtools/rust/files/rustdoc-repro-issue-fix-cargo-config-for-codegenunits.patch
@@ -0,0 +1,26 @@
+rust: rustdoc reproducibility issue fix
+
+rust: rustdoc reproducibility issue fix
+
+The 'codegen-units' option split the crate into multiple compilation units for 
parallel compilation. Currently, this split is causing the rustdoc to generate 
differnt binary between the builds.
+To fix this the codegen-units & the lto options are disabled.
+
+More info about options:
+https://doc.rust-lang.org/cargo/reference/profiles.html#codegen-units
+https://doc.rust-lang.org/rustc/codegen-options/index.html#lto
+
+Upstream-Status: Inappropriate [oe specific]
+
+Signed-off-by: Sundeep KOKKONDA 
+---
+--- a/.cargo/config.toml
 b/.cargo/config.toml
+@@ -3,3 +3,7 @@
+
+ [source.vendored-sources]
+ directory = "vendor"
++
++[profile.release]
++codegen-units = 1
++
+
diff --git a/meta/recipes-devtools/rust/rust-source.inc 
b/meta/recipes-devtools/rust/rust-source.inc
index 20ef5e82bc..facf6eb346 100644
--- a/meta/recipes-devtools/rust/rust-source.inc
+++ b/meta/recipes-devtools/rust/rust-source.inc
@@ -13,6 +13,7 @@ SRC_URI += 
"https://static.rust-lang.org/dist/rustc-${RUST_VERSION}-src.tar.xz;n
 
file://0001-Handle-vendored-sources-when-remapping-paths.patch;patchdir=${RUSTSRC}
 \
 file://repro-issue-fix-with-v175.patch;patchdir=${RUSTSRC} \
 
file://0001-cargo-do-not-write-host-information-into-compilation.patch;patchdir=${RUSTSRC}
 \
+
file://rustdoc-repro-issue-fix-cargo-config-for-codegenunits.patch;patchdir=${RUSTSRC}
 \
 "
 SRC_URI[rust.sha256sum] = 
"4526f786d673e4859ff2afa0bab2ba13c918b796519a25c1acce06dba9542340"
 
diff --git a/meta/recipes-devtools/rust/rust_1.75.0.bb 
b/meta/recipes-devtools/rust/rust_1.75.0.bb
index bb10c852b4..eae1f28bb8 100644
--- a/meta/recipes-devtools/rust/rust_1.75.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.75.0.bb
@@ -136,6 +136,7 @@ python do_configure() {
 config.add_section("rust")
 config.set("rust", "rpath", e(True))
 config.set("rust", "remap-debuginfo", e(True))
+config.set("rust", "lto", "\"off\"")
 config.set("rust", "channel", e(d.expand("${RUST_CHANNEL}")))
 
 # Whether or not to optimize the compiler and standard library
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202540): 
https://lists.openembedded.org/g/openembedded-core/message/202540
Mute This Topic: https://lists.openembedded.org/mt/107561284/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH V2] oeqa/selftest/reproducibile: rename of reproducible directories

2024-07-18 Thread Sundeep KOKKONDA via lists.openembedded.org

From: Sundeep KOKKONDA 

We do see a few reproducible issues are depending on the path length of the 
build directory.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15554

The current implementation of reproducible tests having different names for 
directories but with same length.
The build directory names are changed to have different length.

Signed-off-by: Sundeep KOKKONDA 
---
 meta/lib/oeqa/selftest/cases/reproducible.py | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 7c6cf3eb1f..5460f158e5 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -276,9 +276,13 @@ class ReproducibleTests(OESelftestTestCase):
 os.chmod(save_dir, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP | 
stat.S_IROTH | stat.S_IXOTH)
 self.logger.info('Non-reproducible packages will be copied to %s', 
save_dir)
 
+# The below bug shows that a few reproducible issues are depends on 
build dir path length.
+# https://bugzilla.yoctoproject.org/show_bug.cgi?id=15554
+# So, the reproducibleA & reproducibleB directories are changed to 
reproducibleA & reproducibleB-extended to have different size.
+
 vars_A = self.do_test_build('reproducibleA', self.build_from_sstate)
 
-vars_B = self.do_test_build('reproducibleB', False)
+vars_B = self.do_test_build('reproducibleB-extended', False)
 
 # NOTE: The temp directories from the reproducible build are purposely
 # kept after the build so it can be diffed for debugging.
@@ -333,7 +337,7 @@ class ReproducibleTests(OESelftestTestCase):
 # Copy jquery to improve the diffoscope output usability
 self.copy_file(os.path.join(jquery_sysroot, 
'usr/share/javascript/jquery/jquery.min.js'), os.path.join(package_html_dir, 
'jquery.js'))
 
-run_diffoscope('reproducibleA', 'reproducibleB', 
package_html_dir, max_report_size=self.max_report_size,
+run_diffoscope('reproducibleA', 'reproducibleB-extended', 
package_html_dir, max_report_size=self.max_report_size,
 native_sysroot=diffoscope_sysroot, ignore_status=True, 
cwd=package_dir)
 
 if fails:
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202234): 
https://lists.openembedded.org/g/openembedded-core/message/202234
Mute This Topic: https://lists.openembedded.org/mt/107421488/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] oeqa/selftest/reproducibile: rename of reproducible directories

2024-07-18 Thread Sundeep KOKKONDA via lists.openembedded.org



On 18-Jul-24 16:44, Richard Purdie 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 Thu, 2024-07-18 at 03:04 -0700, Sundeep KOKKONDA via lists.openembedded.org 
wrote:

From: Sundeep KOKKONDA 

We do see a few reproducible issues are depending on the path length of the 
build directory.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15554

The current implementation of reproducible tests having different names for 
directories but with same length.
The build directory names are changed to have difefrent lenth.

Signed-off-by: Sundeep KOKKONDA 
---
  meta/lib/oeqa/selftest/cases/reproducible.py | 10 +++---
  1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 7c6cf3eb1f..6932b0c2a5 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -276,9 +276,13 @@ class ReproducibleTests(OESelftestTestCase):
  os.chmod(save_dir, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP | 
stat.S_IROTH | stat.S_IXOTH)
  self.logger.info('Non-reproducible packages will be copied to 
%s', save_dir)

-vars_A = self.do_test_build('reproducibleA', self.build_from_sstate)
+# The below bug shows that a few reproducible issues are depends on 
build dir path length.
+# https://bugzilla.yoctoproject.org/show_bug.cgi?id=15554
+# So, the reproducibleA & reproducibleB directories are changed to 
reproducible & reproducible-extended to have different size.

-vars_B = self.do_test_build('reproducibleB', False)
+vars_A = self.do_test_build('reproducible', self.build_from_sstate)
+
+vars_B = self.do_test_build('reproducible-extended', False)

  # NOTE: The temp directories from the reproducible build are purposely
  # kept after the build so it can be diffed for debugging.
@@ -333,7 +337,7 @@ class ReproducibleTests(OESelftestTestCase):
  # Copy jquery to improve the diffoscope output usability
  self.copy_file(os.path.join(jquery_sysroot, 
'usr/share/javascript/jquery/jquery.min.js'), os.path.join(package_html_dir, 
'jquery.js'))

-run_diffoscope('reproducibleA', 'reproducibleB', 
package_html_dir, max_report_size=self.max_report_size,
+run_diffoscope('reproducible', 'reproducible-extended', 
package_html_dir, max_report_size=self.max_report_size,
  native_sysroot=diffoscope_sysroot, 
ignore_status=True, cwd=package_dir)

  if fails:

Thanks Sundeep. Lets keep the A/B in there since people are familiar
with it as Yoann mentions but thanks for sending, otherwise looks good.
Can you quickly send a v2 please?


Sure, I'll use "reproducibleA" & "reproducibleB-extended" names.


Thanks,

Sundeep K.



Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202206): 
https://lists.openembedded.org/g/openembedded-core/message/202206
Mute This Topic: https://lists.openembedded.org/mt/107414164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] oeqa/selftest/reproducibile: rename of reproducible directories

2024-07-18 Thread Sundeep KOKKONDA via lists.openembedded.org

From: Sundeep KOKKONDA 

We do see a few reproducible issues are depending on the path length of the 
build directory.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15554

The current implementation of reproducible tests having different names for 
directories but with same length.
The build directory names are changed to have difefrent lenth.

Signed-off-by: Sundeep KOKKONDA 
---
 meta/lib/oeqa/selftest/cases/reproducible.py | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 7c6cf3eb1f..6932b0c2a5 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -276,9 +276,13 @@ class ReproducibleTests(OESelftestTestCase):
 os.chmod(save_dir, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP | 
stat.S_IROTH | stat.S_IXOTH)
 self.logger.info('Non-reproducible packages will be copied to %s', 
save_dir)
 
-vars_A = self.do_test_build('reproducibleA', self.build_from_sstate)
+# The below bug shows that a few reproducible issues are depends on 
build dir path length.
+# https://bugzilla.yoctoproject.org/show_bug.cgi?id=15554
+# So, the reproducibleA & reproducibleB directories are changed to 
reproducible & reproducible-extended to have different size.
 
-vars_B = self.do_test_build('reproducibleB', False)
+vars_A = self.do_test_build('reproducible', self.build_from_sstate)
+
+vars_B = self.do_test_build('reproducible-extended', False)
 
 # NOTE: The temp directories from the reproducible build are purposely
 # kept after the build so it can be diffed for debugging.
@@ -333,7 +337,7 @@ class ReproducibleTests(OESelftestTestCase):
 # Copy jquery to improve the diffoscope output usability
 self.copy_file(os.path.join(jquery_sysroot, 
'usr/share/javascript/jquery/jquery.min.js'), os.path.join(package_html_dir, 
'jquery.js'))
 
-run_diffoscope('reproducibleA', 'reproducibleB', 
package_html_dir, max_report_size=self.max_report_size,
+run_diffoscope('reproducible', 'reproducible-extended', 
package_html_dir, max_report_size=self.max_report_size,
 native_sysroot=diffoscope_sysroot, ignore_status=True, 
cwd=package_dir)
 
 if fails:
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202196): 
https://lists.openembedded.org/g/openembedded-core/message/202196
Mute This Topic: https://lists.openembedded.org/mt/107414164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Rust reproducibility issue summary

2024-07-07 Thread Sundeep KOKKONDA via lists.openembedded.org

On Fri, Jul 5, 2024 at 08:55 PM, Alexander Kanavin wrote:

> 
> After reading the issue and poking at the rustdoc binaries on my local
> disk, I think the key is in finding where those llvm. suffixes are
> generated and *how*. Something (presumably rust-llvm) puts them there, so
> narrowing down to the point where that non-reproducible value is decided
> would help a lot in finding out why it sometimes changes. It does require
> navigating and reading a mountain of unfamiliar llvm code, this is what
> makes the issue difficult.

The.llvm. are generated by ThinLTO optimizations, and this is enabled by 
default. I tried a build by disabling this optimization but that doesn't solved 
the problem. By disabling lto, the.llvm. are not seen in rustdoc binary 
but still the binaries are differed. I'll have to check with llvm community 
that how this hash depends/affects based on build-dir name/length.

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201617): 
https://lists.openembedded.org/g/openembedded-core/message/201617
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Rust reproducibility issue summary

2024-07-07 Thread Sundeep KOKKONDA via lists.openembedded.org

On Fri, Jul 5, 2024 at 05:06 PM, Alexander Kanavin wrote:

> 
> - what seems to be *not* reproducible is having two different build
> directories with significantly different names (e.g. build/ and
> build-rustreprolongdir/). I've seen this in build/ vs build-2/ as
> well, but e.g. build-2/ and build-3/ are reproducible.

Hello Alex,

This case reproduces the issue for me and I haven't checked such case 
earlier... I am able to reproduce the issue when the build directory names are 
different in size ( build & build-somelongpath-rustdoc-repro ).

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201616): 
https://lists.openembedded.org/g/openembedded-core/message/201616
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Rust reproducibility issue summary

2024-07-04 Thread Sundeep KOKKONDA via lists.openembedded.org

Hi Alex,

What distro you used to reproduce the issue & what pkgs were installed. You 
used any shared sstate of Yocto?
With this info I will retry to reproduce the issue on my local machine.

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201578): 
https://lists.openembedded.org/g/openembedded-core/message/201578
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0

2024-07-03 Thread Sundeep KOKKONDA via lists.openembedded.org

On Wed, Jul 3, 2024 at 01:44 PM, Richard Purdie wrote:

> 
> it looks like most of the issues are 1.78 related apart from the one
> above.

That's very useful info, thank you.
We will investigate the issues w/ 1.78 and the above one failure with 1.77.

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201460): 
https://lists.openembedded.org/g/openembedded-core/message/201460
Mute This Topic: https://lists.openembedded.org/mt/106974835/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0

2024-07-02 Thread Sundeep KOKKONDA via lists.openembedded.org

On Tue, Jul 2, 2024 at 08:38 PM, Ross Burton wrote:

> 
> My builder is running oe-selftest -r rust on the incremental upgrades to
> see what of those fail, but I’m not running reproducible builds yet.
> 
> 1.76 was successful, 1.77 is building.

Can you check for reproducible tests also? That helps to see where the issue is 
triggered.

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201442): 
https://lists.openembedded.org/g/openembedded-core/message/201442
Mute This Topic: https://lists.openembedded.org/mt/106974835/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0

2024-07-02 Thread Sundeep KOKKONDA via lists.openembedded.org

Hello Richard,

Thanks for test results. We will look into the failures reported.
These failures are only in 1.78 (Is the testing done on 1.76 & 1.77)?

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201421): 
https://lists.openembedded.org/g/openembedded-core/message/201421
Mute This Topic: https://lists.openembedded.org/mt/106974835/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 9/9] rust: Upgrade 1.77.2->1.78.0

2024-07-02 Thread Sundeep KOKKONDA via lists.openembedded.org

Hello Richard,

Thanks for test results. We will look into the failures reported.
These failures are only in 1.78 (Is the testing done on 1.76 & 1.77)?

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201420): 
https://lists.openembedded.org/g/openembedded-core/message/201420
Mute This Topic: https://lists.openembedded.org/mt/106974835/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/9] rust: Upgrade 1.75.0->1.76.0

2024-07-01 Thread Sundeep KOKKONDA via lists.openembedded.org

Hi Alex,

We intentionally dropped these packages from exclude list (informed to Richard 
earlier) to see the issue fixes with latest releases.

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201298): 
https://lists.openembedded.org/g/openembedded-core/message/201298
Mute This Topic: https://lists.openembedded.org/mt/106974834/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Rust reproducibility issue summary

2024-06-24 Thread Sundeep KOKKONDA via lists.openembedded.org



On 24-Jun-24 17:52, 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 Mon, 24 Jun 2024 at 11:11, Alexander Kanavin via
lists.openembedded.org
wrote:

I can share the two different build directories for your further
inspection perhaps? Let me upload the tarballs somewhere public.

They're here:
https://drive.google.com/file/d/1kKhHoC3oMFPFjvuLvM4glQzKX8JeXNue/view?usp=drive_link
https://drive.google.com/file/d/1RCoZipt6i9wWG3j-j2rilWCNW_NMNCk9/view?usp=drive_link

Please let me know when you have downloaded them because I'm nearly
out of space there, and need to delete them ASAP.


Hi Alex,

Copied. Thnx.

I tried again with latest poky, still the /rustdoc /generated identical :(



Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201119): 
https://lists.openembedded.org/g/openembedded-core/message/201119
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Rust reproducibility issue summary

2024-06-24 Thread Sundeep KOKKONDA via lists.openembedded.org

On Mon, Jun 24, 2024 at 01:50 PM, Alexander Kanavin wrote:

> 
> This is not the case. I just built rust (without sstate, from sources)
> in two different build directories on the same machine, and indeed

Thanks for sharing this... Unfortunately I couldn't see this happening during 
my testing. If this is the case, the issue might be there in rust.

for me diff is not there...
> diff -uNr build-b/tmp/work/core2-64-poky-linux/rust/1.75.0/image/ 
> build-c/tmp/work/core2-64-poky-linux/rust/1.75.0/image/
> diff build-b/tmp/work/core2-64-poky-linux/rust/1.75.0/image/usr/bin/rustdoc 
> build-c/tmp/work/core2-64-poky-linux/rust/1.75.0/image/usr/bin/rustdoc
> diff -uNr build-b/tmp/deploy/deb/core2-64/ build-c/tmp/deploy/deb/core2-64/

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201070): 
https://lists.openembedded.org/g/openembedded-core/message/201070
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Rust reproducibility issue summary

2024-06-23 Thread Sundeep KOKKONDA via lists.openembedded.org

Hello,

I've a local reproducer for this issue. Below are a few observations with my
analysis.
- The deviation in rustdoc binary are because of the different hash-id
generated between the build (as explained above -
https://lists.openembedded.org/g/openembedded-core/message/200238)
- The hash-id generates identically when the rust built from it's sources every
time.
- During the oe-selftest triggered, when the issue reproduced I can see there
are reproducibleA & reproducibleB directories are generated.
But, the rust is not built from sources on both directories beacuse of Setscene
Tasks and Shared State. (reproducibleB directory has rust sources built and
reproducibleA has setscene realted data copied the files into it from sstate
and so, no rust sources are cloned & build into it)
- The above case not always happening with oe-selftest, when the test passed I
can see the reproducibleA also has rust sources pulled and built, in this case
rustdoc generates identically.
- When the issue reproduced, I did a check on the sstate sigdata to find any
deviations but those sig's are identical.
- Also, when the test failed, I tried to find the unique hash-id's generated in
rustdoc in the generated rlibs of rust. I could only find one hash-id in rlibs
where the rust sources are actually built. The other hash-id not found in rlibs
of reproducibleA/B.
- The ' diff
.../reproducibleA/tmp/work/core2-64-poky-linux/rust/1.75.0/temp/depsig.do_package_write_deb

.../reproducibleB/tmp/work/core2-64-poky-linux/rust/1.75.0/temp/depsig.do_package_write_deb
' shows -
8c8
< -rw- 15932884
6a6618ccfc171ea507ad39eb95bc239116b5f5c9e85a50ce9de3b43c73ff17d7./deploy-debs/core2-64/rust-dbg_1.75.0-r0_amd64.deb
---
> -rw- 15932940
> 4dcbe007aa8d46e658f95a3651938d67ca5cd55409c503861f365cb9c38f14e7./deploy-debs/core2-64/rust-dbg_1.75.0-r0_amd64.deb
11c11
< -rw- 2902068
564925753476842ea9052311afa27cbc099136113ea9f5394b5554eccb09e8f3./deploy-debs/core2-64/rust-rustdoc_1.75.0-r0_amd64.deb
---
> -rw- 2901612
> c0cd05fe344400c0a9d31fecd808c3152481f35dacc0556c006b88a239209358./deploy-debs/core2-64/rust-rustdoc_1.75.0-r0_amd64.deb

I am not sure of what that diff indicates.

Can I get some pointers on -
1. Why only sometimes the setscene setting on reproducibleA (which causes rust
sources not to rebuilt)
2. Is there any way/tool to analyze the above depsig data or what is going-on
with setscene.

This helps to identify the issue is happening due to sstate? if not I can look
into rust.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201063):
https://lists.openembedded.org/g/openembedded-core/message/201063
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [scarthgap][PATCH] binutils: stable 2.42 branch updates

2024-06-20 Thread Sundeep KOKKONDA via lists.openembedded.org

Testing done and no regression found.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200942): 
https://lists.openembedded.org/g/openembedded-core/message/200942
Mute This Topic: https://lists.openembedded.org/mt/106775746/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] binutils: stable 2.42 branch updates

2024-06-20 Thread Sundeep KOKKONDA via lists.openembedded.org

Testing done and no regression found.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200941): 
https://lists.openembedded.org/g/openembedded-core/message/200941
Mute This Topic: https://lists.openembedded.org/mt/106775740/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [scarthgap][PATCH] binutils: stable 2.42 branch updates

2024-06-20 Thread Sundeep KOKKONDA via lists.openembedded.org

From: Sundeep KOKKONDA 

Below commits on binutils-2.42 stable branch are updated.

6c360d37662 PR31898 bug in processing DW_RLE_startx_endx
bfda03eed33 aarch64: Remove asserts from operand qualifier decoders
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 EVEX MAP4
d816fda3cbd aarch64: Remove B16B16, SVE2p1 and SME2p1
cb11047e34a Re: Move bfd_init to bfd.c
818bcf40efb print cached error messages using _bfd_error_handler
831be495ef1 aarch64: Fix the 2nd operand in gcsstr and gcssttr instructions.

Dropped: 0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch

Signed-off-by: Sundeep KOKKONDA 
---
 .../binutils/binutils-2.42.inc|   3 +-
 ...sserts-from-operand-qualifier-decode.patch | 382 --
 2 files changed, 1 insertion(+), 384 deletions(-)
 delete mode 100644 
meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch

diff --git a/meta/recipes-devtools/binutils/binutils-2.42.inc 
b/meta/recipes-devtools/binutils/binutils-2.42.inc
index d2f49560f3..c8f526b5c7 100644
--- a/meta/recipes-devtools/binutils/binutils-2.42.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.42.inc
@@ -20,7 +20,7 @@ UPSTREAM_CHECK_GITTAGREGEX = "binutils-(?P\d+_(\d_?)*)"
 
 CVE_STATUS[CVE-2023-25584] = "cpe-incorrect: Applies only for version 2.40 and 
earlier"
 
-SRCREV ?= "553c7f61b74badf91df484450944675efd9cd485"
+SRCREV ?= "cbec9028dd3fa9b49e0204f1a989cea67cae32c6"
 BINUTILS_GIT_URI ?= 
"git://sourceware.org/git/binutils-gdb.git;branch=${SRCBRANCH};protocol=https"
 SRC_URI = "\
  ${BINUTILS_GIT_URI} \
@@ -36,6 +36,5 @@ SRC_URI = "\
  file://0013-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch \
  file://0014-Remove-duplicate-pe-dll.o-entry-deom-targ_extra_ofil.patch \
  file://0015-gprofng-change-use-of-bignum-to-bigint.patch \
- file://0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch \
 "
 S  = "${WORKDIR}/git"
diff --git 
a/meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch
 
b/meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch
deleted file mode 100644
index 7b52425a38..00
--- 
a/meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch
+++ /dev/null
@@ -1,382 +0,0 @@
-From 5b1c70bfe0d8f84dc28237d6150b7b9d57c791a8 Mon Sep 17 00:00:00 2001
-From: Victor Do Nascimento 
-Date: Tue, 16 Apr 2024 11:49:15 +0100
-Subject: [PATCH] aarch64: Remove asserts from operand qualifier decoders
- [PR31595]
-
-Given that the disassembler should never abort when decoding
-(potentially random) data, assertion statements in the
-`get_*reg_qualifier_from_value' function family prove problematic.
-
-Consider the random 32-bit word W, encoded in a data segment and
-encountered on execution of `objdump -D '.
-
-If:
-
-  (W & ~opcode_mask) == valid instruction
-
-Then before `print_insn_aarch64_word' has a chance to report the
-instruction as potentially undefined, an attempt will be made to have
-the qualifiers for the instruction's register operands (if any)
-decoded.  If the relevant bits do not map onto a valid qualifier for
-the matched instruction-like word, an abort will be triggered and the
-execution of objdump aborted.
-
-As this scenario is perfectly feasible and, in light of the fact that
-objdump must successfully decode all sections of a given object file,
-it is not appropriate to assert in this family of functions.
-
-Therefore, we add a new pseudo-qualifier `AARCH64_OPND_QLF_ERR' for
-handling invalid qualifier-associated values and re-purpose the
-assertion conditions in qualifier-retrieving functions to be the
-predicate guarding the returning of the calculated qualifier type.
-If the predicate fails, we return this new qualifier and allow the
-caller to handle the error as appropriate.
-
-As these functions are called either from within
-`aarch64_extract_operand' or `do_special_decoding', both of which are
-expected to return non-zero values, it suffices that callers return
-zero upon encountering `AARCH64_OPND_QLF_ERR'.
-
-Ar present the error presented in the hypothetical scenario has been
-encountered in `get_sreg_qualifier_from_value', but the change is made
-to the whole family to keep the interface consistent.
-
-Bug: https://sourceware.org/PR31595
-
-Upstream-Status: Backport [commit 2601b201e95ea0edab89342ee7137c74e88a8a79]
-
-Signed-off-by: Mark Hatle 

- .../testsuite/binutils-all/aarch64/illegal.d  |  1 +
- .../testsuite/binutils-all/aarch64/illegal.s  |  3 +
- include/opcode/aarch64.h  |  3 +
- opcodes/aarch64-dis.c | 98 +++
- 4 files changed, 87 insertions(+), 18 deletions(-)
-
-diff --git

[OE-core] [PATCH] binutils: stable 2.42 branch updates

2024-06-20 Thread Sundeep KOKKONDA via lists.openembedded.org

From: Sundeep KOKKONDA 

Below commits on binutils-2.42 stable branch are updated.

6c360d37662 PR31898 bug in processing DW_RLE_startx_endx
bfda03eed33 aarch64: Remove asserts from operand qualifier decoders

Dropped: 0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch

Signed-off-by: Sundeep KOKKONDA 
---
 .../binutils/binutils-2.42.inc|   3 +-
 ...sserts-from-operand-qualifier-decode.patch | 382 --
 2 files changed, 1 insertion(+), 384 deletions(-)
 delete mode 100644 
meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch

diff --git a/meta/recipes-devtools/binutils/binutils-2.42.inc 
b/meta/recipes-devtools/binutils/binutils-2.42.inc
index d4e94d0162..c8f526b5c7 100644
--- a/meta/recipes-devtools/binutils/binutils-2.42.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.42.inc
@@ -20,7 +20,7 @@ UPSTREAM_CHECK_GITTAGREGEX = "binutils-(?P\d+_(\d_?)*)"
 
 CVE_STATUS[CVE-2023-25584] = "cpe-incorrect: Applies only for version 2.40 and 
earlier"
 
-SRCREV ?= "73b22b4481e85635eb978585f405c4433bcc0174"
+SRCREV ?= "cbec9028dd3fa9b49e0204f1a989cea67cae32c6"
 BINUTILS_GIT_URI ?= 
"git://sourceware.org/git/binutils-gdb.git;branch=${SRCBRANCH};protocol=https"
 SRC_URI = "\
  ${BINUTILS_GIT_URI} \
@@ -36,6 +36,5 @@ SRC_URI = "\
  file://0013-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch \
  file://0014-Remove-duplicate-pe-dll.o-entry-deom-targ_extra_ofil.patch \
  file://0015-gprofng-change-use-of-bignum-to-bigint.patch \
- file://0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch \
 "
 S  = "${WORKDIR}/git"
diff --git 
a/meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch
 
b/meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch
deleted file mode 100644
index 7b52425a38..00
--- 
a/meta/recipes-devtools/binutils/binutils/0016-aarch64-Remove-asserts-from-operand-qualifier-decode.patch
+++ /dev/null
@@ -1,382 +0,0 @@
-From 5b1c70bfe0d8f84dc28237d6150b7b9d57c791a8 Mon Sep 17 00:00:00 2001
-From: Victor Do Nascimento 
-Date: Tue, 16 Apr 2024 11:49:15 +0100
-Subject: [PATCH] aarch64: Remove asserts from operand qualifier decoders
- [PR31595]
-
-Given that the disassembler should never abort when decoding
-(potentially random) data, assertion statements in the
-`get_*reg_qualifier_from_value' function family prove problematic.
-
-Consider the random 32-bit word W, encoded in a data segment and
-encountered on execution of `objdump -D '.
-
-If:
-
-  (W & ~opcode_mask) == valid instruction
-
-Then before `print_insn_aarch64_word' has a chance to report the
-instruction as potentially undefined, an attempt will be made to have
-the qualifiers for the instruction's register operands (if any)
-decoded.  If the relevant bits do not map onto a valid qualifier for
-the matched instruction-like word, an abort will be triggered and the
-execution of objdump aborted.
-
-As this scenario is perfectly feasible and, in light of the fact that
-objdump must successfully decode all sections of a given object file,
-it is not appropriate to assert in this family of functions.
-
-Therefore, we add a new pseudo-qualifier `AARCH64_OPND_QLF_ERR' for
-handling invalid qualifier-associated values and re-purpose the
-assertion conditions in qualifier-retrieving functions to be the
-predicate guarding the returning of the calculated qualifier type.
-If the predicate fails, we return this new qualifier and allow the
-caller to handle the error as appropriate.
-
-As these functions are called either from within
-`aarch64_extract_operand' or `do_special_decoding', both of which are
-expected to return non-zero values, it suffices that callers return
-zero upon encountering `AARCH64_OPND_QLF_ERR'.
-
-Ar present the error presented in the hypothetical scenario has been
-encountered in `get_sreg_qualifier_from_value', but the change is made
-to the whole family to keep the interface consistent.
-
-Bug: https://sourceware.org/PR31595
-
-Upstream-Status: Backport [commit 2601b201e95ea0edab89342ee7137c74e88a8a79]
-
-Signed-off-by: Mark Hatle 

- .../testsuite/binutils-all/aarch64/illegal.d  |  1 +
- .../testsuite/binutils-all/aarch64/illegal.s  |  3 +
- include/opcode/aarch64.h  |  3 +
- opcodes/aarch64-dis.c | 98 +++
- 4 files changed, 87 insertions(+), 18 deletions(-)
-
-diff --git a/binutils/testsuite/binutils-all/aarch64/illegal.d 
b/binutils/testsuite/binutils-all/aarch64/illegal.d
-index 4b90a1d9f39..b69318aec85 100644
 a/binutils/testsuite/binutils-all/aarch64/illegal.d
-+++ b/binutils/testsuite/binutils-all/aarch64/illegal.d
-@@ -8,5 +8,6 @@ Disassembly of section \.text:
- 
- 0+000 <.*>:
- [ ]+0:[   ]+68ea18cc[ ]+.inst[]+0x68ea18cc ; undefined
-+[ ]+4:[   ]+9dc39839[ ]+.inst[]+0x9dc39839 ; undefined
-

Re: [OE-core] [PATCH v2 2/3] rust: Upgrade 1.75.0->1.76.0

2024-06-17 Thread Sundeep KOKKONDA via lists.openembedded.org

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 will start with 1.79 update soon.

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200843): 
https://lists.openembedded.org/g/openembedded-core/message/200843
Mute This Topic: https://lists.openembedded.org/mt/106689695/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 3/3] rust: reproducibility issue fix with v1.76

2024-06-14 Thread Sundeep KOKKONDA via lists.openembedded.org



On 14-Jun-24 14:41, 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.

Is the issue reported upstream? This should be done, and the link
included into the inappropriate patch.


I guess no, initial patch was made with 
"/0001-Revert-Map-source-absolute-paths-to-OUT_DIR-as-relat.patch/" 
(that is also /Inappropriate/) and based on the changes in crate 'cc' I 
updated the patch to fix the repro issue.


I will check and report the issue to 'cc' crate about buggy 
commit#c4f414f449bb7cffba3bc923f277704d1d08a8ec.



Thanks,

Sundeep K.



Alex

On Fri, 14 Jun 2024 at 07:51, Yash Shinde via lists.openembedded.org
  wrote:

From: Yash Shinde

A few crates are using the updated version of the 'cc' crate and
this is causing the generated object 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 +
  2 files changed, 60 insertions(+)
  create mode 100644 
meta/recipes-devtools/rust/files/repro-issue-fix-with-cc-crate-hashmap.patch

diff --git 
a/meta/recipes-devtools/rust/files/repro-issue-fix-with-cc-crate-hashmap.patch 
b/meta/recipes-devtools/rust/files/repro-issue-fix-with-cc-crate-hashmap.patch
new file mode 100644
index 00..20d7e3fc15
--- /dev/null
+++ 
b/meta/recipes-devtools/rust/files/repro-issue-fix-with-cc-crate-hashmap.patch
@@ -0,0 +1,59 @@
+rust: reproducibility issue fix with v1.76
+
+A few crates are using the updated version of the 'cc' crate and this is 
causing the generated object file names containing a unique hashmap id.
+The hashmap addition to generated files is reverted here.
+
+
+Upstream-Status: Inappropriate [patches need rework]
+Signed-off-by: Sundeep KOKKONDA
+---
+--- a/vendor/cc-1.0.79/src/lib.rs
 b/vendor/cc-1.0.79/src/lib.rs
+@@ -56,12 +56,11 @@
+ #![allow(deprecated)]
+ #![deny(missing_docs)]
+
+-use std::collections::{hash_map, HashMap};
++use std::collections::HashMap;
+ use std::env;
+ use std::ffi::{OsStr, OsString};
+ use std::fmt::{self, Display, Formatter};
+ use std::fs;
+-use std::hash::Hasher;
+ use std::io::{self, BufRead, BufReader, Read, Write};
+ use std::path::{Component, Path, PathBuf};
+ use std::process::{Child, Command, Stdio};
+@@ -1037,24 +1036,7 @@
+
+ let mut objects = Vec::new();
+ for file in self.files.iter() {
+-let obj = if file.has_root() {
+-// If `file` is an absolute path, prefix the `basename`
+-// with the `dirname`'s hash to ensure name uniqueness.
+-let basename = file
+-.file_name()
+-.ok_or_else(|| Error::new(ErrorKind::InvalidArgument, 
"file_name() failure"))?
+-.to_string_lossy();
+-let dirname = file
+-.parent()
+-.ok_or_else(|| Error::new(ErrorKind::InvalidArgument, 
"parent() failure"))?
+-.to_string_lossy();
+-let mut hasher = hash_map::DefaultHasher::new();
+-hasher.write(dirname.to_string().as_bytes());
+-dst.join(format!("{:016x}-{}", hasher.finish(), basename))
+-.with_extension("o")
+-} else {
+-dst.join(file).with_extension("o")
+-};
++let obj = dst.join(file).with_extension("o");
+ let obj = if !obj.starts_with() {
+ dst.join(obj.file_name().ok_or_else(|| {
+ Error::new(ErrorKind::IOError, "Getting object file details 
failed.")
+Index: rustc-1.77.0-src/vendor/cc-1.0.79/.cargo-checksum.json
+===
+--- a/vendor/cc-1.0.79/.cargo-checksum.json
 b/vendor/cc-1.0.79/.cargo-checksum.json
+@@ -1 +1 @@

Re: [OE-core] [PATCH] rust: rustdoc reproducibility - disable PGO

2024-06-03 Thread Sundeep KOKKONDA via lists.openembedded.org



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 you test this patch locally? What was the outcome?
rust-rustdoc_1.75.0-r0_amd64.deb is generated and the binaries are 
identical.
Also, as I mentioned in commit message it is a test patch to see the 
issue is fixed or not on autobuilder.


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 on rustdoc binaries. 
The issue discussion is here:
https://internals.rust-lang.org/t/rustdoc-binary-is-not-reproducible/20027 



Signed-off-by: Sundeep KOKKONDA 
---
  meta/lib/oeqa/selftest/cases/reproducible.py | 2 --
  meta/recipes-devtools/rust/rust_1.75.0.bb    | 4 
  2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py

index 97a9c3da90..80e830136f 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -16,8 +16,6 @@ import os
  import datetime

  exclude_packages = [
-   'rust-rustdoc',
-   'rust-dbg'
 ]

  def is_excluded(package):
diff --git a/meta/recipes-devtools/rust/rust_1.75.0.bb 
b/meta/recipes-devtools/rust/rust_1.75.0.bb

index c66c14cc5a..4caa5892e6 100644
--- a/meta/recipes-devtools/rust/rust_1.75.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.75.0.bb
@@ -153,6 +153,10 @@ python do_configure() {
  rustc = d.getVar('RUSTC_BOOTSTRAP')
  config.set("build", "rustc", e(rustc))

+    # Support for the profiler runtime to generate e.g. coverage 
report,

+    # PGO etc.
+    config.set("build", "profiler", e(False))
+
  cargo = d.getVar('CARGO_BOOTSTRAP')
  config.set("build", "cargo", e(cargo))

--
2.43.0









-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200265): 
https://lists.openembedded.org/g/openembedded-core/message/200265
Mute This Topic: https://lists.openembedded.org/mt/106463035/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] rust: rustdoc reproducibility - disable PGO

2024-06-03 Thread Sundeep KOKKONDA via lists.openembedded.org



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 you test this patch locally? What was the outcome?
rust-rustdoc_1.75.0-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 on rustdoc binaries. The issue 
discussion is here:
https://internals.rust-lang.org/t/rustdoc-binary-is-not-reproducible/20027

Signed-off-by: Sundeep KOKKONDA 
---
  meta/lib/oeqa/selftest/cases/reproducible.py | 2 --
  meta/recipes-devtools/rust/rust_1.75.0.bb| 4 
  2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 97a9c3da90..80e830136f 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -16,8 +16,6 @@ import os
  import datetime

  exclude_packages = [
-   'rust-rustdoc',
-   'rust-dbg'
 ]

  def is_excluded(package):
diff --git a/meta/recipes-devtools/rust/rust_1.75.0.bb 
b/meta/recipes-devtools/rust/rust_1.75.0.bb
index c66c14cc5a..4caa5892e6 100644
--- a/meta/recipes-devtools/rust/rust_1.75.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.75.0.bb
@@ -153,6 +153,10 @@ python do_configure() {
  rustc = d.getVar('RUSTC_BOOTSTRAP')
  config.set("build", "rustc", e(rustc))

+# Support for the profiler runtime to generate e.g. coverage report,
+# PGO etc.
+config.set("build", "profiler", e(False))
+
  cargo = d.getVar('CARGO_BOOTSTRAP')
  config.set("build", "cargo", e(cargo))

--
2.43.0





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200262): 
https://lists.openembedded.org/g/openembedded-core/message/200262
Mute This Topic: https://lists.openembedded.org/mt/106463035/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] rust: rustdoc reproducibility - disable PGO

2024-06-03 Thread Sundeep KOKKONDA via lists.openembedded.org

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-by: Sundeep KOKKONDA 
---
 meta/lib/oeqa/selftest/cases/reproducible.py | 2 --
 meta/recipes-devtools/rust/rust_1.75.0.bb| 4 
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 97a9c3da90..80e830136f 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -16,8 +16,6 @@ import os
 import datetime
 
 exclude_packages = [
-   'rust-rustdoc',
-   'rust-dbg'
]
 
 def is_excluded(package):
diff --git a/meta/recipes-devtools/rust/rust_1.75.0.bb 
b/meta/recipes-devtools/rust/rust_1.75.0.bb
index c66c14cc5a..4caa5892e6 100644
--- a/meta/recipes-devtools/rust/rust_1.75.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.75.0.bb
@@ -153,6 +153,10 @@ python do_configure() {
 rustc = d.getVar('RUSTC_BOOTSTRAP')
 config.set("build", "rustc", e(rustc))
 
+# Support for the profiler runtime to generate e.g. coverage report,
+# PGO etc.
+config.set("build", "profiler", e(False))
+
 cargo = d.getVar('CARGO_BOOTSTRAP')
 config.set("build", "cargo", e(cargo))
 
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200260): 
https://lists.openembedded.org/g/openembedded-core/message/200260
Mute This Topic: https://lists.openembedded.org/mt/106463035/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Rust reproducibility issue summary

2024-06-02 Thread Sundeep KOKKONDA via lists.openembedded.org



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:

I've been asked what the reproducibility issue is and what data we
have. I ran a couple of test builds on the current autobuilder and the
test cluster. I added in the diff at the end of this email, just to
limit the test to what we're interested in.

The test on the new test cluster passed:

https://valkyrie.yoctoproject.org/#/builders/37/builds/36

However the build on the current autobuilder did not:

https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4876

and the different binaries generated are here:

http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20240531-l872m0ip/packages/

We need to get to the bottom of why these are different and the test is
sometimes failing. Any help appreciated!

It is unclear what we need to do to reproduce the issue on demand.

One possible lead is in the original attempt to fix this;
https://git.yoctoproject.org/poky/commit/?id=321aebfa281bd28e368c684ece57867f6bd0cbe7

It is not yet clear if disabling PGO makes things reproducible, as the
same commit also prevented the non reproducible binary (rustdoc) from
being installed (with the demangler line).

PGO as the culprit should be either confirmed, or ruled out first.

If PGO indeed helps then the next step is figure out how to disable
(or tweak) it in a way that doesn't cause issues with chromium:

https://git.yoctoproject.org/poky/commit/?id=694b85a217209787fe8c503a4b697dc6c2bfbe84

Hello Alex,

Initially we did enabled PGO & rust-demangler options for rustdoc 
reproducibility.

https://internals.rust-lang.org/t/rustdoc-binary-is-not-reproducible/20027/5

I did not get any info (from doc or community) on how and why optimation 
is affecting rustdoc binary.

https://internals.rust-lang.org/t/rustdoc-binary-is-not-reproducible/20027/6

However, later we learned that the '/rustdoc/' is reproducible without 
PGO also, and so removed for chromium project. And after removing PGO 
also we've not seen this rustdoc repro issue on autobuilder.


The issue is not reproduced on my end to confirm the PGO is root cause 
or any recent changes on rust recipe causing the issue?



/Sundeep


Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#200231): 
https://lists.openembedded.org/g/openembedded-core/message/200231
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [scarthgap][PATCH] glibc: stable 2.39 branch updates.

2024-05-17 Thread Sundeep KOKKONDA via lists.openembedded.org

Regression testing is done and below are the results:

Before glibc update:
-
Recipe       | Passed     | Failed   | Skipped  |
-
glibc        | 5037       | 123      | 156      |
glibc-user   | 4858       | 231      | 227      |
-

After glibc update:
-
Recipe       | Passed     | Failed   | Skipped  |
-
glibc        | 5043       | 123      | 156      |
glibc-user   | 4866       | 229      | 227      |
-

ptest shows below tests as failed after glibc update:
tst-malloc-fork-deadlock-malloc-check, tst-robustpi7, 
tst-thread-affinity-pthread2

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199522): 
https://lists.openembedded.org/g/openembedded-core/message/199522
Mute This Topic: https://lists.openembedded.org/mt/106156894/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] glibc: stable 2.39 branch updates.

2024-05-17 Thread Sundeep KOKKONDA via lists.openembedded.org

Regression testing is done and below are the results:

Before glibc update:
-
Recipe       | Passed     | Failed   | Skipped  |
-
glibc        | 5041       | 123      | 156      |
glibc-user   | 4854       | 239      | 227      |
-

After glibc update:
-
Recipe       | Passed     | Failed   | Skipped  |
-
glibc        | 5043       | 123      | 156      |
glibc-user   | 4863       | 232      | 227      |
-

ptest shows below tests as failed after glibc update:
tst-robustpi7, tst-tsearch, tst-dynarray-fail-mem, tst-loading, 
mtrace-tst-loading

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199521): 
https://lists.openembedded.org/g/openembedded-core/message/199521
Mute This Topic: https://lists.openembedded.org/mt/106156801/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [scarthgap][PATCH] binutils: stable 2.42 branch updates.

2024-05-17 Thread Sundeep KOKKONDA via lists.openembedded.org

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 Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] binutils: stable 2.42 branch updates.

2024-05-17 Thread Sundeep KOKKONDA via lists.openembedded.org

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 Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [scarthgap][PATCH] glibc: stable 2.39 branch updates.

2024-05-17 Thread Sundeep KOKKONDA via lists.openembedded.org

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 Force DT_RPATH for --enable-hardcoded-path-in-tests
71149c2a2e elf: Only process multiple tunable once (BZ 31686)
f8e4623421 Add a test to check for duplicate definitions in the static library
8b005d7869 i686: Fix multiple definitions of __memmove_chk and __memset_chk
8323a83abd i586: Fix multiple definitions of __memcpy_chk and __mempcpy_chk
5141d4d83c Revert "i586: Fix multiple definitions of __memcpy_chk and 
__mempcpy_chk"
c16871e662 Revert "i686: Fix multiple definitions of __memmove_chk and 
__memset_chk"
fa616ea373 Revert "Add a test to check for duplicate definitions in the static 
library"
ff110b2591 Add a test to check for duplicate definitions in the static library
ad92c483a4 i686: Fix multiple definitions of __memmove_chk and __memset_chk
3148714ab6 i586: Fix multiple definitions of __memcpy_chk and __mempcpy_chk
273a835fe7 time: Allow later version licensing.
acc56074b0 nscd: Use time_t for return type of addgetnetgrentX
836d43b989 login: structs utmp, utmpx, lastlog _TIME_BITS independence (bug 
30701)
9831f98c26 login: Check default sizes of structs utmp, utmpx, lastlog
fd658f026f elf: Also compile dl-misc.os with $(rtld-early-cflags)
a9a8d3eebb CVE-2024-33601, CVE-2024-33602: nscd: netgroup: Use two buffers in 
addgetnetgrentX (bug 31680)
c99f886de5 CVE-2024-33600: nscd: Avoid null pointer crashes after notfound 
response (bug 31678)
5a508e0b50 CVE-2024-33600: nscd: Do not send missing not-found response in 
addgetnetgrentX (bug 31678)
1263d583d2 CVE-2024-33599: nscd: Stack-based buffer overflow in netgroup cache 
(bug 31677)
2f8f157eb0 x86: Define MINIMUM_X86_ISA_LEVEL in config.h [BZ #31676]
e701c7d761 i386: ulp update for SSE2 --disable-multi-arch configurations
e828914cf9 nptl: Fix tst-cancel30 on kernels without ppoll_time64 support
31da30f23c iconv: ISO-2022-CN-EXT: fix out-of-bound writes when writing escape 
sequence (CVE-2024-2961)
423099a032 x86_64: Exclude SSE, AVX and FMA4 variants in libm multiarch
04df8652eb Apply the Makefile sorting fix
edb9a76e30 powerpc: Fix ld.so address determination for PCREL mode (bug 31640)
7b92f46f04 x86-64: Simplify minimum ISA check ifdef conditional with if
9883f4304c x86-64: Don't use SSE resolvers for ISA level 3 or above
9d92452c70 AArch64: Check kernel version for SVE ifuncs
395a89f61e aarch64: fix check for SVE support in assembler
b0e0a07018 aarch64/fpu: Sync libmvec routines from 2.39 and before with AOR
31c7d69af5 i386: Use generic memrchr in libc (bug 31316)
5d070d12b3 x86: Expand the comment on when REP STOSB is used on memset
6484a92698 x86: Do not prefer ERMS for memset on Zen3+
aa4249266e x86: Fix Zen3/Zen4 ERMS selection (BZ 30994)
5a461f2949 Add tst-gnu2-tls2mod1 to test-internal-extras
aded2fc004 elf: Enable TLS descriptor tests on aarch64
a8ba52bde5 arm: Update _dl_tlsdesc_dynamic to preserve caller-saved registers 
(BZ 31372)
15aebdbada Ignore undefined symbols for -mtls-dialect=gnu2
354cabcb26 x86-64: Allocate state buffer space for RDI, RSI and RBX
853e915fdd x86-64: Update _dl_tlsdesc_dynamic to preserve AMX registers
a364304718 x86: Update _dl_tlsdesc_dynamic to preserve caller-saved registers
7fc8242bf8 x86-64: Save APX registers in ld.so trampoline
983f34a125 LoongArch: Correct {__ieee754, _}_scalb -> {__ieee754, _}_scalbf
aad45c8ac3 powerpc: Placeholder and infrastructure/build support to add 
Power11 related changes.
ee7f4c54e1 powerpc: Add HWCAP3/HWCAP4 data to TCB for Power Architecture.
71fcdba577 linux: Use rseq area unconditionally in sched_getcpu (bug 31479)

Signed-off-by: Sundeep KOKKONDA 
---
 meta/recipes-core/glibc/glibc-version.inc |  2 +-
 ...y-the-header-between-arm-and-aarch64.patch |  8 ---
 ...e-Pass-mcpu-along-with-march-to-dete.patch | 62 ---
 meta/recipes-core/glibc/glibc_2.39.bb |  1 -
 4 files changed, 1 insertion(+), 72 deletions(-)
 delete mode 100644 
meta/recipes-core/glibc/glibc/0023-aarch64-configure-Pass-mcpu-along-with-march-to-dete.patch

diff --git a/meta/recipes-core/glibc/glibc-version.inc 
b/meta/recipes-core/glibc/glibc-version.inc
index 618a574566..20125e4339 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.39/master"
 PV = "2.39+git"
-SRCREV_glibc ?= "1b9c1a0047fb26a65a9b2a7b8cd977243f7d353c"
+SRCREV_glibc ?= "c7c3f5bf80ae86b34501f473f1a9fc545c911b7f"
 SRCREV_localedef ?= "fab74f31b3811df543e24b6de47efdf45b538abc"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
diff --git 
a/meta/recipes-core/glibc/glibc/0016-wordsize.h-Unify-the-header-between-arm-and-aarch64.patch

[OE-core] [scarthgap][PATCH] binutils: stable 2.42 branch updates.

2024-05-17 Thread Sundeep KOKKONDA via lists.openembedded.org

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 EVEX MAP4
d816fda3cbd aarch64: Remove B16B16, SVE2p1 and SME2p1
cb11047e34a Re: Move bfd_init to bfd.c
818bcf40efb print cached error messages using _bfd_error_handler
831be495ef1 aarch64: Fix the 2nd operand in gcsstr and gcssttr instructions.

Signed-off-by: Sundeep KOKKONDA 
---
 meta/recipes-devtools/binutils/binutils-2.42.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/binutils/binutils-2.42.inc 
b/meta/recipes-devtools/binutils/binutils-2.42.inc
index 3b6f47d4ce..b4d273c9c3 100644
--- a/meta/recipes-devtools/binutils/binutils-2.42.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.42.inc
@@ -20,7 +20,7 @@ UPSTREAM_CHECK_GITTAGREGEX = "binutils-(?P\d+_(\d_?)*)"
 
 CVE_STATUS[CVE-2023-25584] = "cpe-incorrect: Applies only for version 2.40 and 
earlier"
 
-SRCREV ?= "553c7f61b74badf91df484450944675efd9cd485"
+SRCREV ?= "73b22b4481e85635eb978585f405c4433bcc0174"
 BINUTILS_GIT_URI ?= 
"git://sourceware.org/git/binutils-gdb.git;branch=${SRCBRANCH};protocol=https"
 SRC_URI = "\
  ${BINUTILS_GIT_URI} \
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199517): 
https://lists.openembedded.org/g/openembedded-core/message/199517
Mute This Topic: https://lists.openembedded.org/mt/106156829/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] glibc: stable 2.39 branch updates.

2024-05-17 Thread Sundeep KOKKONDA via lists.openembedded.org

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 definition without multiarch 
(x86-64-v4)
97bb89668d Force DT_RPATH for --enable-hardcoded-path-in-tests
71149c2a2e elf: Only process multiple tunable once (BZ 31686)
f8e4623421 Add a test to check for duplicate definitions in the static library
8b005d7869 i686: Fix multiple definitions of __memmove_chk and __memset_chk
8323a83abd i586: Fix multiple definitions of __memcpy_chk and __mempcpy_chk
5141d4d83c Revert "i586: Fix multiple definitions of __memcpy_chk and 
__mempcpy_chk"
c16871e662 Revert "i686: Fix multiple definitions of __memmove_chk and 
__memset_chk"
fa616ea373 Revert "Add a test to check for duplicate definitions in the static 
library"
ff110b2591 Add a test to check for duplicate definitions in the static library
ad92c483a4 i686: Fix multiple definitions of __memmove_chk and __memset_chk
3148714ab6 i586: Fix multiple definitions of __memcpy_chk and __mempcpy_chk

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 1e4a323d64..20125e4339 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.39/master"
 PV = "2.39+git"
-SRCREV_glibc ?= "273a835fe7c685cc54266bb8b502787bad5e9bae"
+SRCREV_glibc ?= "c7c3f5bf80ae86b34501f473f1a9fc545c911b7f"
 SRCREV_localedef ?= "fab74f31b3811df543e24b6de47efdf45b538abc"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199516): 
https://lists.openembedded.org/g/openembedded-core/message/199516
Mute This Topic: https://lists.openembedded.org/mt/106156801/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] binutils: stable 2.42 branch updates.

2024-05-17 Thread Sundeep KOKKONDA via lists.openembedded.org

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 EVEX MAP4
d816fda3cbd aarch64: Remove B16B16, SVE2p1 and SME2p1
cb11047e34a Re: Move bfd_init to bfd.c
818bcf40efb print cached error messages using _bfd_error_handler
831be495ef1 aarch64: Fix the 2nd operand in gcsstr and gcssttr instructions.

Signed-off-by: Sundeep KOKKONDA 
---
 meta/recipes-devtools/binutils/binutils-2.42.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/binutils/binutils-2.42.inc 
b/meta/recipes-devtools/binutils/binutils-2.42.inc
index 3b6f47d4ce..b4d273c9c3 100644
--- a/meta/recipes-devtools/binutils/binutils-2.42.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.42.inc
@@ -20,7 +20,7 @@ UPSTREAM_CHECK_GITTAGREGEX = "binutils-(?P\d+_(\d_?)*)"
 
 CVE_STATUS[CVE-2023-25584] = "cpe-incorrect: Applies only for version 2.40 and 
earlier"
 
-SRCREV ?= "553c7f61b74badf91df484450944675efd9cd485"
+SRCREV ?= "73b22b4481e85635eb978585f405c4433bcc0174"
 BINUTILS_GIT_URI ?= 
"git://sourceware.org/git/binutils-gdb.git;branch=${SRCBRANCH};protocol=https"
 SRC_URI = "\
  ${BINUTILS_GIT_URI} \
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199515): 
https://lists.openembedded.org/g/openembedded-core/message/199515
Mute This Topic: https://lists.openembedded.org/mt/106156744/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH V2] rust: reproducibility issue fix with v1.75

2024-03-08 Thread Sundeep KOKKONDA via lists.openembedded.org

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(+), 12 deletions(-)

diff --git a/meta/recipes-devtools/rust/files/repro-issue-fix-with-v175.patch 
b/meta/recipes-devtools/rust/files/repro-issue-fix-with-v175.patch
index 6840bafff8..fe0507c981 100644
--- a/meta/recipes-devtools/rust/files/repro-issue-fix-with-v175.patch
+++ b/meta/recipes-devtools/rust/files/repro-issue-fix-with-v175.patch
@@ -1,23 +1,36 @@
 rust: reproducibility issue fix with v1.75
 
-With 1.75 rust release, the '.rustc' section of shared object libs are 
embedded with absolute path names which is casuing reproducibiluty issues.
+With 1.75 rust release, the '.rustc' section of shared object libs are 
embedded with absolute path names which is casuing reproducibility issues.
 This change will fix the path name format back to '/rust/$hash' as in earlier 
versions.
 
 Below are the links for detailed bug description & discusssion with upstream 
rust.
 https://github.com/rust-lang/rust/issues/120825#issuecomment-1964307219
 https://github.com/rust-lang/rust/issues/120825#issuecomment-1964652656
 
-Upstream-Status: Inappropriate [patches need rework]
+Upstream-Status: Backport 
[https://github.com/rust-lang/rust/pull/121959/commits/a9a979839bbdfec48c75d618ab0dce8a953589b8]
 Signed-off-by: Sundeep KOKKONDA 
 ---
 a/compiler/rustc_session/src/session.rs2023-12-21 08:55:28.0 
-0800
-+++ b/compiler/rustc_session/src/session.rs2024-02-26 07:29:15.527577022 
-0800
-@@ -1269,7 +1269,7 @@
- | CrateType::Rlib
- | CrateType::Staticlib
- | CrateType::Cdylib => continue,
+--- a/compiler/rustc_session/src/session.rs 2023-12-21 08:55:28.0 
-0800
 b/compiler/rustc_session/src/session.rs 2024-02-26 07:29:15.527577022 
-0800
+@@ -1260,19 +1260,6 @@
+ }
+
+ pub fn should_prefer_remapped_for_codegen() -> bool {
+-// bail out, if any of the requested crate types aren't:
+-// "compiled executables or libraries"
+-for crate_type in _types {
+-match crate_type {
+-CrateType::Executable
+-| CrateType::Dylib
+-| CrateType::Rlib
+-| CrateType::Staticlib
+-| CrateType::Cdylib => continue,
 -CrateType::ProcMacro => return false,
-+CrateType::ProcMacro => return true,
- }
- }
- 
+-}
+-}
+-
+ let has_split_debuginfo = match self.split_debuginfo() {
+ SplitDebuginfo::Off => false,
+ SplitDebuginfo::Packed => true,
+
+
-- 
2.43.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196856): 
https://lists.openembedded.org/g/openembedded-core/message/196856
Mute This Topic: https://lists.openembedded.org/mt/104810810/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 4/4] rust: Upgrade 1.74.1 -> 1.75.0

2024-01-11 Thread Sundeep KOKKONDA via lists.openembedded.org

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.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193545): 
https://lists.openembedded.org/g/openembedded-core/message/193545
Mute This Topic: https://lists.openembedded.org/mt/103433093/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] rust: rustdoc reproducibility issue fix

2023-12-20 Thread Sundeep KOKKONDA via lists.openembedded.org

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 to this group.
View/Reply Online (#192790): 
https://lists.openembedded.org/g/openembedded-core/message/192790
Mute This Topic: https://lists.openembedded.org/mt/103278939/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] rust: rustdoc reproducibility issue fix

2023-12-20 Thread Sundeep KOKKONDA via lists.openembedded.org

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 but enabled in Yocto 
and causing the issue in rustdoc binary. To fix the issue this optimization is 
set to it's default 'false'.
More about the optimization: 
https://doc.rust-lang.org/rustc/profile-guided-optimization.html

Reverted commit #3e50e45917 "rust: Split rustdoc into a separate package"

Signed-off-by: Sundeep KOKKONDA 
---
 meta/lib/oeqa/selftest/cases/reproducible.py | 2 --
 meta/recipes-devtools/rust/rust_1.71.1.bb| 7 +++
 2 files changed, 3 insertions(+), 6 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 14ccb0b24d..80e830136f 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -16,8 +16,6 @@ import os
 import datetime
 
 exclude_packages = [
-   'rust-rustdoc',
-   'rust-dbg'
]
 
 def is_excluded(package):
diff --git a/meta/recipes-devtools/rust/rust_1.71.1.bb 
b/meta/recipes-devtools/rust/rust_1.71.1.bb
index 3d176e54c1..a0e9316cfd 100644
--- a/meta/recipes-devtools/rust/rust_1.71.1.bb
+++ b/meta/recipes-devtools/rust/rust_1.71.1.bb
@@ -141,13 +141,14 @@ python do_configure() {
 config.add_section("build")
 config.set("build", "submodules", e(False))
 config.set("build", "docs", e(False))
+config.set("build", "tools", ["rust-demangler",])
 
 rustc = d.expand("${WORKDIR}/rust-snapshot/bin/rustc")
 config.set("build", "rustc", e(rustc))
 
 # Support for the profiler runtime to generate e.g. coverage report,
 # PGO etc.
-config.set("build", "profiler", e(True))
+config.set("build", "profiler", e(False))
 
 cargo = d.expand("${WORKDIR}/rust-snapshot/bin/cargo")
 config.set("build", "cargo", e(cargo))
@@ -225,11 +226,9 @@ do_test_compile () {
 
 ALLOW_EMPTY:${PN} = "1"
 
-PACKAGES =+ "${PN}-rustdoc ${PN}-tools-clippy ${PN}-tools-rustfmt"
-FILES:${PN}-rustdoc = "${bindir}/rustdoc"
+PACKAGES =+ "${PN}-tools-clippy ${PN}-tools-rustfmt"
 FILES:${PN}-tools-clippy = "${bindir}/cargo-clippy ${bindir}/clippy-driver"
 FILES:${PN}-tools-rustfmt = "${bindir}/rustfmt"
-RDEPENDS:${PN}-rustdoc = "${PN}"
 RDEPENDS:${PN}-tools-clippy = "${PN}"
 RDEPENDS:${PN}-tools-rustfmt = "${PN}"
 
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192789): 
https://lists.openembedded.org/g/openembedded-core/message/192789
Mute This Topic: https://lists.openembedded.org/mt/103278939/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [nanbield][PATCH] binutils: stable 2.41 branch updates

2023-12-14 Thread Sundeep KOKKONDA via lists.openembedded.org

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: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [nanbield][PATCH] binutils: stable 2.41 branch updates

2023-12-14 Thread Sundeep KOKKONDA via lists.openembedded.org

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-by: Sundeep KOKKONDA 
---
 meta/recipes-devtools/binutils/binutils-2.41.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/binutils/binutils-2.41.inc 
b/meta/recipes-devtools/binutils/binutils-2.41.inc
index b4934c02a8..d4b239258d 100644
--- a/meta/recipes-devtools/binutils/binutils-2.41.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.41.inc
@@ -18,7 +18,7 @@ SRCBRANCH ?= "binutils-2_41-branch"
 
 UPSTREAM_CHECK_GITTAGREGEX = "binutils-(?P\d+_(\d_?)*)"
 
-SRCREV ?= "cb4c3555ac4cf8aaf0935cb6e4b09e6882436d21"
+SRCREV ?= "e13f70c7fcb2f4a39ddad4ccb83660dbfee2caeb"
 BINUTILS_GIT_URI ?= 
"git://sourceware.org/git/binutils-gdb.git;branch=${SRCBRANCH};protocol=https"
 SRC_URI = "\
  ${BINUTILS_GIT_URI} \
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192357): 
https://lists.openembedded.org/g/openembedded-core/message/192357
Mute This Topic: https://lists.openembedded.org/mt/103167965/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [nanbield][PATCH] glibc: stable 2.38 branch updates

2023-12-14 Thread Sundeep KOKKONDA via lists.openembedded.org

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: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [nanbield][PATCH] glibc: stable 2.38 branch updates

2023-12-14 Thread Sundeep KOKKONDA via lists.openembedded.org

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]
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 "elf: Remove unused 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..0ef4289557 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.38/master"
 PV = "2.38+git"
-SRCREV_glibc ?= "750a45a783906a19591fb8ff6b7841470f1f5701"
+SRCREV_glibc ?= "44f757a6364a546359809d48c76b3debd26e77d4"
 SRCREV_localedef ?= "e0eca29583b9e0f62645c4316ced93cf4e4e26e1"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#192354): 
https://lists.openembedded.org/g/openembedded-core/message/192354
Mute This Topic: https://lists.openembedded.org/mt/103167941/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH V2] glibc: stable 2.38 branch updates

2023-11-28 Thread Sundeep KOKKONDA via lists.openembedded.org

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 "elf: Remove unused 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..ccf9d505c5 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.38/master"
 PV = "2.38+git"
-SRCREV_glibc ?= "750a45a783906a19591fb8ff6b7841470f1f5701"
+SRCREV_glibc ?= "1e04dcec491bd8f48b5b74ce3e8414132578a645"
 SRCREV_localedef ?= "e0eca29583b9e0f62645c4316ced93cf4e4e26e1"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#191347): 
https://lists.openembedded.org/g/openembedded-core/message/191347
Mute This Topic: https://lists.openembedded.org/mt/102847456/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] glibc: stable 2.38 branch updates

2023-11-26 Thread Sundeep KOKKONDA via lists.openembedded.org

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: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] glibc: stable 2.38 branch updates

2023-11-26 Thread Sundeep KOKKONDA via lists.openembedded.org

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 "elf: Remove unused 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..ccf9d505c5 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.38/master"
 PV = "2.38+git"
-SRCREV_glibc ?= "750a45a783906a19591fb8ff6b7841470f1f5701"
+SRCREV_glibc ?= "1e04dcec491bd8f48b5b74ce3e8414132578a645"
 SRCREV_localedef ?= "e0eca29583b9e0f62645c4316ced93cf4e4e26e1"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#191246): 
https://lists.openembedded.org/g/openembedded-core/message/191246
Mute This Topic: https://lists.openembedded.org/mt/102823529/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] binutils: stable 2.41 branch updates

2023-11-26 Thread Sundeep KOKKONDA via lists.openembedded.org

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: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] binutils: stable 2.41 branch updates

2023-11-26 Thread Sundeep KOKKONDA via lists.openembedded.org

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 
---
 meta/recipes-devtools/binutils/binutils-2.41.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/binutils/binutils-2.41.inc 
b/meta/recipes-devtools/binutils/binutils-2.41.inc
index b4934c02a8..804f092965 100644
--- a/meta/recipes-devtools/binutils/binutils-2.41.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.41.inc
@@ -18,7 +18,7 @@ SRCBRANCH ?= "binutils-2_41-branch"
 
 UPSTREAM_CHECK_GITTAGREGEX = "binutils-(?P\d+_(\d_?)*)"
 
-SRCREV ?= "cb4c3555ac4cf8aaf0935cb6e4b09e6882436d21"
+SRCREV ?= "c1321df4eb0a136304205085cd4913dd4eb01054"
 BINUTILS_GIT_URI ?= 
"git://sourceware.org/git/binutils-gdb.git;branch=${SRCBRANCH};protocol=https"
 SRC_URI = "\
  ${BINUTILS_GIT_URI} \
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#191244): 
https://lists.openembedded.org/g/openembedded-core/message/191244
Mute This Topic: https://lists.openembedded.org/mt/102823484/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] rust: rust package split

2023-11-21 Thread Sundeep KOKKONDA via lists.openembedded.org

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(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 029b6af331..14ccb0b24d 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -16,7 +16,7 @@ import os
 import datetime
 
 exclude_packages = [
-   'rust',
+   'rust-rustdoc',
'rust-dbg'
]
 
diff --git a/meta/recipes-devtools/rust/rust_1.70.0.bb 
b/meta/recipes-devtools/rust/rust_1.70.0.bb
index 16d433910f..a7efd2f7f0 100644
--- a/meta/recipes-devtools/rust/rust_1.70.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.70.0.bb
@@ -232,9 +232,11 @@ do_test_compile () {
 
 ALLOW_EMPTY:${PN} = "1"
 
-PACKAGES =+ "${PN}-tools-clippy ${PN}-tools-rustfmt"
+PACKAGES =+ "${PN}-rustdoc ${PN}-tools-clippy ${PN}-tools-rustfmt"
+FILES:${PN}-rustdoc = "${bindir}/rustdoc"
 FILES:${PN}-tools-clippy = "${bindir}/cargo-clippy ${bindir}/clippy-driver"
 FILES:${PN}-tools-rustfmt = "${bindir}/rustfmt"
+RDEPENDS:${PN}-rustdoc = "${PN}"
 RDEPENDS:${PN}-tools-clippy = "${PN}"
 RDEPENDS:${PN}-tools-rustfmt = "${PN}"
 
-- 
2.42.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#190998): 
https://lists.openembedded.org/g/openembedded-core/message/190998
Mute This Topic: https://lists.openembedded.org/mt/102742230/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v3] rust: Upgrade 1.70.0 -> 1.71.0

2023-10-20 Thread Sundeep KOKKONDA via lists.openembedded.org

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): 
https://lists.openembedded.org/g/openembedded-core/message/189570
Mute This Topic: https://lists.openembedded.org/mt/100936266/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v3] rust: Upgrade 1.70.0 -> 1.71.0

2023-10-19 Thread Sundeep KOKKONDA via lists.openembedded.org

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 your 
analysis.

Thanks,
Sundeep K.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#189470): 
https://lists.openembedded.org/g/openembedded-core/message/189470
Mute This Topic: https://lists.openembedded.org/mt/100936266/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [mickledore] glibc: stable 2.37 branch updates.

2023-10-12 Thread Sundeep KOKKONDA via lists.openembedded.org

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: https://lists.openembedded.org/mt/101774187/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] rust: reproducibility issue fix

2023-10-11 Thread Sundeep KOKKONDA via lists.openembedded.org

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): 
https://lists.openembedded.org/g/openembedded-core/message/188961
Mute This Topic: https://lists.openembedded.org/mt/101890610/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] rust: reproducibility issue fix

2023-10-10 Thread Sundeep KOKKONDA via lists.openembedded.org

[Yocto#14875]
The '--remap-path-prefix' option removes all references to build directory 
structure in the debug information within the compiled output for Cargo 
dependencies and the project's binary.
However, some references to build directories remains in the final binary in 
.rustc section 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/lib/oeqa/selftest/cases/reproducible.py | 2 --
 meta/recipes-devtools/rust/rust_1.70.0.bb| 1 +
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/reproducible.py 
b/meta/lib/oeqa/selftest/cases/reproducible.py
index 84c6c3a05f..9b4a0887dd 100644
--- a/meta/lib/oeqa/selftest/cases/reproducible.py
+++ b/meta/lib/oeqa/selftest/cases/reproducible.py
@@ -16,8 +16,6 @@ import os
 import datetime
 
 exclude_packages = [
-   'rust',
-   'rust-dbg'
]
 
 def is_excluded(package):
diff --git a/meta/recipes-devtools/rust/rust_1.70.0.bb 
b/meta/recipes-devtools/rust/rust_1.70.0.bb
index 3b9c05a19f..16d433910f 100644
--- a/meta/recipes-devtools/rust/rust_1.70.0.bb
+++ b/meta/recipes-devtools/rust/rust_1.70.0.bb
@@ -130,6 +130,7 @@ python do_configure() {
 # [rust]
 config.add_section("rust")
 config.set("rust", "rpath", e(True))
+config.set("rust", "remap-debuginfo", e(True))
 config.set("rust", "channel", e(d.expand("${RUST_CHANNEL}")))
 
 # Whether or not to optimize the compiler and standard library
-- 
2.39.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188940): 
https://lists.openembedded.org/g/openembedded-core/message/188940
Mute This Topic: https://lists.openembedded.org/mt/101890610/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [kirkstone][PATCH] gcc : upgrade to v11.4

2023-07-31 Thread Sundeep KOKKONDA via lists.openembedded.org

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 failures as reported earlier by Richard and 
we will look into these gcc failures after that.
PASSgcc.c-torture/compile/pr106030.c
PASSgcc.c-torture/compile/pr106030.c
PASSgcc.c-torture/compile/pr106030.c
PASSgcc.c-torture/compile/pr106030.c
PASSgcc.c-torture/compile/pr106030.c
PASSgcc.c-torture/compile/pr106030.c
PASSgcc.c-torture/compile/pr106030.c
PASSgcc.c-torture/compile/pr106751.c
PASSgcc.c-torture/compile/pr106751.c
PASSgcc.c-torture/compile/pr106751.c
PASSgcc.c-torture/compile/pr106751.c
PASSgcc.c-torture/compile/pr106751.c
PASSgcc.c-torture/compile/pr106751.c
PASSgcc.c-torture/compile/pr106751.c
PASSgcc.c-torture/compile/pr106751.c
PASSgcc.c-torture/compile/pr107997.c
PASSgcc.c-torture/compile/pr107997.c
PASSgcc.c-torture/compile/pr107997.c
PASSgcc.c-torture/compile/pr107997.c
PASSgcc.c-torture/compile/pr107997.c
PASSgcc.c-torture/compile/pr107997.c
PASSgcc.c-torture/compile/pr107997.c
PASSgcc.c-torture/compile/pr107997.c
PASSgcc.c-torture/compile/pr108237.c
PASSgcc.c-torture/compile/pr108237.c
PASSgcc.c-torture/compile/pr108237.c
PASSgcc.c-torture/compile/pr108237.c
PASSgcc.c-torture/compile/pr108237.c
PASSgcc.c-torture/compile/pr108237.c
PASSgcc.c-torture/compile/pr108237.c
PASSgcc.c-torture/compile/pr108596.c
PASSgcc.c-torture/compile/pr108596.c
PASSgcc.c-torture/compile/pr108596.c
PASSgcc.c-torture/compile/pr108596.c
PASSgcc.c-torture/compile/pr108596.c
PASSgcc.c-torture/compile/pr108596.c
PASSgcc.c-torture/compile/pr108596.c
PASSgcc.c-torture/compile/pr108688-1.c
PASSgcc.c-torture/compile/pr108688-1.c
PASSgcc.c-torture/compile/pr108688-1.c
PASSgcc.c-torture/compile/pr108688-1.c
PASSgcc.c-torture/compile/pr108688-1.c
PASSgcc.c-torture/compile/pr108688-1.c
PASSgcc.c-torture/compile/pr108688-1.c
PASSgcc.c-torture/compile/pr108688-1.c
PASSgcc.c-torture/execute/pr106032.c
FAILgcc.c-torture/execute/pr106032.c
PASSgcc.c-torture/execute/pr106032.c
FAILgcc.c-torture/execute/pr106032.c
PASSgcc.c-torture/execute/pr106032.c
FAILgcc.c-torture/execute/pr106032.c
PASSgcc.c-torture/execute/pr106032.c
FAILgcc.c-torture/execute/pr106032.c
PASSgcc.c-torture/execute/pr106032.c
FAILgcc.c-torture/execute/pr106032.c
PASSgcc.c-torture/execute/pr106032.c
FAILgcc.c-torture/execute/pr106032.c
PASSgcc.c-torture/execute/pr106032.c
FAILgcc.c-torture/execute/pr106032.c
PASSgcc.c-torture/execute/pr108498-1.c
FAILgcc.c-torture/execute/pr108498-1.c
PASSgcc.c-torture/execute/pr108498-1.c
FAILgcc.c-torture/execute/pr108498-1.c
PASSgcc.c-torture/execute/pr108498-1.c
FAILgcc.c-torture/execute/pr108498-1.c
PASSgcc.c-torture/execute/pr108498-1.c
FAILgcc.c-torture/execute/pr108498-1.c
PASSgcc.c-torture/execute/pr108498-1.c
FAILgcc.c-torture/execute/pr108498-1.c
PASSgcc.c-torture/execute/pr108498-1.c
FAILgcc.c-torture/execute/pr108498-1.c
PASSgcc.c-torture/execute/pr108498-1.c
FAILgcc.c-torture/execute/pr108498-1.c
PASSgcc.c-torture/execute/pr108498-2.c
FAILgcc.c-torture/execute/pr108498-2.c
PASSgcc.c-torture/execute/pr108498-2.c
FAILgcc.c-torture/execute/pr108498-2.c
PASSgcc.c-torture/execute/pr108498-2.c
FAILgcc.c-torture/execute/pr108498-2.c
PASSgcc.c-torture/execute/pr108498-2.c
FAILgcc.c-torture/execute/pr108498-2.c
PASSgcc.c-torture/execute/pr108498-2.c
FAILgcc.c-torture/execute/pr108498-2.c
PASSgcc.c-torture/execute/pr108498-2.c
FAILgcc.c-torture/execute/pr108498-2.c
PASSgcc.c-torture/execute/pr108498-2.c
FAILgcc.c-torture/execute/pr108498-2.c
PASSgcc.c-torture/execute/pr109778.c
FAILgcc.c-torture/execute/pr109778.c
PASSgcc.c-torture/execute/pr109778.c
FAILgcc.c-torture/execute/pr109778.c
PASSgcc.c-torture/execute/pr109778.c
FAILgcc.c-torture/execute/pr109778.c
PASSgcc.c-torture/execute/pr109778.c
FAILgcc.c-torture/execute/pr109778.c
PASSgcc.c-torture/execute/pr109778.c
FAILgcc.c-torture/execute/pr109778.c
PASSgcc.c-torture/execute/pr109778.c
FAILgcc.c-torture/execute/pr109778.c
PASSgcc.c-torture/execute/pr109778.c
FAILgcc.c-torture/execute/pr109778.c
PASSgcc.dg/analyzer/pr105252.c
PASSgcc.dg/analyzer/pr105365.c
PASSgcc.dg/analyzer/pr105366.c
PASSc-c++-common/cpp/va-opt-10.c  -Wc++-compat  (test for excess errors)
PASSgcc.dg/dfp/pr108068.c
FAILgcc.dg/dfp/pr108068.c
UNSUPPORTED gcc.dg/darwin-aligned-globals.c
UNSUPPORTED gcc.dg/darwin-comm-1.c
PASSgcc.dg/pr104464.c
PASSgcc.dg/pr105140.c
PASS

Re: [OE-core] [kirkstone][PATCH] gcc : upgrade to v11.4

2023-07-27 Thread Sundeep KOKKONDA via lists.openembedded.org

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
# of expected failures                            782                    782
# of unresolved testcases                     10                      10
# of unsupported tests                           2760                  2773

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184928): 
https://lists.openembedded.org/g/openembedded-core/message/184928
Mute This Topic: https://lists.openembedded.org/mt/100387943/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [kirkstone][PATCH] gcc : upgrade to v11.4

2023-07-27 Thread Sundeep KOKKONDA via lists.openembedded.org

gcc stable version upgraded from v11.3 to v11.4

For changes in v11.4 see - https://gcc.gnu.org/gcc-11/changes.html

Below is the bug fix list for v11.4
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED=short_desc%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id_format=advanced=FIXED_milestone=11.4

There are a total 115 bugs are fixed in this release, below is the list of bugs 
fixed excluding the regression fixes.

ID  Product CompResolution  Summary▲
108199  gcc tree-optFIXEBitfields, unions and SRA and 
storage_order_attribute
107801  gcc libstdc+FIXEBuilding cross compiler for H8 family 
fails in libstdc++ (c++17/memory_resource.cc)
108265  gcc libstdc+FIXEchrono::hh_mm_ss can't be constructed 
from unsigned durations
104443  gcc libstdc+FIXEcommon_iterator::operator-> is 
not correctly implemented
98056   gcc c++ FIXEcoroutines: ICE tree check: expected 
record_type or union_type or qual_union_type, have array_type since 
r11-2183-g0f66b8486cea8668
107061  gcc target  FIXEENCODEKEY128 clobbers xmm4-xmm6
105433  gcc testsuitFIXEFAIL: 
gcc.target/i386/iamcu/test_3_element_struct_and_unions.c
105095  gcc testsuitFIXEgcc.dg/vect/complex/fast-math-complex-* 
tests are not executed
100474  gcc c++ FIXEICE: in diagnose_trait_expr, at 
cp/constraint.cc:3706
105854  gcc target  FIXEICE: in extract_constrain_insn, at 
recog.cc:2692 (insn does not satisfy its constraints: sse2_lshrv1ti3)
104462  gcc target  FIXEICE: in extract_constrain_insn_cached, 
at recog.cc:2682 with -mavx512fp16 -mno-xsave
106045  gcc libgomp FIXEIncorrect testcase in 
libgomp.c/target-31.c at -O0
56189   gcc c++ FIXEInfinite recursion with noexcept when 
instantiating function template
100295  gcc c++ FIXEInternal compiler error from generic 
lambda capturing parameter pack and expanding it in if constexpr
100613  gcc jit FIXElibgccjit should produce dylib on macOS
104875  gcc libstdc+FIXE
libstdc++-v3/src/c++11/codecvt.cc:312:24: warning: left shift count >= width of 
type
107471  gcc libstdc+FIXEmismatching constraints in 
common_iterator
105284  gcc libstdc+FIXEmissing syncstream and spanstream 
forward decl. in 
98821   gcc c++ FIXEmodules : c++tools configures with CC 
but code fragments assume CXX.
109846  gcc fortran FIXEPointer-valued function reference 
rejected as actual argument
101324  gcc target  FIXEpowerpc64le: hashst appears before mflr 
at -O1 or higher
102479  gcc c++ FIXEsegfault when deducing class template 
arguments for tuple with libc++-14
105128  gcc libstdc+FIXEsource_location compile error for 
latest clang 15
106183  gcc libstdc+FIXEstd::atomic::wait might fail to be 
unblocked by notify_one/all on platforms without platform_wait()
102994  gcc libstdc+FIXEstd::atomic::wait is not marked 
const
105324  gcc libstdc+FIXEstd::from_chars() assertion at 
floating_from_chars.cc:78 when parsing 1.
105375  gcc libstdc+FIXEstd::packaged_task has no deduction 
guide.
104602  gcc libstdc+FIXEstd::source_location::current uses cast 
from void*
106808  gcc libstdc+FIXEstd::string_view range concept 
requirement causes compile 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 +-
 ...ian_11.3.bb => gcc-cross-canadian_11.4.bb} |   0
 .../{gcc-cross_11.3.bb => gcc-cross_11.4.bb}  |   0
 ...-crosssdk_11.3.bb => gcc-crosssdk_11.4.bb} |   0
 ...cc-runtime_11.3.bb => gcc-runtime_11.4.bb} |   0
 ...itizers_11.3.bb => gcc-sanitizers_11.4.bb} |   0
 ...{gcc-source_11.3.bb => gcc-source_11.4.bb} |   0
 ...rch64-Update-Neoverse-N2-core-defini.patch |  20 ++--
 ...rm-add-armv9-a-architecture-to-march.patch |  54 +-
 ...AMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch | 102 +-
 ...s-fix-v4bx-to-linker-to-support-EABI.patch |   6 +-
 .../gcc/{gcc_11.3.bb => gcc_11.4.bb}  |   0
 ...initial_11.3.bb => libgcc-initial_11.4.bb} |   0
 .../gcc/{libgcc_11.3.bb => libgcc_11.4.bb}|   0
 ...ibgfortran_11.3.bb => libgfortran_11.4.bb} |   0
 15 files changed, 92 insertions(+), 96 deletions(-)
 rename meta/recipes-devtools/gcc/{gcc-11.3.inc => gcc-11.4.inc} (97%)
 rename meta/recipes-devtools/gcc/{gcc-cross-canadian_11.3.bb => 
gcc-cross-canadian_11.4.bb} (100%)
 rename meta/recipes-devtools/gcc/{gcc-cross_11.3.bb => gcc-cross_11.4.bb} 
(100%)
 rename

Re: [OE-core] Rust Oe-Selftest implementation V15 Testing

2023-07-19 Thread Sundeep KOKKONDA via lists.openembedded.org




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 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 Wed, Jul 19, 2023 at 11:49 AM Richard Purdie
 wrote:
>
> On Mon, 2023-07-17 at 16:08 +0100, Richard Purdie wrote:
> > On Mon, 2023-07-17 at 16:34 +0200, Alexandre Belloni wrote:
> > > Hello,
> > >
> > > I got some feedback from RP:
> > >
> > > http://autobuilder.yocto.io/pub/non-release/20230716-18/testresults/testresult-report.txt
> > >
> > > This shows warnings for duplicate tests and he also asks being where the
> > > qemuarm64 went, both issues being probably related.
> >
> > I had a look and you probably need to add a:
> >
> > @OETestTag("toolchain-user")
> > @OETestTag("runqemu")
> > class RustSelfTestBase(RustSelfTestSystemEmulated):
> > def test_check(self):
> > self.test_rust()
> >
> > section to the tests to allow the tests to run for the non-IA
> > architectures that use usermode emulation for the other tests which
> > rust can't.
> >
> > That then just brings the question of why there are duplicate tests
> > results being reported. This is where the result for an ID is being
> > reported more than once. I haven't looked into why that might be
> > happening.
>
> I really do want to get this rust test suite issue resolved so I went
> digging into the code to find out what is really going on.
>
> Firstly, the duplicate test results. The issue is that you defined the
> core class like this:
>
>  class RustSelfTestSystemEmulated(OESelftestTestCase, OEPTestResultTestCase):
>  def test_rust
>
> and python unittest has a convention where anything starting "test_" is
> a test.
>
> This meant that the rust test ran unguarded in all the oe-selftest
> targets on the autobuilder and not just in the toolchain-system
> filtered section.
>
> The easiest fix is to drop the RustSelfTestBase class and move the
> toolchain-system decorator to RustSelfTestSystemEmulated. That will
> resolve the duplicate test warnings and ensure things run where they
> should. You could have worked out this issue by finding that there were
> rust test results in oe-selftest-* testresults.json files, e.g. here:
>
> http://autobuilder.yocto.io/pub/non-release/20230716-18/testresults/oe-selftest-centos/oeqa/testresults.json
>
> Moving on, the test result names really don't look good with the
> "[ui]  " and similar prefixes in the results file. I've patched a tweak
> in to drop that.
>
> I also noticed that there were no skipped tests being reported in the
> results. This was due to "SKIP" being used instead of "SKIPPED" which
> resulttool looks for.
>
> We need to also add the toolchain-user decorator to make sure that the
> tests run for the "user" architectures since we don't have any user
> mode rust test equivalent.
>
> I've rolled all these changes into a patch on master-next:
>
> https://git.yoctoproject.org/poky/commit/?h=master-next=46ab84785da15ac156ee0b4a693ce8bb5ccf8c22
>
> which I'll put into testing.
>
> Looking to the future, I have concerns about the ease of maintenance of
> this huge patch to rust to disable failing tests. I'd propose we change
> this to a hardcoded list of tests to ignore in the result parsing code
> which will be easier to maintain in the future.
>

That feels far more maintainable - the scale of the  patch really
concerned me. Also I guess if it's just a list, then running with
everything enabled on upgrade to see what passes/fails would be a
relatively easy option.

Hello Alex, Hello Richard,

During next rebase to rust 1.71.0 we will update this.



> We may want to take that as a subsequent follow up patch.
>
> Cheers,
>
> Richard
>
> 
>


--
Alex Kiernan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184582): 
https://lists.openembedded.org/g/openembedded-core/message/184582
Mute This Topic: https://lists.openembedded.org/mt/100232853/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [mickledore][PATCH] gcc : upgrade to v12.3

2023-06-25 Thread Sundeep KOKKONDA via lists.openembedded.org




From: MacLeod, Randy 
Sent: 24 June 2023 23:36
To: Kokkonda, Sundeep ; 
openembedded-core@lists.openembedded.org 
; Khem Raj 
Cc: Gowda, Naveen ; Moodalappa, Shivaprasad 
; Shinde, Yash 
; Hemraj, Deepthi ; 
umesh.kala...@windriver.com 
Subject: Re: [mickledore][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=FIXED_milestone=12.3

Thanks Sundeep.


Did you run a toochain regression test and if so what are the before, after, 
delta stats

and your summary/analysis of the results?




Hello Randy,


Testing is done and the results shared with community.

https://lists.openembedded.org/g/openembedded-core/message/183347

Thanks,
Sundeep K.




It isn't a strict requirement but if it's easy, then it's good to copy data 
into the commit log rather than link it.

In this case, there are 129 bugs so that's too much info and a link is sensible 
but
it's nice if it's accompanied with a summary.
I don't think we need a commit log update but I'll summarize what I noticed 
below
to give you an indication of what I'd like to see in future commits.

Most of the bugs linked are "Regression" fixes leaving:

https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED_known_to_fail_type=allwords_known_to_work_type=allwords=gcc_format=advanced=FIXED_desc=Regression_desc_type=notregexp_milestone=12.3

IDProduct Comp Assignee Summary
103387 gcc libstdc+redi  powerpc64le: segmentation 
fault on std::cout with ieee128 long doubl
109094 gcc analyzerdmalcolmUninit false positive from 
-fanalyzer when longjmp unwinds frames
106721 gcc targetjakub   Error: invalid character 
'<' in mnemonic since r13-2122-g86c0d98620e
100103 gcc fortran   jrfsousa   Automatic reallocation 
fails inside select rank
107551 gcc targetmarxin __builtin_cpu_supports 
returns a negative integer for "x86-64"
98487   gcc c mpolacek   ICE: tree check: expected 
identifier_node, have tree_list in is_attribut
109427 gcc tree-opt pinskiaparam=vect-induction-float= 
has a typo for IntegerRange
103081 gcc c++   ppalka [ICE] with "using enum"
107417 gcc c++   ppalka g++ fails to recognize 
parameter pack in requires-expression
107542 gcc c++   ppalka ICE in spaceship_comp_cat, 
at cp/method.cc:1055
108104 gcc c++   ppalka ICE in unify, at 
cp/pt.c:24333 with template partial specialization an
108362 gcc libstdc+ ppalkaviews::istream is 
SFINAE-unfriendly
103755 gcc libstdc+redi  {has,use}_facet() and 
iostream constructor performance
105678 gcc libstdc+redi  Undefined reference to 
stacktrace standard library
109165 gcc libstdc+redi  
std::hash>::operator() should be const
109182 gcc libstdc+redi  unused parameter pack is 
in expected(in_place_t)
109242 gcc libstdc+redi  C++2b 
std::optional::transform omits required std::remove_cv_t from
99417   gcc libstdc+unassigned  [C++17] std::variant assignment 
fails to compile
103325 gcc tree-opt unassigned 1 << -1 is never reduced to a 
constant during gimple
106714 gcc targetunassigned Incorrect casts in macros in 
amxtileintrin.h
107121 gcc tree-opt unassigned DEFERRED_INIT misspelled in 
error message
107206 gcc tree-opt unassigned Bogus -Wuninitialized in 
std::optional
107713 gcc targetunassigned Wrong implementation 
atomic_exchange on LoongArch
108097 gcc libstdc+unassigned std::stacktrace AddressSanitizer: 
new-delete-type-mismatch on 0
109000 gcc targetxry111LoongArch: "unmatched" -mabi 
and -mfpu setting can break ABI silent
104554 gcc fortran   anlauf ICE in 
check_assumed_size_reference, at fortran/resolv

The idea is to show that you've looked at what changed and though about it a 
bit even if it's
just bug review like I have above.


Html table below for those interested.


Also the release notes are not very helpful ( 
https://gcc.gnu.org/gcc-12/changes.html ):

GCC 12.3
Target Specific Changes
x86-64

  *   GCC now supports AMD CPUs based on the znver4 core via -march=znver4. The 
switch makes GCC consider using 512 bit vectors when auto-vectorizing.

This is the list of problem reports 
(PRs)
 from GCC's

[OE-core] [mickledore][PATCH] gcc : upgrade to v12.3

2023-06-23 Thread Sundeep KOKKONDA via lists.openembedded.org

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-cross-canadian_12.2.bb => gcc-cross-canadian_12.3.bb} | 0
 .../gcc/{gcc-cross_12.2.bb => gcc-cross_12.3.bb}| 0
 .../gcc/{gcc-crosssdk_12.2.bb => gcc-crosssdk_12.3.bb}  | 0
 .../gcc/{gcc-runtime_12.2.bb => gcc-runtime_12.3.bb}| 0
 .../gcc/{gcc-sanitizers_12.2.bb => gcc-sanitizers_12.3.bb}  | 0
 .../gcc/{gcc-source_12.2.bb => gcc-source_12.3.bb}  | 0
 meta/recipes-devtools/gcc/{gcc_12.2.bb => gcc_12.3.bb}  | 0
 .../gcc/{libgcc-initial_12.2.bb => libgcc-initial_12.3.bb}  | 0
 .../recipes-devtools/gcc/{libgcc_12.2.bb => libgcc_12.3.bb} | 0
 .../gcc/{libgfortran_12.2.bb => libgfortran_12.3.bb}| 0
 11 files changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-devtools/gcc/{gcc-12.2.inc => gcc-12.3.inc} (97%)
 rename meta/recipes-devtools/gcc/{gcc-cross-canadian_12.2.bb => 
gcc-cross-canadian_12.3.bb} (100%)
 rename meta/recipes-devtools/gcc/{gcc-cross_12.2.bb => gcc-cross_12.3.bb} 
(100%)
 rename meta/recipes-devtools/gcc/{gcc-crosssdk_12.2.bb => 
gcc-crosssdk_12.3.bb} (100%)
 rename meta/recipes-devtools/gcc/{gcc-runtime_12.2.bb => gcc-runtime_12.3.bb} 
(100%)
 rename meta/recipes-devtools/gcc/{gcc-sanitizers_12.2.bb => 
gcc-sanitizers_12.3.bb} (100%)
 rename meta/recipes-devtools/gcc/{gcc-source_12.2.bb => gcc-source_12.3.bb} 
(100%)
 rename meta/recipes-devtools/gcc/{gcc_12.2.bb => gcc_12.3.bb} (100%)
 rename meta/recipes-devtools/gcc/{libgcc-initial_12.2.bb => 
libgcc-initial_12.3.bb} (100%)
 rename meta/recipes-devtools/gcc/{libgcc_12.2.bb => libgcc_12.3.bb} (100%)
 rename meta/recipes-devtools/gcc/{libgfortran_12.2.bb => libgfortran_12.3.bb} 
(100%)

diff --git a/meta/recipes-devtools/gcc/gcc-12.2.inc 
b/meta/recipes-devtools/gcc/gcc-12.3.inc
similarity index 97%
rename from meta/recipes-devtools/gcc/gcc-12.2.inc
rename to meta/recipes-devtools/gcc/gcc-12.3.inc
index 0dbbecad4a..4ec03f925c 100644
--- a/meta/recipes-devtools/gcc/gcc-12.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-12.3.inc
@@ -2,11 +2,11 @@ require gcc-common.inc
 
 # Third digit in PV should be incremented after a minor release
 
-PV = "12.2.0"
+PV = "12.3.0"
 
 # BINV should be incremented to a revision after a minor gcc release
 
-BINV = "12.2.0"
+BINV = "12.3.0"
 
 FILESEXTRAPATHS =. "${FILE_DIRNAME}/gcc:${FILE_DIRNAME}/gcc/backport:"
 
@@ -64,7 +64,7 @@ SRC_URI = "${BASEURI} \
file://prefix-map-realpath.patch \
file://hardcoded-paths.patch \
 "
-SRC_URI[sha256sum] = 
"e549cf9cf3594a00e27b6589d4322d70e0720cdd213f39beb4181e06926230ff"
+SRC_URI[sha256sum] = 
"949a5d4f99e786421a93b532b22ffab5578de7321369975b91aec97adfda8c3b"
 
 S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/${SOURCEDIR}"
 B = "${WORKDIR}/gcc-${PV}/build.${HOST_SYS}.${TARGET_SYS}"
diff --git a/meta/recipes-devtools/gcc/gcc-cross-canadian_12.2.bb 
b/meta/recipes-devtools/gcc/gcc-cross-canadian_12.3.bb
similarity index 100%
rename from meta/recipes-devtools/gcc/gcc-cross-canadian_12.2.bb
rename to meta/recipes-devtools/gcc/gcc-cross-canadian_12.3.bb
diff --git a/meta/recipes-devtools/gcc/gcc-cross_12.2.bb 
b/meta/recipes-devtools/gcc/gcc-cross_12.3.bb
similarity index 100%
rename from meta/recipes-devtools/gcc/gcc-cross_12.2.bb
rename to meta/recipes-devtools/gcc/gcc-cross_12.3.bb
diff --git a/meta/recipes-devtools/gcc/gcc-crosssdk_12.2.bb 
b/meta/recipes-devtools/gcc/gcc-crosssdk_12.3.bb
similarity index 100%
rename from meta/recipes-devtools/gcc/gcc-crosssdk_12.2.bb
rename to meta/recipes-devtools/gcc/gcc-crosssdk_12.3.bb
diff --git a/meta/recipes-devtools/gcc/gcc-runtime_12.2.bb 
b/meta/recipes-devtools/gcc/gcc-runtime_12.3.bb
similarity index 100%
rename from meta/recipes-devtools/gcc/gcc-runtime_12.2.bb
rename to meta/recipes-devtools/gcc/gcc-runtime_12.3.bb
diff --git a/meta/recipes-devtools/gcc/gcc-sanitizers_12.2.bb 
b/meta/recipes-devtools/gcc/gcc-sanitizers_12.3.bb
similarity index 100%
rename from meta/recipes-devtools/gcc/gcc-sanitizers_12.2.bb
rename to meta/recipes-devtools/gcc/gcc-sanitizers_12.3.bb
diff --git a/meta/recipes-devtools/gcc/gcc-source_12.2.bb 
b/meta/recipes-devtools/gcc/gcc-source_12.3.bb
similarity index 100%
rename from meta/recipes-devtools/gcc/gcc-source_12.2.bb
rename to meta/recipes-devtools/gcc/gcc-source_12.3.bb
diff --git a/meta/recipes-devtools/gcc/gcc_12.2.bb 
b/meta/recipes-devtools/gcc/gcc_12.3.bb
similarity index 100%
rename from meta/recipes-devtools/gcc/gcc_12.2.bb
rename to meta/recipes-devtools/gcc/gcc_12.3.bb
diff --git a/meta/recipes-devtools/gcc/libgcc-initial_12.2.bb 
b/meta/recipes-devtools/gcc/libgcc-initial_12.3.bb
similarity index 100%
rename from meta/recipes-devtools/gcc/libgcc-initial_12.2.bb
rename to meta/recipes-devtools/gcc/libgcc-initial_12.3.bb
diff --git

Re: [OE-core] [PATCH v14] Rust Oe-Selftest implementation

2023-05-31 Thread Sundeep KOKKONDA via lists.openembedded.org

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 ; 
openembedded-core@lists.openembedded.org 

Cc: MacLeod, Randy ; Kallapa, Umesh 
; Gowda, Naveen ; 
Kokkonda, Sundeep ; Moodalappa, Shivaprasad 
; Shinde, Yash 
Subject: Re: [PATCH v14] Rust Oe-Selftest implementation

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 Tue, 2023-05-30 at 16:21 +0530, Yash Shinde wrote:
> The patch implements Rust testing framework similar to other selftest,
> specifically the gcc selftest in OE. It uses the client and server
> based method to test the binaries for cross-target on the image.
> The test framework is a wrapper around the Rust build system as ./x.py
> test. It tests many functionalities of Rust distribution like tools,
> documentation, libraries, packages, tools, Cargo, Crater etc.
> Please refer the following link for detailed description of Rust
> testing:-
> https://rustc-dev-guide.rust-lang.org/tests/intro.html#tool-tests
>
> To support the rust tests in oe-core, the following functions were
> added:-
> setup_cargo_environment(): Build bootstrap and some early stage tools.
> do_rust_setup_snapshot(): Install the snapshot version of rust binaries.
> do_configure(): To generate config.toml
> do_compile(): To build "remote-test-server" for qemu target image.
>
> Approximate Number of Tests Run in the Rust Testsuite :- 18000
> Approximate Number of Tests that FAIL in bitbake environment :- 100-150
> Normally majority of the testcases are present in major folder "test/"
> It contributes to more than 80% of the testcases present in Rust test
> framework. These tests pass as expected on any Rust versions without
> much fuss. The tests that fail are of less important and contribute to
> less than 2% of the total testcases. These minor tests are observed to
> work on some versions and fail on others. They have to be added, ignored
> or excluded for different versions as per the behavior.
> These tests have been ignored or excluded in the Rust selftest
> environment to generate success of completing the testsuite.
>
> These tests work in parallel mode even in the skipped test mode as
> expected. Although the patch to disable tests is large, it is very simple
> in that it only disables tests. When updating to a newer version of Rust,
> the patch can usually be ported in a day.
>
> Tested for X86, X86-64, ARM, ARM64 and MIPS64 on CentOS release 6.10
>
> Signed-off-by: pgowda 
> Signed-off-by: Vinay Kumar 
> Signed-off-by: Yash Shinde 
> ---
>  meta/lib/oeqa/selftest/cases/rust.py  |   86 +
>  .../rust/files/rust-oe-selftest.patch | 2120 +
>  meta/recipes-devtools/rust/rust-source.inc|1 +
>  meta/recipes-devtools/rust/rust_1.69.0.bb |7 +
>  4 files changed, 2214 insertions(+)
>  create mode 100644 meta/lib/oeqa/selftest/cases/rust.py
>  create mode 100644 meta/recipes-devtools/rust/files/rust-oe-selftest.patch

I did put this into a build for testing on the autobuilder. It hasn't
been running long and I can already see build failures such as:

https://autobuilder.yoctoproject.org/typhoon/#/builders/103/builds/6077
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/7200
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/7190
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2923
https://autobuilder.yoctoproject.org/typhoon/#/builders/37/builds/7200
https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/7217
https://autobuilder.yoctoproject.org/typhoon/#/builders/104/builds/6080
https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/7146
https://autobuilder.yoctoproject.org/typhoon/#/builders/61/builds/7184

and there will likely be more.

I'm finding this rather frustrating and am not sure how this was
tested.

Cheers,

Richard


oe-selftest-results.log
Description: oe-selftest-results.log

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#181995): 
https://lists.openembedded.org/g/openembedded-core/message/181995
Mute This Topic: https://lists.openembedded.org/mt/99216990/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] Cargo: build failure on 32-bit machine when DEBUG enabled

2023-05-29 Thread Sundeep KOKKONDA via lists.openembedded.org

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 messages sent to this group.
View/Reply Online (#181896): 
https://lists.openembedded.org/g/openembedded-core/message/181896
Mute This Topic: https://lists.openembedded.org/mt/99196585/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] rust reproducibility - QA warnings in Yocto

2023-05-25 Thread Sundeep KOKKONDA via lists.openembedded.org

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 with a lot of QA Warnings (attached in Warnings.txt).
Do you have any hint on why this difference in Yocto environment and any 
pointers to fix...



Thanks,
Sundeep K.



remap-path.patch
Description: remap-path.patch


rust-bb.patch
Description: rust-bb.patch
WARNING: rust-1.69.0-r0 do_package_qa: QA Issue: File 
/usr/lib/rustlib/x86_64-poky-linux-gnu/lib/.debug/libstd-f87b8130ceb76c8f.so in 
package rust-dbg contains reference to TMPDIR
File 
/usr/lib/rustlib/x86_64-poky-linux-gnu/lib/.debug/libtest-f170723db3df43ca.so 
in package rust-dbg contains reference to TMPDIR
File /usr/lib/.debug/librustc_macros-f86291dc1fbdaa54.so in package rust-dbg 
contains reference to TMPDIR
File /usr/lib/.debug/libstd-f87b8130ceb76c8f.so in package rust-dbg contains 
reference to TMPDIR
File /usr/lib/.debug/libderive_more-d77c907cca18b532.so in package rust-dbg 
contains reference to TMPDIR
File /usr/lib/.debug/libtest-f170723db3df43ca.so in package rust-dbg contains 
reference to TMPDIR
File /usr/lib/.debug/libserde_derive-ca5d504a7ae8f1e8.so in package rust-dbg 
contains reference to TMPDIR [buildpaths]
WARNING: rust-1.69.0-r0 do_package_qa: QA Issue: File /usr/bin/rustfmt in 
package rust-tools-rustfmt contains reference to TMPDIR [buildpaths]
WARNING: rust-1.69.0-r0 do_package_qa: QA Issue: File /usr/bin/cargo-clippy in 
package rust-tools-clippy contains reference to TMPDIR
File /usr/bin/clippy-driver in package rust-tools-clippy contains reference to 
TMPDIR [buildpaths]
WARNING: rust-1.69.0-r0 do_package_qa: QA Issue: File /usr/bin/cargo-fmt in 
package rust contains reference to TMPDIR
File /usr/bin/rustdoc in package rust contains reference to TMPDIR
File /usr/libexec/rust-analyzer-proc-macro-srv in package rust contains 
reference to TMPDIR
File /usr/lib/librustc_driver-8a0d5425d57fca06.so in package rust contains 
reference to TMPDIR
File /usr/lib/libzerofrom_derive-06e8c5ecfbb9c94a.so in package rust contains 
reference to TMPDIR
File /usr/lib/librustc_macros-f86291dc1fbdaa54.so in package rust contains 
reference to TMPDIR
File /usr/lib/libunic_langid_macros_impl-5b2237a479de72ae.so in package rust 
contains reference to TMPDIR
File /usr/lib/libicu_provider_macros-96bfc1f9dacc37e5.so in package rust 
contains reference to TMPDIR
File /usr/lib/libzerovec_derive-1d602abffb2f1b37.so in package rust contains 
reference to TMPDIR
File /usr/lib/libcstr-e792e95645fa0214.so in package rust contains reference to 
TMPDIR
File /usr/lib/libchalk_derive-88262002a513877f.so in package rust contains 
reference to TMPDIR
File /usr/lib/libstd-f87b8130ceb76c8f.so in package rust contains reference to 
TMPDIR
File /usr/lib/libdisplaydoc-0ea2e1d67387a6f4.so in package rust contains 
reference to TMPDIR
File /usr/lib/libthiserror_impl-f0c551f85c33aff1.so in package rust contains 
reference to TMPDIR
File /usr/lib/libproc_macro_hack-350a8692c28d971d.so in package rust contains 
reference to TMPDIR
File /usr/lib/libderive_more-d77c907cca18b532.so in package rust contains 
reference to TMPDIR
File /usr/lib/libtest-f170723db3df43ca.so in package rust contains reference to 
TMPDIR
File /usr/lib/libyoke_derive-748abcfe36901b00.so in package rust contains 
reference to TMPDIR
File /usr/lib/libserde_derive-ca5d504a7ae8f1e8.so in package rust contains 
reference to TMPDIR
File /usr/lib/libtracing_attributes-8dd673f56f0cb565.so in package rust 
contains reference to TMPDIR
File /usr/lib/rustlib/x86_64-poky-linux-gnu/lib/libcfg_if-0cc580b157fedf68.rlib 
in package rust contains reference to TMPDIR
File 
/usr/lib/rustlib/x86_64-poky-linux-gnu/lib/libprofiler_builtins-f58c3ad46ae05f6c.rlib
 in package rust contains reference to TMPDIR
File 
/usr/lib/rustlib/x86_64-poky-linux-gnu/lib/libcompiler_builtins-606ef814824aca7c.rlib
 in package rust contains reference to TMPDIR
File /usr/lib/rustlib/x86_64-poky-linux-gnu/lib/liblibc-e62c3055e362bc74.rlib 
in package rust contains reference to TMPDIR
File 
/usr/lib/rustlib/x86_64-poky-linux-gnu/lib/librustc_std_workspace_std-ef8c7b35b3f3512b.rlib
 in package rust contains reference to TMPDIR



  3419,199%

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#181721): 
https://lists.openembedded.org/g/openembedded-core/message/181721
Mute This Topic: https://lists.openembedded.org/mt/99133326/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe:

Re: [OE-core] [kirkstone][PATCH] cargo : non vulnerable cve-2022-46176 added to excluded list

2023-04-18 Thread Sundeep KOKKONDA via lists.openembedded.org

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 

Cc: rwmacl...@gmail.com ; umesh.kalap...@gmail.com 
; pgowda@gmail.com ; 
shiv...@gmail.com 
Subject: [OE-core] [kirkstone][PATCH] cargo : non vulnerable cve-2022-46176 
added to excluded list

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.

This cve (https://nvd.nist.gov/vuln/detail/CVE-2022-46176) is a security 
vulnirability when using cargo ssh.
Kirkstone doesn't support rust on-target images and the bitbake using the 
'wget' (which uses 'https') for fetching the sources instead of ssh.
So, cargo-native also not vulnerable 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 8b5f8d49b8..cb2d920441 100644
--- a/meta/conf/distro/include/cve-extra-exclusions.inc
+++ b/meta/conf/distro/include/cve-extra-exclusions.inc
@@ -15,6 +15,11 @@
 # the aim of sharing that work and ensuring we don't duplicate it.
 #

+#cargo https://nvd.nist.gov/vuln/detail/CVE-2022-46176
+#cargo security advisor 
https://blog.rust-lang.org/2023/01/10/cve-2022-46176.html
+#This CVE is a security issue when using cargo ssh. In kirkstone, rust 1.59.0 
is used and the rust on-target is not supported, so the target images are not 
vulnerable to the cve.
+#The bitbake using the 'wget' (which uses 'https') for fetching the sources 
instead of ssh. So, the cargo-native are also not vulnerable to this cve and so 
added to excluded list.
+CVE_CHECK_IGNORE += "CVE-2022-46176"

 # strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006
 # CVE is more than 20 years old with no resolution evident
--
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#180186): 
https://lists.openembedded.org/g/openembedded-core/message/180186
Mute This Topic: https://lists.openembedded.org/mt/98015597/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

62 matches

Mail list logo