[Bug binutils/32256] [Bug] internal labels present in risc-v
https://sourceware.org/bugzilla/show_bug.cgi?id=32256 --- Comment #3 from Andreas Schwab --- They are if there are relocations. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug admin/32252] ./configure produces invalid Makefile
https://sourceware.org/bugzilla/show_bug.cgi?id=32252 --- Comment #4 from Alan Modra --- Hmm, OK, so the lack of Makefile substitutions is due to your config.status line 732: cat >>"/subs1.awk" <<\_ACAWK && Note that a later line has: cat >>"$ac_tmp/subs1.awk" <<\_ACAWK && $ac_tmp/subs1.awk is the correct file. You'll need to figure out why you are missing the $ac_tmp on line 732. It may be a shell quoting bug. Looks like this comes from configure:19730, a few lines below # Create commands to substitute file output variables. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/32256] [Bug] internal labels present in risc-v
https://sourceware.org/bugzilla/show_bug.cgi?id=32256 --- Comment #2 from Akhilesh Kumar --- why these are not visible in arm objdumps but visible for riscv is there any way to suppress it with-out strip ? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/32256] [Bug] internal labels present in risc-v
https://sourceware.org/bugzilla/show_bug.cgi?id=32256 Akhilesh Kumar changed: What|Removed |Added CC||akhilesh.k at samsung dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug admin/32252] ./configure produces invalid Makefile
https://sourceware.org/bugzilla/show_bug.cgi?id=32252 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Alan Modra --- So AC_SUBST_FILE didn't work for you. Check you autoconf version -- You are receiving this mail because: You are on the CC list for the bug.
[Bug admin/32252] ./configure produces invalid Makefile
https://sourceware.org/bugzilla/show_bug.cgi?id=32252 --- Comment #3 from dilyan.palauzov at aegee dot org --- I need autoconf if I generate configure from configure.ac. But I do not generate configure , it comes from git : https://sourceware.org/git/?p=binutils-gdb.git;a=tree . I have autoconf 2.69 and https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=configure.ac does not contain AC_RPEREQ to enforce a particular autoconf version. git grep AC_PREREQ does not mention anything newer than 2.65. So outdated autoconf version cannot be the reason. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/32243] NAME_MAX does not exist on mingw-w64 without the define of _POSIX_ macro
https://sourceware.org/bugzilla/show_bug.cgi?id=32243 oset changed: What|Removed |Added CC||oset at superbox dot pl --- Comment #4 from oset --- NAME_MAX seem to 255 in VC. VC9 ~~~ $ grep -r -nH NAME_MAX * limits.h:117:#define NAME_MAX255 stdio.h:111:#define FILENAME_MAX260 ~~~ VC6 ~~~ $ grep -r -nH NAME_MAX * CRT/SRC/STDIO.H:216:#define FILENAME_MAX260 (...) Include/LIMITS.H:107:#define NAME_MAX255 Include/STDIO.H:200:#define FILENAME_MAX260 ~~~ Same as in Linux: ~~~ $ grep -r -nH -w NAME_MAX * linux/limits.h:11:#define NAME_MAX 255 /* # chars in a file name */ ~~~ Same in MinGW ~~~ $ grep -r -nH -w NAME_MAX * limits.h:108:#define NAME_MAX 255 ~~~ I can't say for newer ones but it can be assumed that if it was N for X years prior, it will be after. That is not something you change on a whim. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/32243] NAME_MAX does not exist on mingw-w64 without the define of _POSIX_ macro
https://sourceware.org/bugzilla/show_bug.cgi?id=32243 --- Comment #6 from oset --- The patch (https://sourceware.org/bugzilla/attachment.cgi?id=15732&action=diff @ https://sourceware.org/bugzilla/show_bug.cgi?id=32243#c1) uses 256. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/32243] NAME_MAX does not exist on mingw-w64 without the define of _POSIX_ macro
https://sourceware.org/bugzilla/show_bug.cgi?id=32243 --- Comment #5 from Alan Modra --- Yes, 255 is the value I used in the patch that was applied. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/32256] New: [Bug] internal labels present in risc-v
https://sourceware.org/bugzilla/show_bug.cgi?id=32256 Bug ID: 32256 Summary: [Bug] internal labels present in risc-v Product: binutils Version: 2.42 Status: NEW Severity: enhancement Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: akhilesh.k at samsung dot com Target Milestone: --- Hi All `.LFB`, `.LVL`, `.LBB`, and `.LBE` are internal labels is expected in compiler generated asm file since these are internal labels i was expecting not be present in objdump. using open source risc-v toolchain observed internal labels are visible in objdump. Is this related with architecture, compiler settings ? because same settings i using for arm and riscv for arm these are not visible but riscv these visible logs akhilesh.k@B0110LHG:~/Activity/L_sections/module$ riscv64-linux-gnu-objdump -d /home/akhilesh.k/Activity/L_sections/module/spinlock_sleep.ko | grep ".L" /home/akhilesh.k/Activity/L_sections/module/spinlock_sleep.ko: file format elf64-littleriscv 0018 <.LVL0>: 0018 <.LBB13>: 24: 80e7jalrra # 20 <.LBB13+0x8> 0028 <.LBE13>: 2a: bb850513addia0,a0,-1096 # bb8 <.LASF527+0x3> 32: 80e7jalrra # 2e <.LBE13+0x6> 0036 <.LBB15>: 42: 80e7jalrra # 3e <.LBB15+0x8> 0046 <.LBE15>: akhilesh.k@B0110LHG:~/Activity/L_sections/module$ akhilesh.k@B0110LHG:$ riscv64-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=riscv64-linux-gnu-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc-cross/riscv64-linux-gnu/11/lto-wrapper Target: riscv64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.4.0-1ubuntu1~22.04' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm --disable-libquadmath --disable-libquadmath-support --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --without-target-system-zlib --enable-multiarch --disable-werror --disable-multilib --with-arch=rv64gc --with-abi=lp64d --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=riscv64-linux-gnu --program-prefix=riscv64-linux-gnu- --includedir=/usr/riscv64-linux-gnu/include --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/32256] [Bug] internal labels present in risc-v
https://sourceware.org/bugzilla/show_bug.cgi?id=32256 Akhilesh Kumar changed: What|Removed |Added CC||akhipatel at gmail dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/32256] [Bug] internal labels present in risc-v
https://sourceware.org/bugzilla/show_bug.cgi?id=32256 --- Comment #1 from Andreas Schwab --- They are referenced by relocations. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/32110] gprofng segfaults on parsing DWARF of clang++ 18.1.3 produced binary
https://sourceware.org/bugzilla/show_bug.cgi?id=32110 --- Comment #9 from Vladimir Mezentsev --- This is an error when gprofng reads Dwarf-5. The easiest test to reproduce the problem: % gprofng display src -func graal/sdk/mxbuild/linux-amd64/PYTHON_JAVA_STANDALONE_SVM_JAVA24/graalpy-community-24.2.0-dev-linux-amd64/jvmlibs/libtrufflenfi.so Segmentation fault (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.
