public inbox for binutils-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alan Modra <amodra@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] PR29320, 'struct obstack' declared inside parameter list
Date: Thu,  7 Jul 2022 02:22:38 +0000 (GMT)	[thread overview]
Message-ID: <20220707022238.49AC338582A5@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9b5ebf652b36502ffe79fb196e312bf9ea93f72f

commit 9b5ebf652b36502ffe79fb196e312bf9ea93f72f
Author: Alan Modra <amodra@gmail.com>
Date:   Wed Jul 6 09:20:09 2022 +0930

    PR29320, 'struct obstack' declared inside parameter list
    
            PR 29320
            * frags.h: Move declaration of struct obstack..
            * as.h: ..to here.

Diff:
---
 gas/as.h    | 2 ++
 gas/frags.h | 2 --
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gas/as.h b/gas/as.h
index ec0c12afe23..4fac7d21a32 100644
--- a/gas/as.h
+++ b/gas/as.h
@@ -385,6 +385,8 @@ extern int max_macro_nest;
 /* Verbosity level.  */
 extern int verbose;
 
+struct obstack;
+
 /* Obstack chunk size.  Keep large for efficient space use, make small to
    increase malloc calls for monitoring memory allocation.  */
 extern int chunksize;
diff --git a/gas/frags.h b/gas/frags.h
index 4306c976194..a03f2d1db6d 100644
--- a/gas/frags.h
+++ b/gas/frags.h
@@ -21,8 +21,6 @@
 #ifndef FRAGS_H
 #define FRAGS_H
 
-struct obstack;
-
 /* A code fragment (frag) is some known number of chars, followed by some
    unknown number of chars. Typically the unknown number of chars is an
    instruction address whose size is yet unknown. We always know the greatest


                 reply	other threads:[~2022-07-07  2:22 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=20220707022238.49AC338582A5@sourceware.org \
    --to=amodra@sourceware.org \
    --cc=bfd-cvs@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).