public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Macleod <amacleod@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-4664] Tweak ranger-debug flags. Date: Mon, 25 Oct 2021 14:44:32 +0000 (GMT) [thread overview] Message-ID: <20211025144432.5B8BC3858C27@sourceware.org> (raw) https://gcc.gnu.org/g:2bfb21bb8ce16698926576870e4b1f2609e0c909 commit r12-4664-g2bfb21bb8ce16698926576870e4b1f2609e0c909 Author: Andrew MacLeod <amacleod@redhat.com> Date: Thu Oct 21 10:58:16 2021 -0400 Tweak ranger-debug flags. Set the 3 possible flags as all individual bits and group for options. * flag-types.h (enum ranger_debug): Adjust values. * params.opt (ranger_debug): Ditto. Diff: --- gcc/flag-types.h | 3 ++- gcc/params.opt | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/gcc/flag-types.h b/gcc/flag-types.h index a5a637160d7..7cf8c28933b 100644 --- a/gcc/flag-types.h +++ b/gcc/flag-types.h @@ -454,9 +454,10 @@ enum ranger_debug { RANGER_DEBUG_NONE = 0, RANGER_DEBUG_TRACE = 1, - RANGER_DEBUG_CACHE = (2 | RANGER_DEBUG_TRACE), + RANGER_DEBUG_CACHE = 2, 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) }; diff --git a/gcc/params.opt b/gcc/params.opt index 393d52bc660..6eb3e15a9e6 100644 --- a/gcc/params.opt +++ b/gcc/params.opt @@ -887,7 +887,7 @@ EnumValue Enum(ranger_debug) String(trace) Value(RANGER_DEBUG_TRACE) EnumValue -Enum(ranger_debug) String(cache) Value(RANGER_DEBUG_CACHE) +Enum(ranger_debug) String(cache) Value(RANGER_DEBUG_TRACE_CACHE) EnumValue Enum(ranger_debug) String(gori) Value(RANGER_DEBUG_GORI)
reply other threads:[~2021-10-25 14:44 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=20211025144432.5B8BC3858C27@sourceware.org \ --to=amacleod@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).