[Bug 1146646] New: LTO: crash build failure TW ppc64le
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1146646 Bug ID: 1146646 Summary: LTO: crash build failure TW ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening@forge.provo.novell.com Reporter: normand@linux.vnet.ibm.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 815020 --> http://bugzilla.opensuse.org/attachment.cgi?id=815020&action=edit crash_standard__ppc64le_201908211314.log LTO: crash build failure TW ppc64le as per https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/c... from which I retrieved the attached crash_standard__ppc64le_201908211314.log related extract lines: === [ 393s] rlprivate.h:433:24: warning: type of '_rl_iscxt' does not match original declaration [-Wlto-type-mismatch] [ 393s] isearch.c:60:17: note: '_rl_iscxt' was previously declared here [ 393s] isearch.c:60:17: note: code may be misoptimized unless '-fno-strict-aliasing' is used [ 393s] rlprivate.h:466:24: warning: type of '_rl_nscxt' does not match original declaration [-Wlto-type-mismatch] [ 393s] search.c:55:17: note: '_rl_nscxt' was previously declared here [ 393s] search.c:55:17: note: code may be misoptimized unless '-fno-strict-aliasing' is used [ 393s] /tmp/ccbEePMn.s: Assembler messages: [ 393s] /tmp/ccbEePMn.s:1931: Error: can't resolve `.toc1' {.toc1 section} - `.LCTOC1' {*UND* section} [ 393s] /tmp/ccbEePMn.s:1935: Error: can't resolve `.toc1' {.toc1 section} - `.LCTOC1' {*UND* section} === There is no such failure if LTO disabled -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1146646
Michel Normand
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1146646
http://bugzilla.opensuse.org/show_bug.cgi?id=1146646#c10
Michel Normand
It's caused by a fact that part of the objects are built with -mminimal-toc
I did not found from where -mminimal-toc is coming from. But I successfully build package with lto adding -mfull-toc for ppc64le in my branch https://build.opensuse.org/package/show/home:michel_mno:branches:Kernel:kdum... as per attached crash_ppc64le_with_lto_and_mfull_toc_build_ok.log I do not know if a valid solution (did not try to test) -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1146646
http://bugzilla.opensuse.org/show_bug.cgi?id=1146646#c11
--- Comment #11 from Martin Liška
Created attachment 837494 [details] crash_ppc64le_with_lto_and_mfull_toc_build_ok.log
(In reply to Martin Liška from comment #9)
It's caused by a fact that part of the objects are built with -mminimal-toc
I did not found from where -mminimal-toc is coming from.
I tried to grep sources, but also didn't find it.
But I successfully build package with lto adding -mfull-toc for ppc64le in my branch https://build.opensuse.org/package/show/home:michel_mno:branches:Kernel: kdump/crash as per attached crash_ppc64le_with_lto_and_mfull_toc_build_ok.log
Please push it to devel project.
I do not know if a valid solution (did not try to test)
-- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com