Thanks Raphael, so I assume this a 'quirk' ie something that the developer(s) used without considering that there is a well established usage pattern for '.d' files.
On the second thought, I think it is a bug. Even if some targets use .d files to output debug information, under normal situations, they should not touch the file at all when they seem to have nothing to output there. I think it would make sense to change this. But fortunately workaround is simple, just use something else than .d for autogenerated make dependency makefiles. Interestingly and for the record using compiler switch -M prevents the compiler from deleting the .d file, but then again, you cannot use -o option with -M option. br Kusti >>> rnei...@web.de 15.1.2009 10:23 >>> Hi Kusti, > After some tracking it seems that SDCC deletes file 'X.d' if I specify > output file with '-o X.o' > > Is this how it should work? Is this different from gcc? If so is it a > bug or feature? At least some SDCC targets (e.g., pic16) use .d files to output debug information (to debug the compiler). So I guess deleting them when --debug-ralloc is not specified (as well as overwriting them when --debug-ralloc is specified) is a feature. Regards, Raphael ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
