search for: sychoe

...is one of them. The reason your Ubuntu stdint.h works is because, coincidentally, Clang's stdint.h uses the same layout and pre-processor built-ins as GCC. This is an implementation detail. Do not rely upon it. You should use Clang's stdint.h. Cheers, James From: Seung-yeon Choe [mailto:sychoe at gmail.com] Sent: 24 November 2011 05:42 To: James Molloy Cc: Anton Korobeynikov; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] arm neon intrinsics cross compile error on windows system Hello, I totally understood about this problem. codesourcery codebench arm eabi version uses newlibc. but, ar...

...he same layout and pre-processor built-ins as GCC.* > *** > > ** ** > > This is an implementation detail. Do not rely upon it. You should use > Clang’s stdint.h.**** > > ** ** > > Cheers,**** > > ** ** > > James**** > > *From:* Seung-yeon Choe [mailto:sychoe at gmail.com] > *Sent:* 24 November 2011 05:42 > *To:* James Molloy > *Cc:* Anton Korobeynikov; llvmdev at cs.uiuc.edu > > *Subject:* Re: [LLVMdev] arm neon intrinsics cross compile error on > windows system**** > > ** ** > > Hello,**** > > ** ** > > I tot...

Hello, I totally understood about this problem. codesourcery codebench arm eabi version uses newlibc. but, arm gnu/linux version uses glibc. hm.. actually there is no problem. it was my mistake as james told me. Thanks. 2011/11/24 Seung-yeon Choe <sychoe at gmail.com> > Hello, James Molly. > > Thank you for your advices. > > Now I aware that this is the problem of stdint.h. And, codesourcery > toolchain also has stdint.h header file at same place of stdio.h > > Generally, Clang has "lib/clang/3.0/include" defau...

Hello, James Molly. Thank you for your advices. Now I aware that this is the problem of stdint.h. And, codesourcery toolchain also has stdint.h header file at same place of stdio.h Generally, Clang has "lib/clang/3.0/include" default search path. If I added codesourcery toolchain path for stdio.h with -I option, stdint.h has been loaded at the specified toolchain path first cuz

Dear all. I built the LLVM 3.0 rc4 with Clang front-end in windows os env. (also with -DLLVM_TARGETS_TO_BUILD=all option) For arm neon intrinsics testing, I tried to compile some codes, which are included a few neon intrinsics. Although I got a well done bitcode on ubuntu build pc, it shows some errors when compile the codes on windows. Could you let me know why occurred errors? is this just a

Dear all I'd wonder why executable's debug information size is bigger than gcc dwarf debug info. When I compiled ARM hello world code with -g option, the arm based assembly and executable files are bigger than gcc results significiantly.(apx. 3x) (source file size was only 3KB) I think that both clang and gcc use same dwarf format ver2 for debugging. But I don't know why the clang

Hello, Anton Korobeynikov. I just built the llvm using ms visual studio 2010 and ran the compile command on windows default command console. additionally, I also specified include dir of arm codesourcery latest toolchain because of missing stdio.h and stdint.h . Thanks and best regards, Seung-yeon. 2011/11/23 Anton Korobeynikov <anton at korobeynikov.info> > Hello > > > In