From: Jeff Law <jeffreyalaw@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [committed] Fix build of libgcc on ports using FDPIC
Date: Sat, 2 Dec 2023 22:47:30 -0700 [thread overview]
Message-ID: <66ce7b3d-607f-48b5-b3f7-562f4ec5a535@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 243 bytes --]
read_encoded_value_with_base has an ifdef'd code path conditional on
__FDPIC__ which was calling _Unwind_gnu_Find_got without a prototype.
This naturally caused various build failures.
This adds a suitable prototype.
Pushed to the trunk.
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 1065 bytes --]
commit 4cef6daf40f4aefd748245a720955d4e52d1a81e
Author: Jeff Law <jlaw@ventanamicro.com>
Date: Sat Dec 2 22:45:48 2023 -0700
[committed] Fix build of libgcc on ports using FDPIC
read_encoded_value_with_base has an ifdef'd code path conditional on __FDPIC__
which was calling _Unwind_gnu_Find_got without a prototype. This naturally
caused various build failures.
This adds a suitable prototype.
Pushed to the trunk.
libgcc
* unwind-pe.h (_Unwind_gnu_Find_got): Add prototype.
diff --git a/libgcc/unwind-pe.h b/libgcc/unwind-pe.h
index 3f98c93589a..d714a27a935 100644
--- a/libgcc/unwind-pe.h
+++ b/libgcc/unwind-pe.h
@@ -173,6 +173,8 @@ read_sleb128 (const unsigned char *p, _sleb128_t *val)
return p;
}
+extern _Unwind_Ptr _Unwind_gnu_Find_got (_Unwind_Ptr);
+
/* Load an encoded value from memory at P. The value is returned in VAL;
The function returns P incremented past the value. BASE is as given
by base_of_encoded_value for this encoding in the appropriate context. */
reply other threads:[~2023-12-03 5:47 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=66ce7b3d-607f-48b5-b3f7-562f4ec5a535@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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: 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).