search for: iswindows

...gt;>>> >>>> Maybe it should be MSVC specific then ? >>> >>> Sure, but presumably you want to differentiate between nasm and masm (if >>> they are not compatible) right? >> >> Right > > Then you need something more specific than 'isWindows'. I'd suggest, > isNASM and isMASM. 'for' rather than 'is' forMSVC ? There is more to it than that :( I was going from the _WIN32 preprocessor symbol. So maybe 'forWIN32' if it is actually needed. Aaron

On 6/2/2011 10:13 AM, Samuel Crow wrote: > Hi Nate, > > I've successfully ported one bitcode from Linux to Mac to Windows. All were x86 and the program was text-based, but I'd say my LLVM Wrapper would be worth some effort in the future if I could just get some help. Currently it just wraps StdIO.h with its own functions Naturally that would work perfectly fine on a similar

Hello, Does anyone know how to generate a Dwarf file for a Windows target? I discovered the DwarfWriter class, but I'm not sure how to add it to the pass manager. Also, what x86 subtarget should I use? From what I can tell, there are five choices: isELF, isDarwin, isCygwin, isMingw, and isWindows. isCygwin and isMingw appear to generate a COFF file in X86TargetMachine.cpp, but that seems unlikely because I don't see a COFF writer in the source code. The fifth choice, isWindows, appears to be the default Windows option that generates no debugging information. Any help would be greatly...

Hi, I tried that before, it produces .text ALIGN 16 .globl _main _main: ; @main ; BB#0: ; %entry subl $20, %esp movl $0, 16(%esp) movl 24(%esp), %eax movl %eax, 12(%esp) movl 28(%esp), %eax movl %eax, 8(%esp) movl $($_.str),

On Jan 28, 2010, at 1:31 AM, Alexander Herz wrote: > Hi, > > I tried that before, it produces Anton, the issue here is the 'isWindows' X86 sub-target. Should it just use the MCAsmInfo values as MingW? -Chris > > .text > ALIGN 16 > .globl _main > _main: ; @main > ; BB#0: ; %entry >...

Hi, Chris > Anton, the issue here is the 'isWindows' X86 sub-target.  Should it just use > the MCAsmInfo values as MingW? Yes, it should. This was fixed in r96165 -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Tue, 12 Jul 2005, Aaron Gray wrote: >>>> Sure, but presumably you want to differentiate between nasm and masm (if >>>> they are not compatible) right? >>> >>> Right >> >> Then you need something more specific than 'isWindows'. I'd suggest, >> isNASM and isMASM. > > 'for' rather than 'is' Yeah sorry. > forMSVC ? There is more to it than that :( > I was going from the _WIN32 preprocessor symbol. So maybe 'forWIN32' if it is > actually needed. I'll leave this...

...bove items. Also, when you do things like this, please send patches. Also, patches should generally be sent to the llvmbugs list (which is designed for bugs and patches), not llvmdev. In response to your recent 'MASM Backend' mail, please update it per the feedback I gave for the 'isWindows' flag email, and resent to llvmbugs. Thanks! -Chris -- http://nondot.org/sabre/ http://llvm.org/

...ease use something more specific. >>> >>> Maybe it should be MSVC specific then ? >> >> Sure, but presumably you want to differentiate between nasm and masm (if >> they are not compatible) right? > > Right Then you need something more specific than 'isWindows'. I'd suggest, isNASM and isMASM. >>>> 5. I notice that the stuff you are controlling enables/disables the exact >>>> same stuff as needed for cygwin. Will this change in the future? >>> >>> Same as Cygwin, so MSVC++ build, gas generated cod...

...e: > >>>>> Sure, but presumably you want to differentiate between nasm and >>>>> masm (if they are not compatible) right? >>>> >>>> >>>> Right >>> >>> >>> Then you need something more specific than 'isWindows'. I'd >>> suggest, isNASM and isMASM. >> >> >> 'for' rather than 'is' > > > Yeah sorry. > >> forMSVC ? There is more to it than that :( >> I was going from the _WIN32 preprocessor symbol. So maybe 'forWIN32' >&...

