search for: no_compact_unwind

I thought of another work around. The FSF gcc driver can implicitly add -no_compact_unwind to the link line. This tells the linker to not produce compact unwind information from the dwarf unwind info in .o files. Then at runtime the darwin unwinder will fallback and use the slow dwarf unwind info. -Nick On Sep 18, 2009, at 2:27 PM, Nick Kledzik wrote: > I dug into this. Bas...

On Fri, Sep 18, 2009 at 02:40:17PM -0700, Nick Kledzik wrote: > I thought of another work around. The FSF gcc driver can implicitly > add -no_compact_unwind to the link line. This tells the linker to not > produce compact unwind information from the dwarf unwind info in .o > files. Then at runtime the darwin unwinder will fallback and use the > slow dwarf unwind info. > > -Nick > Nick, I can confirm that passing "-W...

..._mismatches non-weak -undefined suppress -o libvmd.dylib -ldylib1.10.5.o -L/sw/lib/gcc4.6/lib/gcc/x86_64-apple-darwin11.0.0/4.6.1 -L/sw/lib/gcc4.6/lib/gcc/x86_64-apple-darwin11.0.0/4.6.1/../../.. dpApi.o vmd.o vmdInter.o tclStream.o dpStream.o ssStream.o publicVMDInter.o thread.o -lcrypto -lstdc++ -no_compact_unwind -lSystem -lgcc_ext.10.5 -lgcc -lSystem /sw/lib/gcc4.6/lib/gcc/x86_64-apple-darwin11.0.0/4.6.1/crtfastmath.o -v [MacPro:~/xplor-nih-2.27/vmd/bin.Darwin_11_x86_64] howarth% gdb /usr/bin/ld GNU gdb 6.3.50-20050815 (Apple version gdb-1705) (Fri Jul 1 10:50:06 UTC 2011) Copyright 2004 Free Software Fo...

...inker issues with larger programs like aermod... as -arch x86_64 -force_cpusubtype_ALL -o aermod.o aermod.s /usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.6.3 -weak_reference_mismatches non-weak -o aermod -lcrt1.10.5.o -L./ aermod.o -lgfortran -lgcc_s.10.5 -lgcc_ext.10.5 -no_compact_unwind -lSystem -v @(#)PROGRAM:ld PROJECT:ld64-97.2 Library search paths: ./ /usr/lib /usr/local/lib Framework search paths: /Library/Frameworks/ /System/Library/Frameworks/ ld: in aermod.o, in section __TEXT,__text reloc 17: local relocation for address 0x000FB35C in section __text does not target...

...rger programs like > aermod... > > as -arch x86_64 -force_cpusubtype_ALL -o aermod.o aermod.s > /usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.6.3 -weak_reference_mismatches non-weak -o aermod -lcrt1.10.5.o -L./ aermod.o -lgfortran -lgcc_s.10.5 -lgcc_ext.10.5 -no_compact_unwind -lSystem -v > @(#)PROGRAM:ld PROJECT:ld64-97.2 > Library search paths: > ./ > /usr/lib > /usr/local/lib > Framework search paths: > /Library/Frameworks/ > /System/Library/Frameworks/ > ld: in aermod.o, in section __TEXT,__text reloc 17: local relocation for address...

...gt; > aermod... > > > > as -arch x86_64 -force_cpusubtype_ALL -o aermod.o aermod.s > > /usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.6.3 -weak_reference_mismatches non-weak -o aermod -lcrt1.10.5.o -L./ aermod.o -lgfortran -lgcc_s.10.5 -lgcc_ext.10.5 -no_compact_unwind -lSystem -v > > @(#)PROGRAM:ld PROJECT:ld64-97.2 > > Library search paths: > > ./ > > /usr/lib > > /usr/local/lib > > Framework search paths: > > /Library/Frameworks/ > > /System/Library/Frameworks/ > > ld: in aermod.o, in section __TEXT,_...

...gt; important side effect. We will always be able to test everything > through -core and dump how to run it with -###. LLVM and Clang both > handle options like this, and it seems to scale fine. We can still test any option (for example a darwin specific option) like: lld -flavor darwin -no_compact_unwind ... Clang is different than ld is that it currently (from my understand) just supports the gcc command line options. It does not support completely different command line languages like binutils's ld and darwin's ld have. The darwin linker has ~100 command line options. For most of th...

I dug into this. Based on the .s files in bugzilla, the latest gcc is now adding dwarf unwind info to describe the function epilog. If you run dwarfdump --eh-frame on the .o files made with the new compiler, you'll see extra dwarf unwind instructions at the end like: ... DW_CFA_advance_loc4 (64) #<-- advance to near end of function

On Wed, Jan 23, 2013 at 6:57 PM, Nick Kledzik <kledzik at apple.com> wrote: > Michael, > > I'm looking at flushing out the mach-o driver and targetinfo. > > Can we rename the "ld64" flavor to "darwin". The command line tool on MacOSX is called "ld" - just like on unix. The name ld64 is the current source repository name for the linker. Once

On Fri, Sep 18, 2009 at 11:13:52AM -0700, Nick Kledzik wrote: > > The important thing is that only one unwinder is used. The > _Unwind_Context data structure is different between the darwin and FSF > implementations, so you can't pass it between two different > implementations. Since darwin uses two-level namespace and swapping in > a new libgcc_s.dylib at runtime

Michael, I'm looking at flushing out the mach-o driver and targetinfo. Can we rename the "ld64" flavor to "darwin". The command line tool on MacOSX is called "ld" - just like on unix. The name ld64 is the current source repository name for the linker. Once lld takes over, the term ld64 won't mean anything. I've worked through adding DarwinOpts.td

...esults for libiomp5 are very close to matching those for the FSF gcc compiler with libgomp in terms of the number of passed tests while libiomp5 already exceeds libgomp for the number of verified tests. when using "-fopenmp=libgomp -Xclang -fopenmp=libgomp -L/sw/lib/gcc5/lib > -lm -O3 -Wl,-no_compact_unwind". So we can't get much more broken that the > current behavior with libgomp. > Jack > > On Thu, Apr 30, 2015 at 9:49 AM, Andrey Bokhanko <andreybokhanko at gmail.com > > wrote: > >> All, >> >> I'd like to resurrect the discussion on...

All, I'd like to resurrect the discussion on replacing libgomp with libiomp as the default OpenMP runtime library linked with -fopenmp. For reference, the previous discussion is accessible there: http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20140217/thread.html#99461 We are very close to getting *full* OpenMP 3.1 specification supported in clang (only one (!) clause is not