Displaying 3 results from an estimated 3 matches for "caching_disabled".
2015 Jun 30
8
[LLVMdev] C as used/implemented in practice: analysis of responses
...em from themselves, maybe not, but while certainly a side effect of exploiting undefined behavior, this is not really why we exploit undefined behavior. We exploit undefined behavior because it helps to optimize real programs and shrink the size of generated code.
Here's a simple example:
int caching_disabled;
static void do_something(struct cache *c) {
...
if (!caching_disabled) {
...
... c->something ...
...
}
...
}
/* This is only called when caching is disabled */
void foo() {
...
do_something(NULL);
...
}
a compiler might inline the call to do_something, or special...
2015 Jul 01
2
[LLVMdev] C as used/implemented in practice: analysis of responses
...side effect of exploiting undefined behavior, this is
> not really why we exploit undefined behavior. We exploit undefined behavior
> because it helps to optimize real programs and shrink the size of generated
> code.
> >
> > Here's a simple example:
> >
> > int caching_disabled;
> >
> > static void do_something(struct cache *c) {
> > ...
> >
> > if (!caching_disabled) {
> > ...
> > ... c->something ...
> > ...
> > }
> >
> > ...
> > }
> >
> > /* This is only called wh...
2015 Jun 26
3
[LLVMdev] C as used/implemented in practice: analysis of responses
As part of a project to clarify what behaviour of C implementations is
actually relied upon in modern practice, and what behaviour is
guaranteed by current mainstream implementations, we recently
distributed a survey of 15 questions about C, https://goo.gl/AZXH3S.
We were asking what C is in current mainstream practice: the behaviour
that programmers assume they can rely on, the behaviour