search for: hamstringing

...an omitted statement involving a normal variable, I'd guess you're missing a volatile qualifier. I'm not 100% sure volatile is a valid qualifier for functions, but try it. Well, yes, if I change the signature to: void test(char * volatile x) It works, but that's because I'm hamstringing the optimizers. I don't really see how that has anything to do with the question, though. If I change the signature to: void test(int x) It works too... what's special about 'char *'? > If RTOS stands for real time OS, then reading up on volatile would be a really go...

If this were a problem with an omitted statement involving a normal variable, I'd guess you're missing a volatile qualifier. I'm not 100% sure volatile is a valid qualifier for functions, but try it. If RTOS stands for real time OS, then reading up on volatile would be a really good idea. P.S. Sorry Carl, you're going to receive this twice. I forget to CC the list. --------------

...tted statement involving a normal variable, I'd guess you're missing a volatile qualifier. I'm not 100% sure volatile is a valid qualifier for functions, but try it. Well, yes, if I change the signature to: void test(char * volatile x) It works, but that's because I'm hamstringing the optimizers. I don't really see how that has anything to do with the question, though. If I change the signature to: void test(int x) It works too... what's special about 'char *'? > If RTOS stands for real time OS, then reading up on volatile would be a really go...

I've been chasing down a bug for a few days in some RTOS code I'm building with clang. In the end it comes down to this code: void external(void); void test(char *x) { x--; if (!x) { external(); } } When compiled for ARM with TOT clang (r183249) at -O1 or greater, no calls to 'external()' appear in the output code at all. I have an example

All, With the pending reorganization of the software, I have some questions about how developers set their PATH and LD_LIBRARY_PATH variables when working with LLVM. This is a bit long winded, but bear with me. We're planning to break the "llvm" module up into three modules: * support - lib/Support, lib/System, autoconf, make support, utilities * core - VMCore,