search for: devforum

...rned up no results (please correct me > here). > > How can one set a permanent breakpoint on malloc_error_break under LLVM? Take a look at http://lldb.llvm.org/ for LLDB documentation. If you have further questions, this isn't really the best place to ask; the Xcode section of http://devforums.apple.com/ is generally best for Xcode questions; you can also try the lldb-dev mailing list for questions about lldb. -Eli

Hi All, Please forgive me if this is the wrong group. I did not see a llvm-user group (). The User Guide also lacked a topic (http://llvm.org/docs/userguides.html#userguides). I am an Xcode user. I want to set a breakpoint on malloc_error_break all the time (it makes no sense to re-run after setting the breakpoint on occasion). I want the breakpoint whenever the debugger starts, and for all

Moshe, You're more than likely going to get a better response from https://devforums.apple.com/community/tools/xcode llvmdev is a mailing list for the LLVM project which is separate from Xcode development. Cheers, Joe On Jun 12, 2013, at 8:51 AM, Moshe Kravchik <mkravchik at hotmail.com<mailto:mkravchik at hotmail.com>> wrote: Hi, I've got an assembly file wh...

...on failed: (memberIndex != 0), function makeObjectFileForMember, file /SourceCache/ld64/ld64-136/src/ld/parsers/archive_file.cpp, line 354. This looks like a bug in the Apple linker, which isn't part of LLVM. The best on-topic place to ask would probably be Apple's developer forum (https://devforums.apple.com), but linkers are rather specialised beasts. The fact that it's been fixed in XCode 5 probably means filing a bug won't be that useful for you. Having said that, the ld64 sources are available online, so if you really need an XCode 4 solution you could try to track it down yours...

Hi, I've got an assembly file which used to compile with previous clang versions. However with 4.2 I get the following error: admin$ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch armv7 ./src/asm.s -o asm.o ./src/asm.s:30:5: error: instruction requires a CPU feature not currently enabled add r2, pc, r2 According to ARM

Hi, I'm encountering the following assertion when linking an Xcode project with Xcode 4.6.3 (4H1503). The project has dependencies on, and links against, an Objective-C static library Xcode project, and a C++ static library Xcode project. All are using using LLVM 4.2. ld: Assertion failed: (memberIndex != 0), function makeObjectFileForMember, file

Hey All; Meet the following link error using LLVM 2.0 based on XCode 4.0.1, I don't know what does it mean and how to fix it? please help, thanks. ld: bad codegen, pointer diff in ___cxx_global_var_init79 to global weak symbol __ZN5boost16exception_detail23exception_ptr_bad_allocILi42EE1eE for architecture armv7 clang: error: linker command failed with exit code 1 (use -v to see

...t least I've seen some llc invocations and some amdil backend. I don't know if it compiles down to GPU instructions or just to some IL which is then compiled again. Unfortunately its not open source, and it only works with fglrx, not Mesa so I stopped looking further. http://forums.amd.com/devforum/messageview.cfm?catid=390&threadid=120683&%20enterthread=y Best regards, --Edwin

> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of David A. Greene > Sent: Tuesday, August 10, 2010 12:05 PM > To: Helge Rhodin > Cc: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] PTX backend, BSD license > > Helge Rhodin <helge.rhodin at alice-dsl.net> writes: > > >> But I

Hi, in r176827 the optimization that turns invokes with empty landing pads into plain calls was disabled for invocations of function with the "uwtable" attribute. But given this code: struct S { ~S() {}; }; void blackbox(); __attribute__((__noinline__)) void inner() { blackbox(); } int foo() { S s; inner(); return 0; } int bar() {

Greetings - For a host of reasons I chose (was forced) to upgrade my multi-Opteron box from Fedora 7 -> Fedora 8. In the process, I also updated the ACML I had installed from 4.0.0 to 4.1.0. While I get no errors (that I can find) in the config -> make -> make install sequence, I'm pretty sure (based on some benchmarks) that I'm not getting BLAS and/or Lapack to compile in. So,

Helge Rhodin <helge.rhodin at alice-dsl.net> writes: >> But I didn't study their code thoroughly, so I might be wrong about this. >> > Yes, we don't use the target-independent code generator and the > backend is based on the CBackend. We decided to not use the code > generator because PTX code is also an intermediate language. The > graphics driver