llvm

I'm compiling LLVM as well as clang. I noticed that the output of compilation has llvm[1]: or llvm[2]: or llvm[3] : prefixed to each line. What do those integers in brackets mean? It's the number of the compilation job ( make -j ). Helpful to trace compilation errors. Apparently, it's not connected to the number of the compilation job (can be easily checked via make -j 1). The autoconf-based build system indicates the "level" of the makefile inside the source tree). To be prices, it's a value of make's MAKELEVEL variable. The currently accepted answer is not correct. Furthermore, this is

I have a cpp file and the bitcode using clang 9. Now, I select a cpp line number from the source code and I want to get the LLVM bit code line number for this source code line instead of manually doing disassembly of bit code file and reading the file line by line. Please tell me if it is possible and how. There may not be a set of IR instructions that correspond clearly to that exact line... but it's possible, mostly. There is a function called Instruction::getDebugLoc() that returns the file name and line number for that particular instruction, if it returns anything at all. You can use that

I've just tried compiling an iOS project using the the LLVM 1.5 compiler (included in XCode 3.2.3), and I got a lot of new warnings, including several like this: protocol qualifiers without 'id' is archaic For instance, this happens on lines like this: - (id)initWithContext:(NSManagedObjectContext *)context coordinator:(NSPersistentStoreCoordinator *)coordinator delegate:(<NSFetchedResultsControllerDelegate>)delegate; Now, I think this is probably a "naming conventions" warning, but anyone know what it really means? Archaic: extremely old or extremely old-fashioned . The warning means a

I'm using LLVM 7 and I have an llvm::Module that I'd like to optimize using the standard optimization pipeline. Unfortunately, there isn't a llvm::runDefaultOptimizations function that I can call. There seems to be a bajillion ways to optimize a module in LLVM. My searches on this topic have found many old/depreciated APIs and some examples that don't work on my system. I want to run all of the standard optimizations at -O3 with the least amount of hassle possible. I don't want to manually list all of the passes or even write a for loop. I thought llvm::PassBuilder:

I was just wondering, why is there no autorelease pool optimization under the ARC compiler, where it would retain an object in the innermost scope, remove it from the autorelease pool and release once the object is no longer in use? To quote a very impractical example from another question, for(NSUInteger i = 0; i < 10000; i++) { for(NSUInteger j = 0; j < 10000; j++) { NSNumber* n = [NSNumber numberWithUnsignedInteger:j]; //NSLog(@"%@", n); //Disabled this to increase memory bloat faster. } } Without @autoreleasepool { ... } wrapping, memory grows and grows. Wrapping with @autoreleasepool ,