search for: do_print

...solution to my problem (if it has one) in the mailing list or the source code. The problem is: how can I redefine a function that's been called already by some other function? Suppose I have 3 files, all compiled to bytecode through llvm-gcc (I think it could be clang instead). File1.c: void do_print() { print(); } File2.c: void print() { printf("File2.c\n"); } File3.c: void print() { printf("File3.c\n"); } Then, I have the main file compiled to executable like this: int main() { // initialize and get context (not shown) Module *file1(LoadFile("file1.bc",Con...

...r the source code. The problem is: how can I redefine a > function that's been called already by some other function? why do you want to do this? > Suppose I have 3 files, all compiled to bytecode through llvm-gcc (I > think it could be clang instead). > > File1.c: > void do_print() { print(); } > > File2.c: > void print() { printf("File2.c\n"); } > > File3.c: > void print() { printf("File3.c\n"); } The solution in C is to give the version in File2 a weak linkage type, for example using gcc's "weak" attribute. You then...

...'t be stopped or the cost being stoped is prohibitive. If I find a better way to run an algorithm, I'd like to update the running program non-stopping. Suppose I have 3 files, all compiled to bytecode through llvm-gcc (I think > it could be clang instead). > > File1.c: > void do_print() { print(); } > > File2.c: > void print() { printf("File2.c\n"); } > > File3.c: > void print() { printf("File3.c\n"); } > The solution in C is to give the version in File2 a weak linkage type, > for example using gcc's "weak" attribute. Y...

...mestamps ) return; @@ -524,12 +567,11 @@ static void printk_start_of_line(void) __putstr(tstr); } -void printk(const char *fmt, ...) +static void vprintk_common(const char *prefix, const char *fmt, va_list args) { static char buf[1024]; static int start_of_line = 1, do_print; - va_list args; char *p, *q; unsigned long flags; @@ -537,9 +579,7 @@ void printk(const char *fmt, ...) local_irq_save(flags); spin_lock_recursive(&console_lock); - va_start(args, fmt); (void)vsnprintf(buf, sizeof(buf), fmt, args); - va_end...

This is the next patch series for scrub userland tools. Change log v1->v2: - commands now reachable as "btrfs scrub ..." instead of "btrfs filesystem scrub ..." - ability to scrub a single device instead of a whole file system - superfluous command line options removed - resume is now a separate command ("scrub resume") instead of "scrub start -r" -

...helming in a big project, I think. > > Just for the record, if the function code isn't freed with > freeMachineCodeForFunction, I get a segmentation fault during > recompileAndRelinkFunction with this stack dump: > Running pass 'X86 Machine Code Emitter' on function '@do_print' Well, it's not supposed to segfault. At worst, it should give you an assertion error when you do something wrong (when it's compiled with asserts, of course). Could you either file a bug, or send me the exact code you were using with the command line you used to compile it against svn...

...#39;s a little too overwhelming in a big project, I think. Just for the record, if the function code isn't freed with freeMachineCodeForFunction, I get a segmentation fault during recompileAndRelinkFunction with this stack dump: Running pass 'X86 Machine Code Emitter' on function '@do_print' I know no one should do this, but it's good to know LLVM doesn't allow you to leak (or it's just a good side effect of something else). Although this method can stop the whole program for quite some time, it doesn't require reboot (which can be costy) and doesn't have the...

...mestamps ) return; @@ -524,12 +567,11 @@ static void printk_start_of_line(void) __putstr(tstr); } -void printk(const char *fmt, ...) +static void vprintk_common(const char *prefix, const char *fmt, va_list args) { static char buf[1024]; static int start_of_line = 1, do_print; - va_list args; char *p, *q; unsigned long flags; @@ -537,9 +579,7 @@ void printk(const char *fmt, ...) local_irq_save(flags); spin_lock_recursive(&console_lock); - va_start(args, fmt); (void)vsnprintf(buf, sizeof(buf), fmt, args); - va_end...

...t; think. > > > > Just for the record, if the function code isn't freed with > > freeMachineCodeForFunction, I get a segmentation fault during > > recompileAndRelinkFunction with this stack dump: > > Running pass 'X86 Machine Code Emitter' on function '@do_print' > > Well, it's not supposed to segfault. At worst, it should give you an > assertion error when you do something wrong (when it's compiled with > asserts, of course). Could you either file a bug, or send me the exact > code you were using with the command line you used t...

...ject, I think. >> >> Just for the record, if the function code isn't freed with >> freeMachineCodeForFunction, I get a segmentation fault during >> recompileAndRelinkFunction with this stack dump: >> Running pass 'X86 Machine Code Emitter' on function '@do_print' > > Well, it's not supposed to segfault. At worst, it should give you an > assertion error when you do something wrong (when it's compiled with > asserts, of course). Could you either file a bug, or send me the exact > code you were using with the command line you used t...

I was trying to install software named ncview on a centos 5.3 box. ./configure command gave this error: Error, the X libraries and development headers must be installed for ncview to work! I was surprised that there were many google hits related to ubuntu, none for centos. So even though I eventually figured out what to do, I decided to share this with the list anyhow, so maybe next time I

On Sat, Jan 30, 2010 at 6:22 PM, Conrado Miranda <miranda.conrado at gmail.com> wrote: > Albert Graef wrote: >> >> The way I do this in Pure is to always call global functions in an >> indirect fashion, using an internal global variable which holds the >> current function pointer. When a function definition gets updated, the >> Pure interpreter just jits the

Albert Graef wrote: > The way I do this in Pure is to always call global functions in an > indirect fashion, using an internal global variable which holds the > current function pointer. When a function definition gets updated, the > Pure interpreter just jits the new function, changes the global variable > accordingly, and frees the old code. > > Compared to Duncan's

...rc/cmd/lp/cmd/adaptor/cancel_job.c update: usr/src/cmd/lp/cmd/adaptor/misc.c update: usr/src/cmd/lp/cmd/adaptor/misc.h update: usr/src/cmd/lp/cmd/adaptor/show_queue.c update: usr/src/cmd/lp/cmd/adaptor/submit_job.c update: usr/src/cmd/lp/cmd/lpadmin/Makefile update: usr/src/cmd/lp/cmd/lpadmin/do_printer.c update: usr/src/cmd/lp/cmd/lpadmin/lpadmin.c update: usr/src/cmd/lp/cmd/lpadmin/lpadmin.h update: usr/src/cmd/lp/cmd/lpadmin/rmdest.c update: usr/src/cmd/lp/cmd/lpc/process.c update: usr/src/cmd/lp/cmd/lpc/topq.c update: usr/src/cmd/lp/cmd/lpsched/Makefile update: usr/src/cmd/lp/cmd/lpsc...