3 captures
15 Nov 2014 - 20 Jan 2024
Oct NOV Dec
15
2013 2014 2015
success
fail

About this capture

COLLECTED BY

Organization: Internet Archive

The Internet Archive discovers and captures web pages through many different web crawls. At any given time several distinct crawls are running, some for months, and some every day or longer. View the web archive through the Wayback Machine.

Collection: Wide Crawl started June 2014

Web wide crawl with initial seedlist and crawler configuration from June 2014.
TIMESTAMPS

The Wayback Machine - http://web.archive.org/web/20141115153557/http://lwn.net/Articles/552953/
 
LWN.net Logo

Log in now

Create an account

Subscribe to LWN

LWN.net Weekly Edition for November 13, 2014

High-DPI displays and Linux

LWN.net Weekly Edition for November 6, 2014

A control group manager

Kdbus meets linux-kernel

Pondering the X client vulnerabilities

Pondering the X client vulnerabilities

Posted Jun 5, 2013 11:03 UTC (Wed) by epa (subscriber, #39769)
In reply to: Pondering the X client vulnerabilities by hummassa
Parent article: Pondering the X client vulnerabilities

I'm not going to pretend that because computers are faster, there is no longer performance-critical code. (Even though it is worth bearing in mind that today's mobile platforms or ARM-based servers are still far more powerful than the high-end workstations for which X was written.) My point is that some code is performance-critical, but not *all of it*. The 80-20 rule applies - actually more like 99-1, where a small part of the code is the inner loop where micro-optimizations like skipping bounds checking make a difference.

By all means profile the code, find the hot sections, and after careful review turn off safety for those. That does not justify running without bounds checking or overflow checking for the rest of the code.


(Log in to post comments)


Copyright © 2014, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds