https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #14 from Andreas Schwab ---
It doesn't make sense to use both -MM and -MD. Either you want to generate
only dependencies, then use -M or -MM (and -MF to redirect to a file). Or you
want to generate dependencies as side effect of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #13 from Allan W. Macdonald ---
Ahhh, so, "to get back the old behaviour" (as @ Richard Biener put it), this
seems to work (at least with my project):
%.d: %.c
gcc -MM -MD -dumpbase '' $<
Not obvious in the gcc 11.3.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
Andrew Pinski changed:
What|Removed |Added
Version|unknown |11.1.0
--- Comment #12 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #11 from Allan W. Macdonald ---
The makefiles I've been maintaining contain a mechanism to make sure that any
change in a locally-included file will cause the c file that includes it to be
compiled again, like so:
### Extract of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #10 from Andreas Schwab ---
If you want to generate only dependencies, use -M or -MM. -MD and -MMD are
primarily used to generate dependencies as side effect of compilation.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #8 from Allan W. Macdonald ---
(In reply to Andrew Pinski from comment #7)
> Does using -c instead help?
Why would we want to compile the file without FIRST checking for dependencies?
The .d file needs to be up to date so that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #7 from Andrew Pinski ---
Does using -c instead help?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #6 from Allan W. Macdonald ---
(In reply to Allan W. Macdonald from comment #5)
> Here is a workaround:
or just
gcc -E -MMD test.c > /dev/null
if gcc-11 is default gcc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
Allan W. Macdonald changed:
What|Removed |Added
CC||allan.w.macdonald at gmail dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #4 from Yann Droneaud ---
(In reply to Alexandre Oliva from comment #3)
> dump files now consistently take the base name from the output name, when
> not overridden
>
> since in this case gcc is called for (compiling and) linking,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
--- Comment #3 from Alexandre Oliva ---
dump files now consistently take the base name from the output name, when not
overridden
since in this case gcc is called for (compiling and) linking, and the final
output name is a.* (.out or .exe,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
Yann Droneaud changed:
What|Removed |Added
CC||yann at droneaud dot fr
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183
Richard Biener changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org
--- Comment
14 matches
Mail list logo
