search for: notyp

Displaying 20 results from an estimated 52 matches for "notyp".

Did you mean: notype
2008 Nov 12
0
libxen-dev: multiple symbol definition
...enguest.a(xg_private.o): In function `lock_pages': (.text+0x4d0): multiple definition of `lock_pages' /usr/lib/libxenctrl.a(xc_private.o):(.text+0x700): first defined here collect2: ld returned 1 exit status Indeed: /usr/lib$ readelf -s libxenctrl.a | grep lock_pages 8: 00000000 0 NOTYPE GLOBAL DEFAULT UND lock_pages 10: 00000000 0 NOTYPE GLOBAL DEFAULT UND unlock_pages 8: 00000000 0 NOTYPE GLOBAL DEFAULT UND lock_pages 10: 00000000 0 NOTYPE GLOBAL DEFAULT UND unlock_pages 15: 00000000 0 NOTYPE GLOBAL DEFAULT UND lock_pages 17: 000000...
2012 Oct 19
0
[LLVMdev] Section specialization & COFF.
On Fri, Oct 19, 2012 at 2:55 AM, r4start <r4start at gmail.com> wrote: > Hi all. > > While compiling next code > @A = weak unnamed_addr constant { i32, i32, i32 } { i32 0, i32 0, i32 0 }, > section ".data" > was discovered that llc ignores weak linkage if we emit it in COFF object. > Attached patch solves this problem, please review. > > I found some
2012 Oct 10
0
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
Great, thanks for your help. I'll take a crack at it and contact Renato if I have questions. -Greg On Wed, Oct 10, 2012 at 1:05 PM, Jim Grosbach <grosbach at apple.com> wrote: > Cool; glad to help. > > When I added the data region bits, I tried to keep the ARM-style annotations in mind a bit, so hopefully things will fit together without too much trouble. > > -Jim >
2012 Oct 19
2
[LLVMdev] Section specialization & COFF.
Hi all. While compiling next code @A = weak unnamed_addr constant { i32, i32, i32 } { i32 0, i32 0, i32 0 }, section ".data" was discovered that llc ignores weak linkage if we emit it in COFF object. Attached patch solves this problem, please review. I found some similar tests in test/Objects/Inputs. Should I do something like trivial.ll checking or there is a better way to check
2012 Oct 16
5
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
...hat field in the doc. Lastly, from MCELFStreamer, how do I determine if we generating an ARM or Thumb ELF? I can catch Thumb from the EmitThumbFunc, but that seems a little odd. Suggestions? Here's what I have so far: $ readelf -s via-llvm-as.o | grep "\$." 2: 00000000 0 NOTYPE LOCAL DEFAULT 4 $d 3: 00000000 0 NOTYPE LOCAL DEFAULT 4 $t $ readelf -s via-gcc-as.o | grep "\$." 5: 00000000 0 NOTYPE LOCAL DEFAULT 1 $t 15: 0000020c 0 NOTYPE LOCAL DEFAULT 1 $d 17: 00000218 0 NOTYPE LOCAL DEFAULT 1 $t 44:...
2012 Oct 22
2
[LLVMdev] Section specialization & COFF.
...numbers 0 number of relocations 0 number of line numbers C0301040 flags Initialized Data COMDAT; sym= _aaa 4 byte align Read Write RAW DATA #3 00000000: F3 E0 01 00 oa.. COFF SYMBOL TABLE 000 00AA9D1B ABS notype Static | @comp.id 001 00000001 ABS notype Static | @feat.00 002 00000000 SECT1 notype Static | .drectve Section length 2F, #relocs 0, #linenums 0, checksum 0 004 00000000 SECT2 notype Static | .debug$S Section length 64,...
2015 Sep 18
5
Fwd: Skipping names of temporary symbols increased size of ARM binaries.
...clang++ -c -o main.o -O0 -g --target=armv7l-linux-gnueabihf main.cpp and then look at the symbols readelf -s main.o there will be a number of similar entries (showing one entry only here for conciseness): Num: Value Size Type Bind Vis Ndx Name 7: 00000062 0 NOTYPE LOCAL DEFAULT 9 These are the .Linfo_string<index> symbols whose names are skipped due to r236642. If we now link it clang++ -o main.out --target=armv7l-linux-gnueabihf main.o all the symbols get through to the final binary: readelf -s main.out Num: Value Size Type...
2012 Jun 07
0
[LLVMdev] MC disassembler for ARM
...table. Similarly each stretch of Thumb code gets a "$t" and each data a "$d". For example if I assemble: .arm mov r0, r3 ldr r2, Lit Lit: .word 42 add r0, r0, r0 .thumb mov r5, r2 then the symbol table contains these entries: 4: 00000000 0 NOTYPE LOCAL DEFAULT 1 $a [...] 6: 00000008 0 NOTYPE LOCAL DEFAULT 1 $d 7: 0000000c 0 NOTYPE LOCAL DEFAULT 1 $a 8: 00000010 0 NOTYPE LOCAL DEFAULT 1 $t which shows that an ARM region begins at offset 0x0, a data one at offset 0x8, we switch back to ARM...
2010 Mar 11
0
Different results for different order of factor levels?
...is a set of code used to get the coefficients for two different orders of factor levels. THE CODE USED TO GET THE COEFFICIENTS: #Abbr = Subject #PDSI = covariate #PDSI2 = PDSI^2 (To fit a polynomial) #Set the Level order i.levels<-c("Mixed","Short","Tall","NoType") #I am not interested in this level for my comparison data.sub <- data[which(data$indep != "NoType"),] #Convert the data into factors data$indep<-factor(data$indep, levels = i.levels) #Run the model F <- lme(response~indep+PDSI+PDSI2+indep:PDSI+indep:PDSI2, random = ~...
2012 Jun 07
2
[LLVMdev] MC disassembler for ARM
..." and each data a "$d". > > For example if I assemble: > > .arm > mov r0, r3 > ldr r2, Lit > Lit: > .word 42 > add r0, r0, r0 > .thumb > mov r5, r2 > > then the symbol table contains these entries: > 4: 00000000 0 NOTYPE LOCAL DEFAULT 1 $a > [...] > 6: 00000008 0 NOTYPE LOCAL DEFAULT 1 $d > 7: 0000000c 0 NOTYPE LOCAL DEFAULT 1 $a > 8: 00000010 0 NOTYPE LOCAL DEFAULT 1 $t > > which shows that an ARM region begins at offset 0x0, a data one at > off...
2012 Oct 10
2
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
Cool; glad to help. When I added the data region bits, I tried to keep the ARM-style annotations in mind a bit, so hopefully things will fit together without too much trouble. -Jim On Oct 10, 2012, at 12:05 PM, Renato Golin <rengolin at systemcall.org> wrote: > Thanks Jim! > > I have updated the bug with your comments, I think it's a good start. > > Greg, let me know
2017 Feb 16
3
Linker error with XRay & GCC/libstdc++ 6.1
Hi Dean, Wondering if you've seen anything like this: /usr/local/google/home/blaikie/dev/llvm/build/clang/debug/split/notypes/nostandalone/projects/compiler-rt/lib/xray/tests/unit && /usr/local/google/home/blaikie/dev/llvm/build/clang/debug/split/notypes/nostandalone/./bin/clang fdr_logging_test.cc.x86_64.o xray_unit_test_main.cc.x86_64.o gtest-all.cc.x86_64.o -o /usr/local/google/home/blaikie/dev/llvm/build/cla...
2012 Jun 08
2
[LLVMdev] MC disassembler for ARM
...For example if I assemble: >> >> .arm >> mov r0, r3 >> ldr r2, Lit >> Lit: >> .word 42 >> add r0, r0, r0 >> .thumb >> mov r5, r2 >> >> then the symbol table contains these entries: >> 4: 00000000 0 NOTYPE LOCAL DEFAULT 1 $a >> [...] >> 6: 00000008 0 NOTYPE LOCAL DEFAULT 1 $d >> 7: 0000000c 0 NOTYPE LOCAL DEFAULT 1 $a >> 8: 00000010 0 NOTYPE LOCAL DEFAULT 1 $t >> >> which shows that an ARM region begins at offset 0x0...
2012 Jun 07
2
[LLVMdev] MC disassembler for ARM
Hi Tim, Thanks a lot for the reply. I tested libc.so which is a shared library. llvm-objdump also report some disassemble errors. Could you please tell me more about $a, $t and $d symbols? How these symbols are used to define different regions? Where I can find this symbols in ELF object file? Thanks, David I'm now try to find a decoder of ARM instructions in oder On Thu, Jun 7, 2012
2012 Jun 07
0
[LLVMdev] MC disassembler for ARM
...ot; and each data a "$d". > > For example if I assemble: > > .arm > mov r0, r3 > ldr r2, Lit > Lit: > .word 42 > add r0, r0, r0 > .thumb > mov r5, r2 > > then the symbol table contains these entries: > 4: 00000000 0 NOTYPE LOCAL DEFAULT 1 $a > [...] > 6: 00000008 0 NOTYPE LOCAL DEFAULT 1 $d > 7: 0000000c 0 NOTYPE LOCAL DEFAULT 1 $a > 8: 00000010 0 NOTYPE LOCAL DEFAULT 1 $t > > which shows that an ARM region begins at offset 0x0, a data one at > of...
2017 Mar 09
2
Use of host/target compiler when building compiler-rt
...w, so > removing it seems like a not great idea at the moment. > > > That said, I tried putting compiler-rt in runtimes instead of projects and > I got a bunch of cmake errors starting with: > > CMake Error at > /usr/local/google/home/blaikie/dev/llvm/build/clang/debug/split/notypes/nostandalone/lib/cmake/llvm/AddLLVM.cmake:1174 > (add_dependencies): > The dependency target "GotsanRuntimeCheck" of target "check-runtimes" > does > not exist. > Call Stack (most recent call first): > CMakeLists.txt:110 (add_lit_target) > > Any i...
2001 Aug 15
3
RC2 artifacts
...However, I've been playing with RC2 and I've still been banging my head into a number of problems. A majority of the music I make has long drones with a fair amount of spectral content, and I often find these play havok with the encoder. Here is a recent example I ran into. http://www.notype.com/users/833-45/ogg/fadein_01.ape http://www.notype.com/users/833-45/ogg/fadein_01.pac original file (monkey's audio & lpac compression). rc2 ogg files: http://www.notype.com/users/833-45/ogg/fadein_64.ogg http://www.notype.com/users/833-45/ogg/fadein_128.ogg http://www.notype.com/user...
2012 Jun 08
0
[LLVMdev] MC disassembler for ARM
...or example if I assemble: >> >> .arm >> mov r0, r3 >> ldr r2, Lit >> Lit: >> .word 42 >> add r0, r0, r0 >> .thumb >> mov r5, r2 >> >> then the symbol table contains these entries: >> 4: 00000000 0 NOTYPE LOCAL DEFAULT 1 $a >> [...] >> 6: 00000008 0 NOTYPE LOCAL DEFAULT 1 $d >> 7: 0000000c 0 NOTYPE LOCAL DEFAULT 1 $a >> 8: 00000010 0 NOTYPE LOCAL DEFAULT 1 $t >> >> which shows that an ARM region begins at offset 0x...
2012 Oct 16
0
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
...That was the only part I didn't know how to get. Jim should know. > I can catch Thumb from the EmitThumbFunc, but that seems a > little odd. Ignore EmitThumbFunc, it has nothing to do with your change. > $ readelf -s via-llvm-as.o | grep "\$." > 2: 00000000 0 NOTYPE LOCAL DEFAULT 4 $d > 3: 00000000 0 NOTYPE LOCAL DEFAULT 4 $t Clearly, you're not detecting all code/data changes, or the direct ELF emission is not creating too many constant pools. Can you attach the assembly generated and the ELF object created from both the inline as...
2006 Sep 08
2
[LLVMdev] build broken on linux/amd64
...allback' /home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function `llvm::X86JITInfo::emitFunctionStub(void*, llvm::MachineCodeEmitter&)': /home/rafael/dev/llvm/cvs/lib/Target/X86/X86JITInfo.cpp:225: undefined reference to `X86CompilationCallback' 68: 0000000000000000 0 NOTYPE GLOBAL DEFAULT 21 _X86CompilationCallback 69: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UND _X86CompilationCallback2 77: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UND X86CompilationCallback 93: 00000000000002da 209 FUNC GLOBAL DEFAULT 21 X86CompilationCallback2 Bes...