From: Andrew MacLeod <amacleod@redhat.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [COMMITTED] Fix --param=ranger-debug=all to include a trace.
Date: Wed, 3 Nov 2021 10:38:51 -0400 [thread overview]
Message-ID: <909ad085-58e7-e98f-6cca-4b6e610bdfd2@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
Sigh. still didn't get the bitmask right :-P A recent patch made each
of trace/gori/cache their own flag, but didn't adjust the 'all' value to
account that cache no longer included trace.... so all had no trace in
it. fixed thusly.
Bootstrapped on x86_64-pc-linux-gnu with no regressions. Pushed.
Andrew
[-- Attachment #2: 0002-Fix-param-ranger-debug-all-to-include-a-trace.patch --]
[-- Type: text/x-patch, Size: 1008 bytes --]
From 309bb7ff6e2807ecd849c133c3639705f20e5894 Mon Sep 17 00:00:00 2001
From: Andrew MacLeod <amacleod@redhat.com>
Date: Mon, 1 Nov 2021 16:40:45 -0400
Subject: [PATCH 2/6] Fix --param=ranger-debug=all to include a trace.
A recent change made each debug flag its own value, but the 'all' value was
not adjusted properly and 'trace' was left out.
* flag-types.h (RANGER_DEBUG_ALL): Fix values.
---
gcc/flag-types.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gcc/flag-types.h b/gcc/flag-types.h
index 7cf8c28933b..459e3e07016 100644
--- a/gcc/flag-types.h
+++ b/gcc/flag-types.h
@@ -458,7 +458,8 @@ enum ranger_debug
RANGER_DEBUG_GORI = 4,
RANGER_DEBUG_TRACE_GORI = (RANGER_DEBUG_TRACE | RANGER_DEBUG_GORI),
RANGER_DEBUG_TRACE_CACHE = (RANGER_DEBUG_TRACE | RANGER_DEBUG_CACHE),
- RANGER_DEBUG_ALL = (RANGER_DEBUG_GORI | RANGER_DEBUG_CACHE)
+ RANGER_DEBUG_ALL = (RANGER_DEBUG_GORI | RANGER_DEBUG_CACHE
+ | RANGER_DEBUG_TRACE)
};
/* EVRP mode. */
--
2.17.2
reply other threads:[~2021-11-03 14:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=909ad085-58e7-e98f-6cca-4b6e610bdfd2@redhat.com \
--to=amacleod@redhat.com \
--cc=gcc-patches@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).