|
From: | David Brown |
Subject: | Re: [avr-gcc-list] binutils 2.22 blow up program size with -flto |
Date: | Tue, 31 Jul 2012 08:30:56 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 |
On 30/07/2012 23:25, Georg-Johann Lay wrote:
David Brown schrieb:What we really need is not an "optimise for size" switch, but an "optimise for the fastest possible code within the specific limit of X KB". Is that on the things-to-do list? :-)Just add it to your GCC todo list and supply a patch ;-)
I've got the plan in place: 1. Enumerate all possible combinations of X KB of code. 2. Filter out those that correctly implement the source code. 3. Sort by speed. 4. Pick the fastest. 5. Output the hex file.The prototype Python code for step 1 is already written, but I'm having trouble testing - I think I need more ram in my PC, and maybe a faster processor...
mvh., David
mvh., David
[Prev in Thread] | Current Thread | [Next in Thread] |