>>> You shouldn't have to add new classes to the .td file, just modify >>> printOp for your asmprinters. >> >> I dont think printOp is virtual and therefore cannot be overriden ? > > Why does it need to be virtual? No 'intel' printers want % signs. The GAS intel code generator generates percents, look at the X86InstrInfo.td file it is full of

I am building a package for various noncentral hypergeometric distributions. I want to include some heavy mathematical formulas. It appears that the build and INSTALL commands produce only .chm files and not .pdf files from my .Rd files under Windows. This means that it cannot show complicated mathematical formulas. The solution might be to include a .pdf file as a vignette. I tried that,

I am building a package for various noncentral hypergeometric distributions. I want to include some heavy mathematical formulas. It appears that the build and INSTALL commands produce only .chm files and not .pdf files from my .Rd files under Windows. This means that it cannot show complicated mathematical formulas. The solution might be to include a .pdf file as a vignette. I tried that,

...const sys::Path &Src) { 2.3 X86 stuff Patch lib/Target/X86/X86SubTarget.cpp & X86JITInfo.cpp in such way: X86SubTarget.cpp: #if defined(__CYGWIN__) || defined(__MINGW32__) TargetType = isCygwin; #elif defined(__APPLE__) TargetType = isDarwin; #elif defined(_WIN32) TargetType = isWindows; #endif X86JITInfo.cpp: #if defined(__CYGWIN__) || defined(__APPLE__) || defined(__MINGW32__) ".globl _X86CompilationCallback\n" "_X86CompilationCallback:\n" #else ... #if defined(__CYGWIN__) || defined(__APPLE__) || defined(__MINGW32__) "call _X86CompilationCall...

Hi Nate, I've successfully ported one bitcode from Linux to Mac to Windows.  All were x86 and the program was text-based, but I'd say my LLVM Wrapper would be worth some effort in the future if I could just get some help.  Currently it just wraps StdIO.h with its own functions. Here's some of what it would take to make portable bitcodes in C or LLVM Assembly: * Convert all

>>> 1. Please send patches instead of full files. The best way to do this >>> is >>> to use CVS like this: 'cvs diff -u' in the directory that you care >>> about. You can also specify specific files to diff as well. >> >> Okay, I will do this in future, our posts crossed so I have not done that >> for the MASM backend. I will

Dear Forum, I installed MetaTrader 4 with wine it is up and running everything works well, the best performers is with the new wine 1.3. BUT if I run some EA Experts Advisors I get on two of it problems and the application crashes. The EA`s with crashes have custom .dll (FCS300.dll) and I try to debug this errors. Code: 0028:Ret ntdll.RtlFreeHeap() retval=00000001 ret=7d7984a2 0028:Ret

hi, i have downloaded newest wine version (20040309) and installed lotus notes on it. i use debian woody/stable. i have followed the german mini-howto, installed the dll's and so on, noticed on this site, but when i try to start it, i get many information, til it stops. here the last lines: rr:module:import_dll No implementation for COMCTL32.dll.FlatSB_SetScrollRange imported from

...erentiate between nasm and >>>>>> masm (if they are not compatible) right? >>>>> >>>>> >>>>> >>>>> Right >>>> >>>> >>>> >>>> Then you need something more specific than 'isWindows'. I'd >>>> suggest, isNASM and isMASM. >>> >>> >>> >>> 'for' rather than 'is' >> >> >> >> Yeah sorry. >> >>> forMSVC ? There is more to it than that :( >>> I was going from the...

...so, when you do things like this, please send patches. Also, patches > should generally be sent to the llvmbugs list (which is designed for bugs > and patches), not llvmdev. In response to your recent 'MASM Backend' > mail, please update it per the feedback I gave for the 'isWindows' flag > email, and resent to llvmbugs. I will make these changes and create some patches. Aaron