Messages in this thread | | | Subject | Re: Why is the kfree() argument const? | From | Zan Lynx <> | Date | Fri, 18 Jan 2008 12:31:05 -0700 |
| |
On Fri, 2008-01-18 at 11:14 -0800, Vadim Lobanov wrote: [cut] > Second, even if const did have stronger semantics that forbade the value of x > from being modified during execution of foo, the compiler still could not > reorder the two function calls, before it cannot assume that the two > functions (in their internal implementations) do not touch some other, > unknown to this code, global variable.
This is why GCC has the pure and const function attributes. These attributes are more powerful than the "const" keyword, and do allow optimizations with assumptions about global state. -- Zan Lynx <zlynx@acm.org> [unhandled content-type:application/pgp-signature]
| |