[Bug ld/30938] New: [RISCV]linking erro with lp64f
https://sourceware.org/bugzilla/show_bug.cgi?id=30938
Bug ID: 30938
Summary: [RISCV]linking erro with lp64f
Product: binutils
Version: 2.39
Status: NEW
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: akhilesh.k at samsung dot com
Target Milestone: ---
I am getting "can't link single-float modules with double-float modules"
linking error, while compiling below code with lp64f.
as per risc-v spec only difference is, for lp64f ABI_FLEN=32 and for lp64d
ABI_FLEN=64.
user@starfive:/tmp$ cat float.c
int main() {
float x = 1.0;
return 1;
}
user@starfive:/tmp$ gcc -g -O -c float.c -mabi=lp64d
user@starfive:/tmp$ gcc -g -O -c float.c -mabi=lp64f
user@starfive:/tmp$ gcc float.c -mabi=lp64d
user@starfive:/tmp$ gcc float.c -mabi=lp64f
/usr/bin/ld: /tmp/ccbnQISS.o: can't link single-float modules with double-float
modules
/usr/bin/ld: failed to merge target specific data of file /tmp/ccbnQISS.o
collect2: error: ld returned 1 exit status
user@starfive:/tmp$
user@starfive:/tmp$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/riscv64-linux-gnu/12/lto-wrapper
Target: riscv64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 12.2.0-10'
--with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-12
--program-prefix=riscv64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --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
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch
--disable-werror --disable-multilib --with-arch=rv64gc --with-abi=lp64d
--enable-checking=release --build=riscv64-linux-gnu --host=riscv64-linux-gnu
--target=riscv64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Debian 12.2.0-10)
user@starfive:/tmp$
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug ld/30938] [RISCV]linking erro with lp64f
https://sourceware.org/bugzilla/show_bug.cgi?id=30938 Akhilesh Kumar changed: What|Removed |Added Target||RISC-V CC||akhilesh.k at samsung dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30938] [RISCV]linking erro with lp64f
https://sourceware.org/bugzilla/show_bug.cgi?id=30938 --- Comment #1 from Andreas Schwab --- Since the compiler is configured with -disable-multilib you are lacking the complete set of single-float crt*.o objects and libraries. Only -mabi=lp64d is supported with this compiler. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30578] libavcodec/x86/mathops.h:125: Error: operand type mismatch for ` shr'
https://sourceware.org/bugzilla/show_bug.cgi?id=30578 Jan Engelhardt changed: What|Removed |Added CC||jengelh at inai dot de -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/30376] windres cannot parse rc files which it itself generated
https://sourceware.org/bugzilla/show_bug.cgi?id=30376
--- Comment #10 from Nick Clifton ---
(In reply to Pali Rohár from comment #7)
> "resource_name4" "resource_type4" { "resource_string_data4" }
> i686-w64-mingw32-windres: test-resource.rc:4: syntax error
Right - this is the same issue as described in comment #3. The parser thinks
that you are concatenating two double-quoted-strings together to make a single
resource name that includes a space in the middle. Since spaces are not
allowed in resource names it signals a syntax error.
> Binary resource test-resource.ms.res compiled by MS compiler I can put into
> resource-only DLL via MS linker and then list its content via wrestool:
> --type='"RESOURCE_TYPE4"' --name='"RESOURCE_TYPE4"' --language=1033
> And now if I decompile resource.ms.res via GNU windres I get following
> output:
>
> $ i686-w64-mingw32-windres test-resource.ms.res
>
> /* Type: """RESOURCE_TYPE4"""
>
>Name: """RESOURCE_NAME4""". */
>
> """RESOURCE_NAME4""" """RESOURCE_TYPE4""" MOVEABLE PURE
> BEGIN
> 0x6f736572L, 0x65637275L, 0x7274735fL, 0x5f676e69L, 0x61746164L,
> "4"
> END
> It is clear that it is not what was on the input as resource name and types
> have messed quote character.
I think that the triple quotes are an attempt to encode a single quote without
it having any kind of special meaning. But in practice this does not work.
I think the point that you are trying to make however is that the MS resource
compiler actually includes the double quote characters as part of the resource
names, correct ?
I will have a look into this now.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug binutils/30376] windres cannot parse rc files which it itself generated
https://sourceware.org/bugzilla/show_bug.cgi?id=30376 --- Comment #11 from Pali Rohár --- (In reply to Nick Clifton from comment #10) > I think the point that you are trying to make however is that the MS > resource compiler actually includes the double quote characters as part of > the resource names, correct ? Yes, above test proves that. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30930] ld-2.41 links mame in a way which gets stuck on aarch64
https://sourceware.org/bugzilla/show_bug.cgi?id=30930 --- Comment #18 from Szabolcs Nagy --- i tried the specified steps and the bug is not reproducible. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30930] ld-2.41 links mame in a way which gets stuck on aarch64
https://sourceware.org/bugzilla/show_bug.cgi?id=30930 --- Comment #19 from Nick Clifton --- (In reply to Szabolcs Nagy from comment #18) > i tried the specified steps and the bug is not reproducible. Oh dear - that implies that the problem might be specific the Fedora binutils. Thanks for having a look at the problem. I guess it is up to the Fedora folks now. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30930] ld-2.41 links mame in a way which gets stuck on aarch64
https://sourceware.org/bugzilla/show_bug.cgi?id=30930 --- Comment #20 from Szabolcs Nagy --- (In reply to Szabolcs Nagy from comment #18) > i tried the specified steps and the bug is not reproducible. (In reply to Nick Clifton from comment #19) > (In reply to Szabolcs Nagy from comment #18) > > i tried the specified steps and the bug is not reproducible. > > Oh dear - that implies that the problem might be specific the Fedora > binutils. > > Thanks for having a look at the problem. I guess it is up to the Fedora > folks now. seems they made the build use lld, so now i have to undo that. will look at it tomorrow -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30930] ld-2.41 links mame in a way which gets stuck on aarch64
https://sourceware.org/bugzilla/show_bug.cgi?id=30930 --- Comment #21 from Julian Sikorski --- (In reply to Szabolcs Nagy from comment #20) > seems they made the build use lld, so now i have to undo that. > will look at it tomorrow Sorry about that, I should have mentioned it here. You do not need to do git revert. You can do $ fedpkg switch-branch f39 $ fedpkg srpm $ mock -r fedora-rawhide-aarch64 mame-0.259-1.fc39.src.rpm -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30910] gprofng cross test fail: can't read "CHECK_TARGET": no such variable
https://sourceware.org/bugzilla/show_bug.cgi?id=30910 Vladimir Mezentsev changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Vladimir Mezentsev --- I cannot reproduce this on our machines. Is the sources from https://sourceware.org/git/binutils-gdb.git or from binutils-2.41.tar ? What is an output of "uname -a" ? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30910] gprofng cross test fail: can't read "CHECK_TARGET": no such variable
https://sourceware.org/bugzilla/show_bug.cgi?id=30910 --- Comment #2 from YunQiang Su --- I use git master, aka https://sourceware.org/git/binutils-gdb.git. > name -a Linux vm-1 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-1 (2023-07-14) x86_64 GNU/Linux The operating system is Debian. In fact I also tried to build x86-64 target on arm64 platform. It has the same problem: > uname -a Linux Faphine 5.14.0-0.bpo.2-arm64 #1 SMP Debian 5.14.9-2~bpo11+1 (2021-10-10) aarch64 GNU/Linux > mkdir build > cd build > ../configure --target=x86_64-linux-gnu > make > make check -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30940] New: alpha: ld segfaults in
https://sourceware.org/bugzilla/show_bug.cgi?id=30940
Bug ID: 30940
Summary: alpha: ld segfaults in
Product: binutils
Version: 2.42 (HEAD)
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: mcree at orcon dot net.nz
Target Milestone: ---
ld running on Alpha has been noted to be segfaulting on certain builds in the
debian-ports archive. Backtrace of a coredump with latest build gives:
#0 0x00012005fa08 in elf64_alpha_check_relocs (abfd=0x1202b51a0,
info=0x1201d4e18 ,
sec=, relocs=) at
../../binutils-gdb.git/bfd/elf64-alpha.c:1984
#1 0x000120090e84 in _bfd_elf_link_iterate_on_relocs (abfd=0x1202b51a0,
info=0x1201d4e18 ,
action=0x12005f7d0 ) at
../../binutils-gdb.git/bfd/elflink.c:4179
#2 0x00012004da0c in bfd_link_check_relocs (abfd=0x2242b00,
info=0x120166f48)
at ../../binutils-gdb.git/bfd/linker.c:3361
#3 0x00012001fa60 in lang_check_relocs () at
../../binutils-gdb.git/ld/ldlang.c:8031
#4 lang_process () at ../../binutils-gdb.git/ld/ldlang.c:8318
#5 0x000120003264 in main (argc=, argv=) at
../../binutils-gdb.git/ld/ldmain.c:501
(gdb) list
1979 loaded into memory, we need a RELATIVE reloc. */
1980 sreloc->size += sizeof (Elf64_External_Rela);
1981 if (sec->flags & SEC_READONLY)
1982{
1983 info->flags |= DF_TEXTREL;
1984 info->callbacks->minfo
1985(_("%pB: dynamic relocation against `%pT' in "
1986 "read-only section `%pA'\n"),
1987 sec->owner, h->root.root.root.string, sec);
1988}
Noted binutils working at version 2.34 but fails at 2.35 so bisected getting
first bad commit as:
1f7f2abbc31ee9e6d4faca58bef14d8ee8cb1bd2
alpha: Warn DT_TEXTREL with -M
--
You are receiving this mail because:
You are on the CC list for the bug.
