similar to: [LLVMdev] Improving link time building llvm

On 6/16/07, David A. Greene <greened at obbligato.org> wrote: > Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the > linker that causes excessive link time when building llvm. We switched > to using cvs binutils and our link times went from minutes to seconds. > > I didn't see anything about this on the web pages. It might be good > information to

On Friday 15 June 2007 19:48, Aaron Gray wrote: > > Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the > > linker that causes excessive link time when building llvm. We switched > > to using cvs binutils and our link times went from minutes to seconds. > > Is there a binutils snapshot that can be used instead ? I would assume that any recent snapshot

> Just FYI, we discovered that GNU binutils 2.17 has a nasty bug in the > linker that causes excessive link time when building llvm. We switched > to using cvs binutils and our link times went from minutes to seconds. Is there a binutils snapshot that can be used instead ? Aaron

I recommend you don't parse version strings. In fact I switch the check to use AC_COMPILE precisely for the reason that gcc --version is totally unreliable and vendor specific. For example, what's the regular expression that tells you what the GCC version is: i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5470) (Aspen 5470.3) Per the rest of this thread, you can't

I am trying to build llvm-2.7 using non-system gcc/binutils. My gcc version is 4.1.2, and binutils is 2.17.50.0.15. I get the following errors `.L2438' referenced in section `.gnu.linkonce.r._ZNK4llvm16DAGTypeLegalizer13getTypeActionENS_3EVTE' of /build/toolchain/src/llvm-2.7/objdir/Release/lib/libLLVMSelectionDAG.a(LegalizeTypes.o): defined in discarded section

+llvm-dev Discussion here: https://sourceware.org/ml/gnu-gabi/2017-q2/msg00000.html On Tue, May 2, 2017 at 10:17 AM, Suprateeka R Hegde <hegdesmailbox at gmail.com> wrote: > On 02-May-2017 12:05 AM, Florian Weimer wrote: >> On 05/01/2017 08:28 PM, Suprateeka R Hegde wrote: >>> So the ratio shows ~96% is RELATIVE reloc. And only ~4% others. This is >>> not the

On Thu, May 13, 2010 at 12:28 PM, john blair <mailtome200420032002 at yahoo.com> wrote: > I am trying to build llvm-2.7 using non-system gcc/binutils. My gcc version is 4.1.2, and binutils is 2.17.50.0.15. I get the following errors That version of gcc is known to have issues building LLVM; see http://llvm.org/docs/GettingStarted.html#brokengcc . Try upgrading your gcc version. -Eli

Can someone provide instructions and the necessary environment/toolchain support needed to get Xen to build and boot on a native EFI system (i.e. with no CSM/legacy support)? Joe

Hi, I'm going to implement Mach-O support in llvm-objcopy. Before working on this, I'd like to hear your thoughts how llvm-objcopy should handle Mach-O section names. By convention, Mach-O section names are denoted by "<segment name>,<section name>". However, GNU objcopy renames them in the following rule [1]: - If the section name is well-known, rename it to an

I performed tests basing on first diff of https://reviews.llvm.org/D40352. (Creates .eh_frame for each .text.*, sets SHF_LINK_ORDER and .sh_link of created .eh_frame section to point to corresponding .text.) With use of GNU ld (GNU Binutils) 2.29.51.20171006 it reports errors when linking sample apps: ~/LLVM/Release/bin/clang++ test.cpp -ffunction-sections -o test.o /usr/local/bin/ld: .eh_frame

Hi ! During linking LLD and other linkers builds a static hash table for dynamic symbols, so that in runtime dynamic linker can use this table and find symbols faster. --hash-style=style linker option is used to select the hash type: "Set the type of linker's hash table(s). style can be either "sysv" for classic ELF ".hash" section, "gnu" for new style GNU

> On May 23, 2019, at 2:05 AM, James Henderson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I discussed this with Seiya off the mailing list yesterday, and this was the suggestion we came up with, on the basis that GNU objcopy has support for the renaming for GDB support, but it might be confusing to people who are new to the system, so we provide a more expected output

>> With GNU gold (GNU Binutils 2.29.51.20171006) 1.14 have an assert: >> ~/LLVM/Release/bin/clang++ test.cpp -ffunction-sections -o test.o >> /usr/local/bin/ld: internal error in layout_eh_frame_section, at >> .././../gold/object.cc:1309 >> It is that place: >> https://github.com/gittup/binutils/blob/gittup/gold/object.cc#L1372 >> Did not investigate it,

Thanks for the reply Eli. I have the same version of gcc/binutils as my system gcc/binutils And it gets built without any errors with them. --- On Thu, 5/13/10, Eli Friedman <eli.friedman at gmail.com> wrote: > From: Eli Friedman <eli.friedman at gmail.com> > Subject: Re: [LLVMdev] Building llvm using non-system gcc/binutils > To: "john blair"

> > Yes, it is a bug in ld. I have been working with H.J. and we have just tracked it down. > > > > > It seems that hjl helped, after all. > > Syslinux built, or better to write, linked with: > binutils 2.26.51.20160212 git 95c00d1 is salt-n-pepa. > > Both, ISOLINUX and EXTLINUX have passed the test on both, SeaBIOS and Bare-metal. > > Thanks hpa.

On Mon, Nov 16, 2020 at 10:42 PM Igor Kudrin <ikudrin at accesssoftek.com> wrote: > > On 14.11.2020 3:42, Fāng-ruì Sòng wrote: > > For .debug_* in object files: > > > > DWARF32 -> SHT_PROGBITS (unchanged) > > DWARF64 -> SHT_DWARF64 or SHT_GNU_DWARF64 > > > > In LLD, we will need to allow mixed SHT_PROGBITS and SHT_DWARF64. If > > all

Linux GABI [1] introduced new .note.gnu.property section which contains a program property note which describes special handling requirements for linker and run-time loader. LLD does not support .note.gnu.property yet. GABI specifies 2 types of entries: GNU_PROPERTY_STACK_SIZE and GNU_PROPERTY_NO_COPY_ON_PROTECTED: * GNU_PROPERTY_STACK_SIZE: Its pr_data field contains an integer in the format

Hi Eli, I tried to build llvm with gcc-4.4.3 and binutils-2.20.1. This time it failed with /build/toolchain/src/llvm-2.7/objdir/Release/bin/tblgen: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /build/toolchain/src/llvm-2.7/objdir/Release/bin/tblgen) make[1]: *** [/build/toolchain/src/llvm-2.7/objdir/lib/VMCore/Release/Intrinsics.gen.tmp] Error 1 make[1]: Leaving

Hello, We (the Portable Native Client team) would like to start upstreaming our LLVM modifications which contain support for Software Fault Isolation (SFI) as required for sandboxing programs to run under Native Client. Since the "total patch size" is quite big, we are splitting the effort to manageable chunks that can be committed, tested and reviewed separately as independently as

On 6/27/2010 10:35 PM, Rafael Espindola wrote: > Try to run just that ld command first. Same error message? Run in in > gdb and set a breakpoint just before gold tries to load the plugin. > Sorry, I am really out of ideas on what is going wrong here... It is the same error message . Can you tell me which gcc version are you using to compile the llvm chain, and also the binutils svn