[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/24326] `nm` outputs symbol values of 0 for ft LTO object f
From: |
brandon.m.simmons at gmail dot com |
Subject: |
[Bug binutils/24326] `nm` outputs symbol values of 0 for ft LTO object files |
Date: |
Wed, 13 Mar 2019 15:17:44 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=24326
--- Comment #2 from Brandon Simmons <brandon.m.simmons at gmail dot com> ---
Sorry I meant to post gcc version. I'm on debian stretch and these are the
versions available there
$ nm --version
GNU nm (GNU Binutils for Debian) 2.28
$ gcc --version
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
I also just noticed I get the same results (both files have roughly same size
and contents, at a glance, and nm works the same) on both fat/not-fat:
$ gcc -flto -ffat-lto-objects -c mytemp.c -o mytemp.o.ltofat
$ gcc -flto -fno-fat-lto-objects -c mytemp.c -o mytemp.o.lto_nonfat
I'm attaching both.
Glad to know this might be a thing that's fixed in newer versions. Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/24326] New: `nm` outputs symbol values of 0 for ft LTO object files, brandon.m.simmons at gmail dot com, 2019/03/12
- [Bug binutils/24326] `nm` outputs symbol values of 0 for ft LTO object files, nickc at redhat dot com, 2019/03/13
- [Bug binutils/24326] `nm` outputs symbol values of 0 for ft LTO object files,
brandon.m.simmons at gmail dot com <=
- [Bug binutils/24326] `nm` outputs symbol values of 0 for ft LTO object files, brandon.m.simmons at gmail dot com, 2019/03/13
- [Bug binutils/24326] `nm` outputs symbol values of 0 for ft LTO object files, brandon.m.simmons at gmail dot com, 2019/03/13
- [Bug binutils/24326] `nm` outputs symbol values of 0 for ft LTO object files, nickc at redhat dot com, 2019/03/13
- [Bug binutils/24326] `nm` outputs symbol values of 0 for ft LTO object files, brandon.m.simmons at gmail dot com, 2019/03/13