public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-4249] opts: include missing header files. Date: Fri, 8 Oct 2021 11:46:16 +0000 (GMT) [thread overview] Message-ID: <20211008114616.A12E73857815@sourceware.org> (raw) https://gcc.gnu.org/g:816da497dfba541aabdbe08a03e6e9988a7d9573 commit r12-4249-g816da497dfba541aabdbe08a03e6e9988a7d9573 Author: Martin Liska <mliska@suse.cz> Date: Fri Oct 8 13:45:18 2021 +0200 opts: include missing header files. gcc/objc/ChangeLog: * objc-next-runtime-abi-01.c: Add missing include. * objc-next-runtime-abi-02.c: Likewise. Diff: --- gcc/objc/objc-next-runtime-abi-01.c | 1 + gcc/objc/objc-next-runtime-abi-02.c | 1 + 2 files changed, 2 insertions(+) diff --git a/gcc/objc/objc-next-runtime-abi-01.c b/gcc/objc/objc-next-runtime-abi-01.c index 17c86189923..12f8bdc0b9c 100644 --- a/gcc/objc/objc-next-runtime-abi-01.c +++ b/gcc/objc/objc-next-runtime-abi-01.c @@ -39,6 +39,7 @@ along with GCC; see the file COPYING3. If not see #include "langhooks.h" #include "c-family/c-objc.h" #include "objc-act.h" +#include "opts.h" /* When building Objective-C++, we are not linking against the C front-end and so need to replicate the C tree-construction diff --git a/gcc/objc/objc-next-runtime-abi-02.c b/gcc/objc/objc-next-runtime-abi-02.c index 677b75f0334..7ca0fd7cf00 100644 --- a/gcc/objc/objc-next-runtime-abi-02.c +++ b/gcc/objc/objc-next-runtime-abi-02.c @@ -51,6 +51,7 @@ along with GCC; see the file COPYING3. If not see #include "target.h" #include "tree-iterator.h" +#include "opts.h" #include "objc-runtime-hooks.h" #include "objc-runtime-shared-support.h"
reply other threads:[~2021-10-08 11:46 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=20211008114616.A12E73857815@sourceware.org \ --to=marxin@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).