On Fri, 1 Oct 1999, Mark Brown wrote:
> On Thu, Sep 30, 1999 at 10:21:29PM -0700, [EMAIL PROTECTED] wrote: > [suggestion to build stock egcs/pgcc in /usr/local] Okay, might do that. > > I recently updated one of my testing machines to Potato, and the patched > > gcc seems to be working fine. Unfortunately, the Potato gcc source package > > requires the Potato debhelper, which won't compile without versioned perl, > > and the slink egcs package doesn't patch with any pgcc patch files. :/ > > You can probably convince it to build without too much hacking at the > dependancies, or you could just upgrade perl (which works now). Or just > carry on using your existing package. So I could upgrade my Slink system to Potato's perl? Or..? I'm semi-clueless on this subject at the moment. Brain fried when my server's power supply and boot/root hard drive burned out. Maybe installing into /usr/local would be the best way to go for slink.. > > And how could I verify that the patched compiler is actually producing > > optimised code? (In my case for AMD K6 with MMX) > > Benchmarking. Even if the compiler thinks it is generating code > optimised for your processor, there's no guarantee that it will > actually run any faster. Oookie. What I had in mind actually was checking the produced executable for MMX instructions. :> I'm not too sure what to look for or how, aside from possibly loading it up in gdb and disassembling.
