<br><br><div class="gmail_quote">On Wed, Apr 22, 2009 at 1:43 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><div style="word-wrap:break-word"><br><div><div>On 22.04.2009, at 22:41, Eliot Miranda wrote:</div><br><blockquote type="cite"><br><br><div class="gmail_quote">On Wed, Apr 22, 2009 at 1:04 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div style="word-wrap:break-word"><br><div><div>On 22.04.2009, at 21:58, Eliot Miranda wrote:</div><blockquote type="cite">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div style="word-wrap:break-word"><div><div><br></div><div> Actually, no. -fno-omit-frame-pointer seems to *force* a frame pointer even on platforms that by default have none ... or is that what you need?</div>
</div></div> </blockquote><div><br></div><div>Right. Somewhere (and I haven't found out where) the autoconf configuration decides to apply -fomit-frame-pointer, which is fine as it generates faster code, etc. </div>
</div></blockquote> <div><br></div><div>platforms/unix/config/acinclude.m4</div><div><br></div><div>If you change any of the autoconf stuff remember to run autoconf to regenerate the configure script.</div><div><br></div>
<blockquote type="cite"> <div class="gmail_quote"><div>But I need (actually, want; I could work around, but shouldn't have to) a frame pointer for one file, and a subsequent -fno-omit-frame-pointer will override a preceeding -fomit-frame-pointer with the compilers I'm aware of.</div>
</div></blockquote><div><br></div><div>Good.</div><br><blockquote type="cite"><div class="gmail_quote"> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><div></div><div><br></div><blockquote type="cite"><div class="gmail_quote"><div> My problem, however, is how to get autoconf to generate a specific compile rule for one file. I can define the alternative COMPILEALT macro but I can't yet figure out how to spit out that rule for a specific source file withoput hacking it at the wrong place. But I'm getting closer :/</div>
</div></blockquote><br></div><div>Assuming you put it in the vm directory, hacking platforms/unix/vm/Makefile.in should do it, no?</div></div></blockquote><div><br></div><div>Thanks for the suggestion! tried it but no. So I think I have to duplicate the ${srcs} collection and processing in mkmf.</div>
<div></div></div></blockquote></div><div><br></div><div>I meant to add a line for your file</div><div><br></div><div>myCogFile$o : myCogFile.c</div><div><span style="white-space:pre">        </span>$(COMPILE) -fomit-frame-pointer $@ myCogFile.c</div>
</div></blockquote><div><br></div><div>Close but because COMPILE ends in "...-c -o" one can't write</div><div> cogit$o : cogit.c</div><div><span style="white-space:pre">        </span>$(COMPILE) -fno-omit-frame-pointer cogit$o $(srcdir)/vm/cogit.c</div>
<div></div></div></blockquote></div><div><br></div><div>how about</div><div><br></div><div><div><div class="gmail_quote"><div> cogit$o : cogit.c</div><div><span style="white-space:pre">        </span>$(COMPILE) cogit$o -fno-omit-frame-pointer $(srcdir)/vm/cogit.c</div>
</div></div></div></div></blockquote><div><br></div><div>Perfect. Thanks.</div></div>