search for: fblocks

I'm trying to compile some C++ code on Windows that contains blocks. The compiler gives me the error that the blocks language feature is not enabled and that I should enable it with "-fblocks". When I add that compiler flag, the compile fails immediately saying "unknown argument: '-fblocks'" Is this perhaps an incomplete feature? Regards, Eric Mader

Hello, i try to compile a small test programm with clang and the command line option -fblocks. clang -m32 -march=i686 -D__COCOTRON__ -DWINDOWS -D_GNU_SOURCE -D__LITTLE_ENDIAN__ -D_FORTIFY_SOURCE=1 -x objective-c -fobjc-exceptions -fconstant-string-class=NSConstantString -O2 -Wno-unknown-pragmas -fmessage-length=0 --std=c99 -pipe -Ic:/devel/tools/mingw64/lib/gcc/x86_64-w64-mingw32/4.7.1/inc...

Hi Curtis, > I hope this is the right list for such questions.... I've been trying to > get LLVM compiled under Linux (Ubuntu 9.04, 64 bit) for the last couple > of days. I can't reproduce this with ubuntu 9.10, 64 bit x86, gcc 4.4.1, using your configure options. What version of gcc are you using? > CXXFLAGS="-fPIC" ./configure --enable-optimized

I hope this is the right list for such questions.... I've been trying to get LLVM compiled under Linux (Ubuntu 9.04, 64 bit) for the last couple of days. It all ends with the error: llvm[2]: Linking Release executable tblgen (without symbols) /home/cjones/Desktop/Build/llvm/utils/TableGen/Release/ AsmMatcherEmitter.o: In function `(anonymous

...ation of linker directives for automatic library linking">; +def fauto_profile : Flag<["-"], "fauto-profile">, Group<f_Group>, + Flags<[DriverOption, CC1Option]>, + HelpText<"Enable automatic profile guided optimizations">; + def fblocks : Flag<["-"], "fblocks">, Group<f_Group>, Flags<[CC1Option]>, HelpText<"Enable the 'blocks' language feature">; def fbootclasspath_EQ : Joined<["-"], "fbootclasspath=">, Group<f_Group>; diff --git a/li...

