search for: fpascal

...e patch. Unfortunately, there wasn't a testcase that I could use that was small and wouldn't require modification after every compiler change. Looking at the bug report, I've attached the testcase below. You can compile it like this: $ llvm-gcc -Os -fmessage-length=0 -pipe -std=gnu99 -fpascal-strings -fasm-blocks -pedantic -msse3 test.c -o test.s -S See the attached test.s for comments on what is wrong with the output. You're correct that proper physical register liveness information is required for a less conservative fix. However, I don't know if that will ever happen. If it...

Hello. I am not sure this is the right place to ask but here is my question. About a year ago there was a fix of some obscure bug (rdar://problem/8030636 which is located on the internal Apple bugtracker I believe and so not available to the general public :)) Some discussion can be found here: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20100531/102160.html. Unfortunately, no

...ssible for the application in question. Here's the (abriged) build command: CompileC build/Objects-normal/i386/gen_codegen.o gen_codegen.cpp normal i386 c++ com.apple.compilers.gcc.4_0 cd llvm /Developer/usr/bin/gcc-4.0 -x c++ -arch i386 -fmessage-length=0 - pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -isysroot / Developer/SDKs/MacOSX10.4u.sdk -fvisibility-inlines-hidden -mmacosx- version-min=10.4 -gdwarf-2 -iquote /build/codegen.build/codegen- generated-files.hmap -I/llvm/build/codegen.build/codegen-own-target- headers.hmap -I/codegen.build/codegen-all-target-header...

...ude/llvm/Config/config.h after you configure. -Chris > > CompileC build/Objects-normal/i386/gen_codegen.o gen_codegen.cpp > normal i386 c++ com.apple.compilers.gcc.4_0 > cd llvm > /Developer/usr/bin/gcc-4.0 -x c++ -arch i386 -fmessage-length=0 - > pipe -Wno-trigraphs -fpascal-strings -fasm-blocks -O0 -isysroot / > Developer/SDKs/MacOSX10.4u.sdk -fvisibility-inlines-hidden -mmacosx- > version-min=10.4 -gdwarf-2 -iquote /build/codegen.build/codegen- > generated-files.hmap -I/llvm/build/codegen.build/codegen-own-target- > headers.hmap -I/codegen.build/codeg...

...e patch. Unfortunately, there wasn't a testcase that I could use that was small and wouldn't require modification after every compiler change. Looking at the bug report, I've attached the testcase below. You can compile it like this: $ llvm-gcc -Os -fmessage-length=0 -pipe -std=gnu99 -fpascal-strings -fasm-blocks -pedantic -msse3 test.c -o test.s -S See the attached test.s for comments on what is wrong with the output. You're correct that proper physical register liveness information is required for a less conservative fix. However, I don't know if that will ever happen. If it...

Hi, For the record, adding UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.4u.sdk/ was insufficient to restrict the .a/.o files to link against the 10.4 sdk, but env MACOSX_DEPLOYMENT_TARGET=10.4 make did the trick. Thanks! On Jan 14, 2009, at 1:29 PM, Jean-Daniel Dupas wrote: > > Le 14 janv. 09 à 21:48, Chris Lattner a écrit : > >> >> On Jan 14, 2009, at 12:44 PM,

Le 14 janv. 09 à 21:48, Chris Lattner a écrit : > > On Jan 14, 2009, at 12:44 PM, Graham Wakefield wrote: > >> Sorry if this is a newb q... I'm developing an application on a >> 10.5 machine but want to target the 10.4 SDK. Is there a magic >> incantation for the llvm configure script to set the sysroot path, >> equivalent to e.g. --with-sysroot

...leC build/llvmAV.build/Release/weirdbug_nolib.build/Objects- normal/i386/main_weird.o /code/luaAV/oct08/mergathon/llvmAV/ main_weird.cpp normal i386 c++ com.apple.compilers.gcc.4_0 cd /code/luaAV/oct08/mergathon/llvmAV /Developer/usr/bin/gcc-4.0 -x c++ -arch i386 -pipe -Wno- trigraphs -fpascal-strings -Os -fmessage-length=0 -fvisibility- inlines-hidden -mmacosx-version-min=10.4 -I/code/luaAV/oct08/ mergathon/llvmAV/build/llvmAV.build/Release/weirdbug_nolib.build/ weirdbug_nolib.hmap -Wmost -Wno-four-char-constants -Wno-unknown- pragmas -F/code/luaAV/oct08/mergathon/llvmAV/build/Relea...

If wxRuby-SWIG is as usable as wxRuby 0.6.0, maybe it should be given a version number and packaged up for download. Given the nature of SWIG, having a lot more people use it would probably result in more code contributions to this project. Seems most of the changes are 2+ months old, so I''m guessing wxRuby-SWIG is fairly stable right now in terms of frequency of changes...