public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Oleg Endo <oleg.endo@t-online.de>
To: David Sherwood <david.sherwood@arm.com>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>,
	Richard Sandiford <Richard.Sandiford@arm.com>
Subject: Re: [PATCH][4/N] Introduce new inline functions for GET_MODE_UNIT_SIZE and GET_MODE_UNIT_PRECISION
Date: Thu, 27 Aug 2015 12:26:00 -0000	[thread overview]
Message-ID: <62DFBE89-764E-4F9A-82C7-47DB45C78729@t-online.de> (raw)
In-Reply-To: <000001d0e09e$2a606780$7f213680$@arm.com>

Hi,

On 27 Aug 2015, at 16:58, David Sherwood <david.sherwood@arm.com> wrote:

> Hi Oleg,
> 
> Oh I'm so sorry I broke the build - I should have spotted that. Have you 
> already checked in this fix or do you want me to?

No, I haven't committed the patch.  Please do so if it's OK.

Cheers,
Oleg



>> -----Original Message-----
>> From: Oleg Endo [mailto:oleg.endo@t-online.de]
>> Sent: 26 August 2015 15:53
>> To: Jeff Law
>> Cc: David Sherwood; GCC Patches
>> Subject: Re: [PATCH][4/N] Introduce new inline functions for GET_MODE_UNIT_SIZE and
>> GET_MODE_UNIT_PRECISION
>> 
>> 
>> On 26 Aug 2015, at 23:27, Oleg Endo <oleg.endo@t-online.de> wrote:
>> 
>>> 
>>> On 19 Aug 2015, at 22:35, Jeff Law <law@redhat.com> wrote:
>>> 
>>>> On 08/19/2015 06:29 AM, David Sherwood wrote:
>>>>>> I asked Richard S. to give this a once-over which he did.  However, he
>>>>>> technically can't approve due to the way his maintainership position was
>>>>>> worded.
>>>>>> 
>>>>>> The one request would be a function comment for emit_mode_unit_size and
>>>>>> emit_mode_unit_precision.  OK with that change.
>>>>> Thanks. Here's a new patch with the comments added.
>>>>> 
>>>>> Good to go?
>>>>> David.
>>>>> 
>>>>> ChangeLog:
>>>>> 
>>>>> 2015-08-19  David Sherwood  <david.sherwood@arm.com>
>>>>> 
>>>>> 	gcc/
>>>>> 	* genmodes.c (emit_mode_unit_size_inline): New function.
>>>>> 	(emit_mode_unit_precision_inline): New function.
>>>>> 	(emit_insn_modes_h): Emit new #define.  Emit new functions.
>>>>> 	(emit_mode_unit_size): New function.
>>>>> 	(emit_mode_unit_precision): New function.
>>>>> 	(emit_mode_adjustments): Add mode_unit_size adjustments.
>>>>> 	(emit_insn_modes_c): Emit new arrays.
>>>>> 	* machmode.h (GET_MODE_UNIT_SIZE, GET_MODE_UNIT_PRECISION): Update to
>>>>> 	use new inline methods.
>>>> 
>>>> Thanks, this is OK for the trunk.
>>> 
>>> It seems this broke sh-elf, at least when compiling on OSX with its native clang.
>>> 
>>> ../../gcc-trunk/gcc/machmode.h:228:43: error: redefinition of 'mode_unit_size' with a different
> type:
>>>     'const unsigned char [56]' vs 'unsigned char [56]'
>>> extern CONST_MODE_UNIT_SIZE unsigned char mode_unit_size[NUM_MACHINE_MODES];
>>>                                         ^
>>> ./insn-modes.h:417:24: note: previous definition is here
>>> extern unsigned char mode_unit_size[NUM_MACHINE_MODES];
>>>                      ^
>> 
>> This following fixes the problem for me:
>> 
>> Index: gcc/genmodes.c
>> ===================================================================
>> --- gcc/genmodes.c	(revision 227221)
>> +++ gcc/genmodes.c	(working copy)
>> @@ -1063,7 +1063,7 @@
>> unsigned char\n\
>> mode_unit_size_inline (machine_mode mode)\n\
>> {\n\
>> -  extern unsigned char mode_unit_size[NUM_MACHINE_MODES];\n\
>> +  extern CONST_MODE_UNIT_SIZE unsigned char mode_unit_size[NUM_MACHINE_MODES];\n\
>>   switch (mode)\n\
>>     {");
>> 
>> 
>> Cheers,
>> Oleg
> 
> 
> 

  reply	other threads:[~2015-08-27 12:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 11:52 David Sherwood
2015-08-18 19:26 ` Jeff Law
2015-08-19 12:35   ` David Sherwood
2015-08-19 13:41     ` Jeff Law
2015-08-26 14:34       ` Oleg Endo
2015-08-26 14:54         ` Oleg Endo
2015-08-27  7:59           ` David Sherwood
2015-08-27 12:26             ` Oleg Endo [this message]
2015-09-01  6:01           ` Jeff Law
2015-09-01 12:45 David Sherwood

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=62DFBE89-764E-4F9A-82C7-47DB45C78729@t-online.de \
    --to=oleg.endo@t-online.de \
    --cc=Richard.Sandiford@arm.com \
    --cc=david.sherwood@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@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).