Apple GCC pathologically slow

[dave@…]

• Install openssh with macports
• time an scp some large-ish directory from a remote host
• launch a linux VM on the same hardware
• time the same scp
• compare

My results: openssh on the Mac is roughly half the speed of openssh on Linux. Now:

• install gcc43 and gcc_select with macports
• gcc_select mp-gcc43
• port upgrade -f openssh
• run the timing test again

My results: timing approximately identical to Linux.

My conclusions: When MacPorts is installed, it should force-install and use a stock gcc. Failing that, all the installation guides should be updated to note that you might want to do that before installing anything else.

[dave@…]

Sorry, title should've been "Apple GCC generates slow code"

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Cc Me!

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

If they are working correctly, ports do not start using a different compiler just because gcc_select has been changed.
If you use the debug option (port -df upgrade openssh) you should be able to see which compiler is being used.
Did you do something special to force the the gcc_select compiler to be used?
If not, then I am not sure the results say anything about the Apple GCC.

[dave@…]

Gah! You're right! No, it's not choosing the gcc_select compiler. I'm once again at a total loss to explain the discrepancy I've seen.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

This is puzzling.
Since this might not be a MacPorts problem, I will close this ticket for now.

If it turns out it is a MacPorts problem, we can reopen.

[(none)]

Milestone Port Bugs deleted