[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3
From: |
Boyapati, Anitha |
Subject: |
Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3 |
Date: |
Fri, 14 Oct 2011 13:10:42 +0800 |
>>
>
>I am completely in line with Eric: Your debugger will have to get
smarter
>and
>not the compiler get dumb again.
>
>Johann
As it was put, it is more of a performance question than about the
correctness of it. I am not sure what exactly the issue is, but you are
right that one cannot rely on rcall/ret matching sequences.
At first glance it appeared that the although we are achieving both
performance and size gain using rcall for stack allocation, the code
looked very misleading. Hence I suggested making it optional. On second
thoughts, I am taking it back :)
Anitha
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Boyapati, Anitha, 2011/10/13
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Boyapati, Anitha, 2011/10/13
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Weddington, Eric, 2011/10/13
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Georg-Johann Lay, 2011/10/13
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Weddington, Eric, 2011/10/13
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Georg-Johann Lay, 2011/10/13
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Weddington, Eric, 2011/10/13
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Georg-Johann Lay, 2011/10/13
- Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Weddington, Eric, 2011/10/13
Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3, Boyapati, Anitha, 2011/10/14
Re: [avr-gcc-list] [AVR] RTL prologue/epilogue ver.3,
Boyapati, Anitha <=