* Akim Demaille wrote on Thu, Jun 26, 2003 at 02:47:24PM CEST: > > On Thu, Jun 26, 2003 at 11:23:04AM +0200, Ralf Wildenhues wrote: > >> Intel compiler icc version 7.1 handles the -MF option inconsistently. > > [...] > >> Subsequently, the depcomp 'icc' mode will not be detected correctly > >> during the ./configure run, since it uses '-MD -MF'. > > > This sucks. If -MF cannot work with -MD, depcomp will have to call icc > > twice: one time to get dependency information, and another time to do > > the actual compilation. This will be slower.
ACK. > > Or we could use -MD alone, but as ICC does respect subdirectories (at > > least with ICC 7.0, compiling foo/bar.c with -MD would create ./bar.d > > instead of foo/bar.d -- could you check this with 7.1?) we'd need to > > implement some locking scheme in depcomp so that compiling foo/bar.c > > and baz/bar.c in parallel do not write the same bar.d. Just so I don't misunderstand you: | $ ls -R | .: | foo | | ./foo: | bar.c bar.h | $ icc -MD -c foo/bar.c ; ls -R | .: | bar.d bar.o foo | | ./foo: | bar.c bar.h | $ more bar.d | bar.o: foo/bar.c /usr/include/assert.h /usr/include/features.h \ | [...] | foo/bar.h Similar behaviour with -MMD. > >> Any suggestions? > > Complain to Intel, if not already done. Will do so and report back for news. Could take some time, though. > Err, maybe my message went unnoticed, but you might find additional > information here too. All but the last of your messages (which I read after sending mine) looked to me like they are different issues. Regards, Ralf
