From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: Reinitialise macro_nest
Date: Thu, 19 Jan 2023 18:40:07 +1030 [thread overview]
Message-ID: <Y8j634999Uh3otCN@squeak.grove.modra.org> (raw)
Another oss-fuzz related patch. Doesn't fix any real bug.
* input-scrub.c (input_scrub_begin): Init macro_nest.
diff --git a/gas/input-scrub.c b/gas/input-scrub.c
index c753243277c..d3da84094ff 100644
--- a/gas/input-scrub.c
+++ b/gas/input-scrub.c
@@ -220,6 +220,7 @@ input_scrub_begin (void)
physical_input_file = NULL; /* No file read yet. */
next_saved_file = NULL; /* At EOF, don't pop to any other file */
+ macro_nest = 0;
input_scrub_reinit ();
do_scrub_begin (flag_m68k_mri);
}
--
Alan Modra
Australia Development Lab, IBM
reply other threads:[~2023-01-19 8:10 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=Y8j634999Uh3otCN@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.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).