From: Paolo Carlini <paolo.carlini@oracle.com>
To: "Andre Vieira (lists)" <Andre.SimoesDiasVieira@arm.com>,
"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCHv3][ARM] -mpure-code option for ARM
Date: Thu, 22 Sep 2016 20:20:00 -0000 [thread overview]
Message-ID: <939c9bac-b006-8833-a73b-24aa8b0329b7@oracle.com> (raw)
In-Reply-To: <57E40F29.3010509@arm.com>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
Hi,
On 22/09/2016 19:04, Andre Vieira (lists) wrote:
> diff --git a/gcc/hooks.c b/gcc/hooks.c
> index 99ec4014adb6fcbb073bf538dd00fe8695ee6cb2..1e925645c3173f8d97e104b9b2f480fca2ede438 100644
> --- a/gcc/hooks.c
> +++ b/gcc/hooks.c
> @@ -481,3 +481,13 @@ void
> hook_void_gcc_optionsp (struct gcc_options *opts ATTRIBUTE_UNUSED)
> {
> }
> +
> +/* Generic hook that takes an unsigned int, an unsigned int pointer and
> + returns false. */
> +
> +bool
> +hook_uint_uintp_false (unsigned int, unsigned int *)
> +{
> + return false;
> +}
> +
I don't see this change in the committed ChangeLog and, as is, it
doesn't have a counterpart in hooks.h. Something as trivial as the below
fixes the bootstrap error for me on x86_64-linux.
Thanks,
Paolo.
////////////////////
[-- Attachment #2: p --]
[-- Type: text/plain, Size: 528 bytes --]
Index: hooks.h
===================================================================
--- hooks.h (revision 240379)
+++ hooks.h (working copy)
@@ -76,6 +76,7 @@ extern void hook_void_tree (tree);
extern void hook_void_tree_treeptr (tree, tree *);
extern void hook_void_int_int (int, int);
extern void hook_void_gcc_optionsp (struct gcc_options *);
+extern bool hook_uint_uintp_false (unsigned int, unsigned int *);
extern int hook_int_uint_mode_1 (unsigned int, machine_mode);
extern int hook_int_const_tree_0 (const_tree);
next prev parent reply other threads:[~2016-09-22 20:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 14:46 [PATCH][ARM] " Andre Vieira (lists)
2016-07-01 19:04 ` Sandra Loosemore
2016-07-07 12:29 ` mickael guene
2016-07-07 12:31 ` mickael guene
2016-07-11 16:57 ` [PATCHv2][ARM] " Andre Vieira (lists)
2016-07-25 10:52 ` [PATCHv2, PING][ARM] " Andre Vieira (lists)
2016-08-11 14:13 ` [PATCHv2, PING 2][ARM] " Andre Vieira (lists)
2016-08-30 8:01 ` [PATCHv2, PING 3][ARM] " Andre Vieira (lists)
2016-09-19 9:25 ` [PATCHv2, PING 4][ARM] " Andre Vieira (lists)
2016-09-22 14:22 ` [PATCHv2][ARM] " Richard Earnshaw (lists)
2016-09-22 15:10 ` [PATCHv3][ARM] " Andre Vieira (lists)
2016-09-22 15:47 ` Richard Earnshaw (lists)
2016-09-22 17:24 ` Andre Vieira (lists)
2016-09-22 19:34 ` Christophe Lyon
2016-09-22 20:05 ` Bill Seurer
2016-09-22 20:30 ` Martin Sebor
2016-09-22 20:20 ` Paolo Carlini [this message]
2016-09-23 13:47 ` [PATCH, arm-embedded] " Andre Vieira (lists)
2016-09-23 6:31 ` [PATCHv2][ARM] " Sandra Loosemore
2016-09-23 8:51 ` Andre Vieira (lists)
2016-09-23 10:41 ` Andre Vieira (lists)
2016-09-23 15:12 ` Sandra Loosemore
2016-10-04 13:24 ` mickael guene
2016-10-04 14:15 ` Andre Vieira (lists)
2016-09-22 18:22 [PATCHv3][ARM] " David Edelsohn
2016-09-22 22:16 Uros Bizjak
2016-09-23 10:18 ` Jakub Jelinek
2016-09-23 10:39 ` Andre Vieira (lists)
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=939c9bac-b006-8833-a73b-24aa8b0329b7@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=Andre.SimoesDiasVieira@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).