From: Louis Krupp <louis.krupp@zoho.com>
To: "gcc-patches" <gcc-patches@gcc.gnu.org>
Subject: gcc build problem (i386.c) -- missing declaration
Date: Thu, 22 Sep 2016 23:41:00 -0000 [thread overview]
Message-ID: <15754196d7b.ee211d9511911.500849851081562859@zoho.com> (raw)
As of revision 240383 , i386.c isn't compiling. The errors are:
In file included from ../../gcc_trunk/gcc/target-def.h:106:0,
from ../../gcc_trunk/gcc/config/i386/i386.c:81:
./target-hooks-def.h:92:38: error: ‘hook_uint_uintp_false’ was not declared in this scope
#define TARGET_ASM_ELF_FLAGS_NUMERIC hook_uint_uintp_false
^
./target-hooks-def.h:2205:5: note: in expansion of macro ‘TARGET_ASM_ELF_FLAGS_NUMERIC’
TARGET_ASM_ELF_FLAGS_NUMERIC, \
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
./target-hooks-def.h:1792:5: note: in expansion of macro ‘TARGET_ASM_OUT’
TARGET_ASM_OUT, \
^~~~~~~~~~~~~~
../../gcc_trunk/gcc/config/i386/i386.c:50811:29: note: in expansion of macro ‘TARGET_INITIALIZER’
struct gcc_target targetm = TARGET_INITIALIZER;
The problem seems to be that hook_uint_uintp_false() was added to hooks.c but not to hooks.h. I have things working on my copy with this change:
--- hooks.h (revision 240383)
+++ hooks.h (working copy)
@@ -95,6 +95,7 @@ extern tree hook_tree_tree_int_treep_bool_null (tr
extern unsigned hook_uint_void_0 (void);
extern unsigned int hook_uint_mode_0 (machine_mode);
+extern bool hook_uint_uintp_false (unsigned int, unsigned int *);
extern bool default_can_output_mi_thunk_no_vcall (const_tree, HOST_WIDE_INT,
HOST_WIDE_INT, const_tree);
If I'm not missing something, and if this is a genuine build problem, and if this change looks good, I can commit it unless someone else is in the process of doing that. I just need someone's approval. (I should add that I'm on the Fortran commit-after-approval list, but I'm not on a general gcc list as far as I know.)
Louis Krupp
next reply other threads:[~2016-09-22 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 23:41 Louis Krupp [this message]
2016-09-23 5:27 ` Anton Blanchard
2016-09-29 18:44 ` Jeff Law
2016-09-29 18:46 ` Louis Krupp
2016-10-03 12:15 ` Gerald Pfeifer
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=15754196d7b.ee211d9511911.500849851081562859@zoho.com \
--to=louis.krupp@zoho.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).