[llvm-commits] [llvm] r117667 - in /llvm/trunk: include/llvm/ include/llvm/CodeGen/ include/llvm/Target/ lib/CodeGen/ lib/CodeGen/SelectionDAG/ lib/Target/ARM/ lib/Target/Alpha/ lib/Target/Blackfin/ lib/Target/CBackend/ lib/Target/CellSPU/ lib/Ta
nlewycky at google.com
Fri Oct 29 16:08:14 PDT 2010
On 29 October 2010 15:47, John Thompson
<john.thompson.jtsoftware at gmail.com>wrote:
> If stack space is of concern, I think it would be safer to go back to
> vector. Using vector will mean more heap allocations, but the overall
> memory usage would probably be less.
> How do you measure the stack space (i.e. is there a simple way besides
> inspection in the debugger)? I'd like to measure both.
gcc -Wframe-larger-than=16384 will warn of functions using more than 16k of
stack space, on gcc 4.4.
> On Fri, Oct 29, 2010 at 2:22 PM, Dale Johannesen <dalej at apple.com> wrote:
>> Interesting. It's true very small sizes are most common for these
>> vectors, but I wouldn't have expected the overhead to be that significant.
>> Perhaps try lowering all the fixed allocations to 4?
>> On Oct 29, 2010, at 2:10 PMPDT, Nick Lewycky wrote:
>> On 29 October 2010 10:29, John Thompson <
>> John.Thompson.JTSoftware at gmail.com> wrote:
>>> Author: jtsoftware
>>> Date: Fri Oct 29 12:29:13 2010
>>> New Revision: 117667
>>> URL: http://llvm.org/viewvc/llvm-project?rev=117667&view=rev
>>> Inline asm multiple alternative constraints development phase 2 -
>>> improved basic logic, added initial platform support.
>> This change makes SelectionDAGBuilder::visitInlineAsm use up 30k of stack
>> space, largely due to the switch from std::vector to SmallVector. Please
> John Thompson
> John.Thompson.JTSoftware at gmail.com
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-commits