search for: _pragma

...propagate this information. > The Microsoft implementation is scary. I'd be much happier with __assume if it caused a syntax error in the misprint example given. One generalization I would like to see (perhaps after spending enough time to understand how to safely inject attributes or _Pragma via macros) is how to make an assert generate syntax errors when it is provably violated even in release mode. This gets even better if you control the intermediate format and can store the flow-of-control syntax error conditions with the bytecode representation of the function. (Am I misread...

On Oct 22, 2008, at 5:47 PM, Kenneth Boyd wrote: > One generalization I would like to see (perhaps after spending enough > time to understand how to safely inject attributes or _Pragma via > macros) is how to make an assert generate syntax errors when it is > provably violated even in release mode. I like this idea. Sounds good. One can imagine enrolling static analysis and automated theorem provers to help out on the harder problems. :-) > (Am I misreading C99/...

On Oct 22, 2008, at 3:28 PM, Paul Biggar wrote: > As part of our PHP compiler (phpcompiler.org), it would be great to be > able to annotate our generated C code with, for example, (var != > NULL), or (var->type == STRING), and have that information passed > around (esp interprocedurally at link-time) by the LLVM optimizers. For some odd reason I was thinking this was going to be

...d-2 h323]# make clean install rm -f *.o *.so core.* cc -g -pg -c -o chan_h323.o -pipe -Wall -fPIC -Wmissing-prototypes -Wmissing-declarations - DP_LINUX -D_REENTRANT -D_GNU_SOURCE -march=i686 -DPBYTE_ORDER=PLITTLE_ENDIA N -DP_HAS_SEMAPHORES -DP_SSL -DP_PTHREADS -DPHAS_TEMPLATES -DPTRACING -DP_US E_PRAGMA -I/root/pwlib/include/ptlib/unix -I/root/pwlib/include -I/root/op enh323/include -Wno-missing-prototypes -Wno-missing-declarations chan_h323.c g++ -g -pg -c -o ast_h323.o -pipe -Wall -fPIC -Wmissing-prototypes -Wmissing-declarations -D P_LINUX -D_REENTRANT -D_GNU_SOURCE -march=i686 -DPBYTE_ORDE...

...fork was based on older GRTE which had unfinished patches to support Clang), though I > haven't had the time to look at that recently. > > I should add a huge disclaimer: this won't be easy and requires understanding the macro hell in glibc, GRTE relies on > some hacky uses of `_Pragma` to supplement for some macros otherwise not possible with Clang. Even if you do get it to > build I think it may be a waste of time to try and just implement the missing symbols in your case (or figure out why > they're not being exported). > > Thanks. > > On 22/12/2018 09:...

To whom it may concern, Is there a way to build glibc with clang/llvm? I’m working on enabling llvm-cov for my compiler which is a totally new arch with a libc.a built from newlib. I successfully built compiler-rt but when I typed the command ` clang++ --target=xxx -fprofile-instr-generate -fcoverage-mapping foo.cc -o foo`, the linker failed because of undefined reference to

Hi, I'm interested in whether or not there is a way of providing source-level annotations to help LLVM with optimizations, similar to VisualC++'s __assume facility (http://msdn.microsoft.com/en-us/library/1b3fsfxw.aspx). As part of our PHP compiler (phpcompiler.org), it would be great to be able to annotate our generated C code with, for example, (var != NULL), or (var->type ==