On Mon, Apr 08, 2013 at 09:20:11AM +0200, Samuel Thibault wrote:
> Ah, right. Indeed in some cases it could make a difference in some rare
> loop cases if the compiler has to spill, but with nowadays' L1 speed,
> that probably doesn't matter so much.
It's not that rare, but debugging should curren
Thomas Schwinge, le Mon 08 Apr 2013 08:26:06 +0200, a écrit :
> On Mon, 8 Apr 2013 00:13:16 +0200, Samuel Thibault
> wrote:
> > Thomas Schwinge, le Mon 08 Apr 2013 00:06:23 +0200, a écrit :
> > > On Sun, 7 Apr 2013 21:10:09 +0200, Samuel Thibault
> > > wrote:
> > > > In the Debian package, when
Hi!
On Mon, 8 Apr 2013 00:13:16 +0200, Samuel Thibault
wrote:
> Thomas Schwinge, le Mon 08 Apr 2013 00:06:23 +0200, a écrit :
> > On Sun, 7 Apr 2013 21:10:09 +0200, Samuel Thibault
> > wrote:
> > > In the Debian package, when building the kdb-enabled kernel,
> > > we pass -fno-omit-frame-point
Thomas Schwinge, le Mon 08 Apr 2013 00:06:23 +0200, a écrit :
> On Sun, 7 Apr 2013 21:10:09 +0200, Samuel Thibault
> wrote:
> > In the Debian package, when building the kdb-enabled kernel,
> > we pass -fno-omit-frame-pointer in CFLAGS, and I'll push
> > -fno-optimize-sibling-calls too. Both of th
Hi!
On Sun, 7 Apr 2013 21:10:09 +0200, Samuel Thibault
wrote:
> In the Debian package, when building the kdb-enabled kernel,
> we pass -fno-omit-frame-pointer in CFLAGS, and I'll push
> -fno-optimize-sibling-calls too. Both of them permit to get useful call
> traces in kdb. They should rather be
Hello,
In the Debian package, when building the kdb-enabled kernel,
we pass -fno-omit-frame-pointer in CFLAGS, and I'll push
-fno-optimize-sibling-calls too. Both of them permit to get useful call
traces in kdb. They should rather be included in the upstream
configfrag.ac, don't they?
Samuel
