From: Evgeny Karpov <Evgeny.Karpov@microsoft.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "ubizjak@gmail.com" <ubizjak@gmail.com>,
Tobias Burnus <tburnus@baylibre.com>,
Radek Barton <radek.barton@microsoft.com>,
"christophe.lyon@linaro.org" <christophe.lyon@linaro.org>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Subject: [PATCH] i386: Remove declaration of unused functions
Date: Tue, 25 Jun 2024 21:59:35 +0000 [thread overview]
Message-ID: <DBBPR83MB061373831CDD989E7B33AF6FF8D52@DBBPR83MB0613.EURPRD83.prod.outlook.com> (raw)
The patch fixes the issue introduced in
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=63512c72df09b43d56ac7680cdfd57a66d40c636
and reported at
https://gcc.gnu.org/pipermail/gcc-patches/2024-June/655599.html .
Regards,
Evgeny
The patch fixes the issue with compilation on x86_64-gnu-linux
when warnings for unused functions are treated as errors.
gcc/ChangeLog:
* config/i386/i386.cc (legitimize_dllimport_symbol): Remove unused
functions.
(legitimize_pe_coff_extern_decl): Likewise.
---
gcc/config/i386/i386.cc | 2 --
1 file changed, 2 deletions(-)
diff --git a/gcc/config/i386/i386.cc b/gcc/config/i386/i386.cc
index aee88b08ae9..6d6a478f6f5 100644
--- a/gcc/config/i386/i386.cc
+++ b/gcc/config/i386/i386.cc
@@ -104,8 +104,6 @@ along with GCC; see the file COPYING3. If not see
/* This file should be included last. */
#include "target-def.h"
-static rtx legitimize_dllimport_symbol (rtx, bool);
-static rtx legitimize_pe_coff_extern_decl (rtx, bool);
static void ix86_print_operand_address_as (FILE *, rtx, addr_space_t, bool);
static void ix86_emit_restore_reg_using_pop (rtx, bool = false);
--
2.25.1
next reply other threads:[~2024-06-25 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 21:59 Evgeny Karpov [this message]
2024-06-25 23:27 ` Iain Sandoe
2024-06-26 7:40 ` Christophe Lyon
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=DBBPR83MB061373831CDD989E7B33AF6FF8D52@DBBPR83MB0613.EURPRD83.prod.outlook.com \
--to=evgeny.karpov@microsoft.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=radek.barton@microsoft.com \
--cc=tburnus@baylibre.com \
--cc=ubizjak@gmail.com \
/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).