Re: heap corruption in du

[Stepan Kasal]

Ahoj Mikulasi,

On Mon, Oct 24, 2005 at 04:01:09PM +0200, Mikulas Patocka wrote:
> >>You can modify libtool so that when it is creating static library and
> >>compiler is "icc" or "icpc" (or "some/path/icc" or "some/path/icpc"),
> >>it passes it -no-ipo switch. (dynamic libraries work fine with -ipo).
... 
> If you want to solve it in some way (detect intel compiler and pass it 
> -no-ipo when creating object files that will be packed into "*.a"), you 
> can, if you don't want, you don't have to.

do I understand correctly that you propose that ./configure will modify
CC if it matches certain pattern?

I'm afraid that that might induce some grievance; I, personally, don't like
if the program thinks it knows better that I.  I suppose you the feeling.

What if next version of the compiler will fix the issue, in a totally
transparent way?  People would complain that we slow down their programs
by switching off ipo.  And the nature of Autoconf mean that this bug will
live in many tarballs long after it is fixed in Autoconf.

But I can imagine that Autoconf would issue a warning, saying that if the
project doesn't build, you might try to add -ipo-obj or -no-ipo to cc.
But I'm afraid that there is no easy way to determine whether the project
builds a *.a library.

Or it could be made as a patch for Automake, so that the warning is issued
only if Automake sees a static library...

Mikulas, do you volunteer to write a patch?

Thank you very much for reporting this problems, but I currently see no
easy way to store the knowledge into Autotools.  (And I'm afraid no one
is willing to follow the more laborous path...)  So we end up hoping that
other users of Intel compiler will find this thread in the archives...

Have a nice day,
        Stepan