[Bug backends/25832] New: aarch64 fails to compile with musl

: backends Assignee: unassigned at sourceware dot org Reporter: luizluca at gmail dot com CC: elfutils-devel at sourceware dot org Target Milestone: --- Hello gibc has user_fpsimd_struct.vregs as __uint128_t https://github.com/bminor/glibc/blob/master/sysdeps

[Bug libdw/23301] New: free on unitialized value

Assignee: unassigned at sourceware dot org Reporter: luizluca at gmail dot com CC: elfutils-devel at sourceware dot org Target Milestone: --- Created attachment 11075 --> https://sourceware.org/bugzilla/attachment.cgi?id=11075&action=edi

[Bug general/21002] Incompatible with MUSL libc

https://sourceware.org/bugzilla/show_bug.cgi?id=21002 --- Comment #7 from Luiz Angelo Daros de Luca --- I'm back with news. I manage to compile all elfutils for OpenWrt, not just libs. As expected, obstack and fts were missing. I managed to build using: https://github.com/pullmoll/musl-obstack

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #17 from Luiz Angelo Daros de Luca --- > Or your alternative glibc headers don't provide enough information about > assert to the compiler? musl dropped the attribute noreturn, which got reverted sometime after. http://www.openwa

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #14 from Luiz Angelo Daros de Luca --- I do not set -DNDEBUG. All compiler flags are similar in this case. Maybe a gcc bug? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #12 from Luiz Angelo Daros de Luca --- Great! Thanks! How about libcpu/i386_disasm.c case? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #9 from Luiz Angelo Daros de Luca --- ./configure is called as: AR="i486-openwrt-linux-musl-gcc-ar" AS="i486-openwrt-linux-musl-gcc -c -Os -pipe -march=pentium4 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

https://sourceware.org/bugzilla/show_bug.cgi?id=21011 Luiz Angelo Daros de Luca changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resol

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #6 from Luiz Angelo Daros de Luca --- Mark, I know that both might be a compiler bug. However, the cost of solving them are very low. Yes, I might be compiling elfutils with non-standard options. However, the non-standard might b

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #5 from Luiz Angelo Daros de Luca --- Mark, I know that both might be a compiler bug. However, the cost of solving them are very low. Yes, I might be compiling elfutils with non-standard options. However, the non-standard might b

[Bug general/21002] Incompatible with MUSL libc

https://sourceware.org/bugzilla/show_bug.cgi?id=21002 --- Comment #5 from Luiz Angelo Daros de Luca --- It is not part of my use case but besides the problems already mentioned, elfutils/src will still miss from glibc: - obstack - fts (I already use a patch to remove its dependency on lib*) The

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #1 from Luiz Angelo Daros de Luca --- Another case: i386_disasm.c: In function 'i386_disasm': /home/luizluca/prog-local/lede/trunk/staging_dir/toolchain-mipsel_24kc_gcc-5.4.0_musl-1.1.15/include/fortify/string.h:47:24: error: 'str

[Bug general/21011] New: "may be used uninitialized" error with -Werror=maybe-uninitialized

NCONFIRMED Severity: normal Priority: P2 Component: general Assignee: unassigned at sourceware dot org Reporter: luizluca at gmail dot com CC: elfutils-devel at sourceware dot org Target Milestone: --- Hello, I get this error when compiling with -We

[Bug general/21010] Incompatible with MUSL libc: strerror_r

https://sourceware.org/bugzilla/show_bug.cgi?id=21010 Luiz Angelo Daros de Luca changed: What|Removed |Added Blocks||21002 Referenced Bugs:

[Bug general/21002] Incompatible with MUSL libc

https://sourceware.org/bugzilla/show_bug.cgi?id=21002 Luiz Angelo Daros de Luca changed: What|Removed |Added Depends on||21008, 21009, 21010 --- C

[Bug general/21008] Incompatible with MUSL libc: error.h and error() not provided

https://sourceware.org/bugzilla/show_bug.cgi?id=21008 Luiz Angelo Daros de Luca changed: What|Removed |Added Blocks||21002 Referenced Bugs:

[Bug general/21009] Incompatible with MUSL libc: canonicalize_file_name

https://sourceware.org/bugzilla/show_bug.cgi?id=21009 Luiz Angelo Daros de Luca changed: What|Removed |Added Blocks||21002 Referenced Bugs:

[Bug general/21008] Incompatible with MUSL libc: error.h and error() not provided

https://sourceware.org/bugzilla/show_bug.cgi?id=21008 --- Comment #1 from Luiz Angelo Daros de Luca --- BTW, simply moving the include into system.h will dramatically reduce the number of files I need to patch in order to compile with MUSL. -- You are receiving this mail because: You are on the

[Bug general/21010] New: Incompatible with MUSL libc: strerror_r

Component: general Assignee: unassigned at sourceware dot org Reporter: luizluca at gmail dot com CC: elfutils-devel at sourceware dot org Target Milestone: --- >From original bug 21002 - I have to think about that strerror_r replacement. Normally we expect jus