public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/109183] [regression?] since GCC 11.1, -MM -MMD generates "a-" prefixed dependency files
Date: Thu, 13 Apr 2023 21:05:33 +0000	[thread overview]
Message-ID: <bug-109183-4-eyPYOdik8t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109183-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109183

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|unknown                     |11.1.0

--- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This what the gcc.cc includes:
 %{MD:-MD %{!o:%b.d}%{o*:%.d%*}}\
 %{MMD:-MMD %{!o:%b.d}%{o*:%.d%*}}\


+ %b     substitute the basename for outputs related with the input file
+       being processed.  This is often a substring of the input file name,
+       up to (and not including) the last period but, unless %w is active,
+       it is affected by the directory selected by -save-temps=*, by
+       -dumpdir, and, in case of multiple compilations, even by -dumpbase
+       and -dumpbase-ext and, in case of linking, by the linker output
+       name.  When %w is active, it derives the main output name only from
+       the input file base name; when it is not, it names aux/dump output
+       file.

Anyways this changed with r11-627-g1dedc12d186a11 .

I think it is the correct behavior though.

  parent reply	other threads:[~2023-04-13 21:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 10:36 [Bug preprocessor/109183] New: " yann at droneaud dot fr
2023-03-20  9:19 ` [Bug preprocessor/109183] " rguenth at gcc dot gnu.org
2023-03-21 18:46 ` yann at droneaud dot fr
2023-03-26 19:29 ` aoliva at gcc dot gnu.org
2023-03-27 17:23 ` yann at droneaud dot fr
2023-04-13 16:09 ` allan.w.macdonald at gmail dot com
2023-04-13 16:12 ` allan.w.macdonald at gmail dot com
2023-04-13 16:12 ` pinskia at gcc dot gnu.org
2023-04-13 16:21 ` allan.w.macdonald at gmail dot com
2023-04-13 16:31 ` jakub at gcc dot gnu.org
2023-04-13 16:40 ` schwab@linux-m68k.org
2023-04-13 19:27 ` allan.w.macdonald at gmail dot com
2023-04-13 21:05 ` pinskia at gcc dot gnu.org [this message]
2023-04-14 12:52 ` allan.w.macdonald at gmail dot com
2023-04-14 13:45 ` schwab@linux-m68k.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109183-4-eyPYOdik8t@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).