search for: forwindows

Here is a mod to X86 that allows GAS to be used with MS Visual C++. I introduces a 'forWindows' variable like 'forCygwin' in th X86SharedAsmPrinter class. This may prompt thurther normalization, on the otherhand it may not :) Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050711/17...

On Mon, 11 Jul 2005, Aaron Gray wrote: > Here is a mod to X86 that allows GAS to be used with MS Visual C++. > > I introduces a 'forWindows' variable like 'forCygwin' in th > X86SharedAsmPrinter class. > A couple of comments: 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 speci...

hi, I am Praveen , working in Yash Technologies , I would like to know your contact number as we want to know whether the speex codec is compatible with the Windows Mobile 5.0 or not . Also can we get the source code for the pocket pc version of the speex codec . Hope we get your contact number soon. thanks, Praveen --------------------------------- Yahoo! India Answers: Share

...I've also followed all the instructions in the guide to cross-compiling by Yan and Rossini. When I try to cross-compile I get a load of errors, apparently due to R.h (and possibly other things) not being found: [snip - everything fine up to here] i586-mingw32-g++ -isystem /home/harry/RLibrary/forWindows/cross-tools/i586-mingw32/include -I/home/harry/RLibrary/forWindows/WinR/R-2.6.0/include -Wall -O2 -c adaboost.cpp -o adaboost.o In file included from dataset.h:20, from node_terminal.h:21, from distribution.h:20, from adaboost.h:20,...

>> Here is a mod to X86 that allows GAS to be used with MS Visual C++. >> >> I introduces a 'forWindows' variable like 'forCygwin' in th >> X86SharedAsmPrinter class. >> > > A couple of comments: > > 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 >...

...t do not want to release yet. So I may have gotten out of sync here. Ok >> 3. You need to invent a target triple for your new configuration. You'll >> notice that the forCygwin/forDarwin variables are set based on the >> target triple of the module... as you coded it, forWindows is only >> ever set if the t-t is empty. > > Right, presumably Wndows does not set the TT. Should Windows or MSVC++ > have one ? If so how do I go about it. Maybe Jeff should be involved ? It should/will. Currently there is no C/C++ front-end that works on native windows, but...

...roceedure in place to avoid possible confusion. >>> 3. You need to invent a target triple for your new configuration. >>> You'll >>> notice that the forCygwin/forDarwin variables are set based on the >>> target triple of the module... as you coded it, forWindows is only >>> ever set if the t-t is empty. >> >> Right, presumably Wndows does not set the TT. Should Windows or MSVC++ >> have one ? If so how do I go about it. Maybe Jeff should be involved ? > > It should/will. Currently there is no C/C++ front-end that works...

Jeff Cohen wrote: > Chris Lattner wrote: > >> 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 >>>> >>>>

...pc-cygwin and mingw uses i686-pc-mingw32, so I think that >> using i686-pc-masm and i686-pc-nasm make sense. > > Okay, how do we implement that ? In your LLC changes, just check for *-nasm and/or *-masm in the same places that *-darwin and *-cygwin are. >>>> 4. The name forWindows isn't very specific, as there are multiple dev >>>> systems available on windows (including cygwin, mingw, masm, nasm, >>>> etc). Please use something more specific. >>> >>> Maybe it should be MSVC specific then ? >> >> Sure, but pr...

Chris Lattner wrote: > 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

...86AsmPrinter.cpp lib/Target/X86/X86MASMPrinter.h lib/Target/X86/X86MASMPrinter.cpp lib/Target/X86/X86.td lib/Target/X86/X86InstrInfo.td lib/Target/X86/makefile Makefile.rules win32/x86/x86.vcproj X86AsmPrinter.{cpp|h} - have new variable 'forWindows' added which fits in with working with GAS on MSVC++ build. X86AsmPrinter.cpp also has the new 'masm' target added. X86MASMPrinter.{cpp|h} - X86MASMPrinter class X86.td, X86InstrInfo.td, makefile, Makefile.rules - have new GenAsmWriter2.inc target added. win32/x86/x86.vcproj - Window...

On Tue, 12 Jul 2005, Aaron Gray wrote: >>> X86InstrInfo.td file it is full of them. >> >> Ah, I see what you're talking about. Please feel free to remove all of >> those from the Intel format. For example, change this: >> >> def IN8rr : I<0xEC, RawFrm, (ops), >> "in{b} {%dx, %al|%AL, %DX}">, Imp<[DX],

>> The GAS intel code generator generates percents, look at the >> X86InstrInfo.td file it is full of them. > > Ah, I see what you're talking about. Please feel free to remove all of > those from the Intel format. For example, change this: > > def IN8rr : I<0xEC, RawFrm, (ops), > "in{b} {%dx, %al|%AL, %DX}">, Imp<[DX],

...hat using i686-pc-masm and i686-pc-nasm make sense. >> >> Okay, how do we implement that ? > > In your LLC changes, just check for *-nasm and/or *-masm in the same > places that *-darwin and *-cygwin are. Okay I will look into that tommorow. >>>>> 4. The name forWindows isn't very specific, as there are multiple dev >>>>> systems available on windows (including cygwin, mingw, masm, nasm, >>>>> etc). Please use something more specific. >>>> >>>> Maybe it should be MSVC specific then ? >>> &gt...

...6/X86MASMPrinter.h > lib/Target/X86/X86MASMPrinter.cpp > lib/Target/X86/X86.td > lib/Target/X86/X86InstrInfo.td > lib/Target/X86/makefile > Makefile.rules > win32/x86/x86.vcproj > >X86AsmPrinter.{cpp|h} - have new variable 'forWindows' added which fits in >with working with GAS on MSVC++ build. X86AsmPrinter.cpp also has the new >'masm' target added. > >X86MASMPrinter.{cpp|h} - X86MASMPrinter class > >X86.td, X86InstrInfo.td, makefile, Makefile.rules - have new >GenAsmWriter2.inc target added....