...d. llvm is in the path that contains "Build/llvm- objcts" while llvm-gcc is in "Install/llvm-gcc-4.4.2". Maybe there's some "-L" that I need to specify? I've written a very small main.c that uses blocks, and when I try to compile/link it, I get: $ clang -fblocks -v -o a.out main.c clang version 1.1 (http://llvm.org/svn/llvm-project/cfe/trunk ) Target: x86_64-unknown-linux-gnu Thread model: posix "/home/cjones/Desktop/Build/llvm-objects/bin/clang-cc" -triple x86_64-unknown-linux-gnu -S -disable-free -main-file-name main.c -- relocation-model...

...ilt-in specs. Target: x86_64-unknown-linux-gnu Configured with: ../llvm-gcc-svn/configure --prefix=/home/cjones/ Desktop/Install/llvm-gcc-svn --program-prefix=llvm- --enable- languages=c,c++ --disable-multilib --enable-llvm=/home/cjones/Desktop/ Install/llvm $ ~/Desktop/Install/llvm/bin/clang -fblocks -v -o a.out main.c clang version 1.1 (http://llvm.org/svn/llvm-project/cfe/trunk ) Target: x86_64-unknown-linux-gnu Thread model: posix "/home/cjones/Desktop/Install/llvm/bin/../libexec/clang-cc" -triple x86_64-unknown-linux-gnu -S -disable-free -main-file-name main.c -- relocation-m...

When trying to link more than one object files compiled with clang, I run into errors of the following type: $ clang -fblocks -g -I$HOME/opt/include -L$HOME/opt/lib/ -o helloworld helloworld.c hello.o world.o -lBlocksRuntime world.o: In function `gnu_dev_major': /usr/include/sys/sysmacros.h:43: multiple definition of `gnu_dev_major' hello.o:/usr/include/sys/sysmacros.h:43: first defined here world.o: In function `...

The syntax below works, and gives the expected results, in R version 2.0.0, provided that I have loaded packages Matrix, latticeExtra and lme4. However, I cannot get it to work in version 2.2.1. Can anyone tell me how to fit this model in the more recent version? Thanks in anticipation, Nick Galwey barleyprogeny.model1lme <- lme(yield_g_m2 ~ 1, data =

...IDEs that support it 4) Fix some compiler warnings. GCC 4.3.3 seems super strict about %p. function pointers can't be cast to void * either. 5) Avoid a warning for apple_versioning.c that "ISO C does not allow empty files" Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and -fblocks to define and copy some blocks (and invoke them, obviously). Also tested on Mac OS X 10.6 and linking against -lBlocksRuntime ahead of -lSystem. -------------- next part -------------- A non-text attachment was scrubbed... Name: blocks-linux.diff Type: application/octet-stream Size: 10483 byte...

...omatic > library linking">; > > +def fauto_profile : Flag<["-"], "fauto-profile">, Group<f_Group>, > + Flags<[DriverOption, CC1Option]>, > + HelpText<"Enable automatic profile guided optimizations">; > + > def fblocks : Flag<["-"], "fblocks">, Group<f_Group>, Flags<[CC1Option]>, > HelpText<"Enable the 'blocks' language feature">; > def fbootclasspath_EQ : Joined<["-"], "fbootclasspath=">, Group<f_Group>; >...

...t/SemaCXX/goto.cpp?r1=127752&r2=128255&diff_format=h causes: FAIL: Clang :: SemaCXX/goto.cpp (2268 of 2917) ******************** TEST 'Clang :: SemaCXX/goto.cpp' FAILED ******************** Script: -- /home/dim/obj/llvm-1/Release+Asserts/bin/clang -cc1 -fsyntax-only -verify -Wall -fblocks /home/dim/src/llvm-2.9rc2/tools/clang/test/SemaCXX/goto.cpp -- Exit Code: 1 Command Output (stderr): -- error: 'error' diagnostics seen but not expected: Line 73: redefinition of 'f' error: 'note' diagnostics seen but not expected: Line 5: previous definition is here 2...

On 14/12/09 13:57, Abhishek Kulkarni wrote: > When trying to link more than one object files compiled with clang, I run into > errors of the following type: > > $ clang -fblocks -g -I$HOME/opt/include -L$HOME/opt/lib/ -o helloworld > helloworld.c hello.o world.o -lBlocksRuntime > world.o: In function `gnu_dev_major': > /usr/include/sys/sysmacros.h:43: multiple definition of `gnu_dev_major' > hello.o:/usr/include/sys/sysmacros.h:43: first defined here &g...

...bitcast (void ()* @foo to i8*)], section "llvm.metadata" # Compile IR -> Obj directly. clang -cc1 -triple x86_64-apple-macosx10.13.0 -emit-obj -fembed-bitcode=all -x ir test.ll -o test_ll.o # Compile IR -> BC -> Obj. clang -cc1 -triple x86_64-apple-macosx10.13.0 -emit-llvm-bc -fblocks -fencode-extended-block-signature -x ir test.ll -o test.bc clang -cc1 -triple x86_64-apple-macosx10.13.0 -emit-obj -fembed-bitcode=all -x ir test.bc -o test_bc.o # Extract and disassemble embedded bitcode from both scenarios. segedit test_bc.o -extract __LLVM __bitcode bc_bc.bc segedit test_ll.o...

...t; >> >> # Compile IR -> Obj directly. >> clang -cc1 -triple x86_64-apple-macosx10.13.0 -emit-obj -fembed- >> bitcode=all -x ir test.ll -o test_ll.o >> >> # Compile IR -> BC -> Obj. >> clang -cc1 -triple x86_64-apple-macosx10.13.0 -emit-llvm-bc -fblocks - >> fencode-extended-block-signature -x ir test.ll -o test.bc >> clang -cc1 -triple x86_64-apple-macosx10.13.0 -emit-obj -fembed- >> bitcode=all -x ir test.bc -o test_bc.o >> >> # Extract and disassemble embedded bitcode from both scenarios. >> segedit test_bc...

...it-obj -mrelax-all -disable-free -main-file-name round.c -pic-level 1 -mdisable-fp-elim -masm-verbose -target-cpu yonah -target-linker-version 97.14 -resource-dir /Volumes/MacPro/Projects/OpenSource/llvm/release/Release+Asserts/lib/clang/2.9 -ferror-limit 19 -fmessage-length 180 -stack-protector 1 -fblocks -fdiagnostics-show-option -fcolor-diagnostics -o round.o -x c round.c 1. <eof> parser at end of file 2. Code generation 3. Running pass 'Function Pass Manager' on module 'round.c'. 4. Running pass 'X86 DAG->DAG Instruction Selection' on function '@test' cla...

Hi Jack, Are you packaging all the static libraries that lld produces as part of the package ? PS : When I build on x86_64, I only get a 9M image for lld. Thanks Shankar Easwaran On 11/20/2013 9:15 AM, Jack Howarth wrote: > When lld-3.4 is added to the tools directory of the llvm source tree > as lld, the resulting cmake build produces a huge number of static libs and > bloats

...; 4) Fix some compiler warnings. GCC 4.3.3 seems super strict about %p. > function pointers can't be cast to void * either. > 5) Avoid a warning for apple_versioning.c that "ISO C does not allow empty > files" > > Tested on Ubuntu Linux 9.04 with clang and llvm-gcc and -fblocks to define > and copy some blocks (and invoke them, obviously). Also tested on Mac OS X > 10.6 and linking against -lBlocksRuntime ahead of -lSystem. > > <blocks-linux.diff> > > Shantonu Sen > ssen at apple.com > > Sent from my Mac Pro > > _____________________...

...it-obj -mrelax-all -disable-free -main-file-name round.c -pic-level 1 -mdisable-fp-elim -masm-verbose -target-cpu yonah -target-linker-version 97.14 -resource-dir /Volumes/MacPro/Projects/OpenSource/llvm/release/Release+Asserts/lib/clang/2.9 -ferror-limit 19 -fmessage-length 180 -stack-protector 1 -fblocks -fdiagnostics-show-option -fcolor-diagnostics -o round.o -x c round.c > 1. <eof> parser at end of file > 2. Code generation > 3. Running pass 'Function Pass Manager' on module 'round.c'. > 4. Running pass 'X86 DAG->DAG Instruction Selection' on function...

Hi all, Well! we had a rather fruitful phase 1 testing round. Several issues were addressed. After a bit of a delay, we are ready for phase 2 testing. This phase is to make sure that no patches submitted to fix problems and complete features in phase 1 caused further difficulties. Please download the sources, compile them, and then compile as much as you can with both clang and llvm-gcc.