search for: tradoff

> I fully agree with Steve here, and dislike developers' attitude of "We > know what's good for you, and since you don't/can't have a clue - we > won't trust you with decisions". Well, I'm on the developers' side. They need to produce a product that _now_ gets installed in some embedded device and is expected to be still secure in 15 years and longer

...ed of course. The natural conclusion of the "I'm the parent trying to protect you from bad decisions" idea is that everyone else is a child. There's plenty of people that can understand exactly the risks they're taking with smaller key sizes, and are still willing to make the tradoff. > Still, recompilation has a too variable cost (in the dependencies) - > it's hard to be sure that you _only_ changed that one constant and > didn't forget something that ./configure would have found etc. > > >> There's no way the developers can know >> or...

...nsform I'm suggesting here. This is probably a lack of awareness on my part, not a lack of literature though. While I have some basic background in the area, I can't claim to have made an extensive study of loop optimization techniques. *Particularly* profile guided ones. w.r.t. the tradoffs in practice, I'm going to answer this in a separate response just to keep this one short. I've been playing with both approaches and there appears to be appeal in both. I'm currently leaning towards a mixture of both approaches. > > Some of your points I have quick feedback...

I've been playing with approaches to getting better optimization of loops which contain infrequently executed slow paths. I've gotten as far as throwing together a proof of concept implementation of a profile guided optimization to separate a single loop with multiple latches into a loop nest, but I want to get feedback from interested parties before investing much more effort. The