From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] ARM: Introduce ARM_DEFAULT_SHORT_ENUMS
Date: Tue, 04 Apr 2017 10:52:00 -0000 [thread overview]
Message-ID: <58E37AF7.4050300@embedded-brains.de> (raw)
In-Reply-To: <58E37A8C.2070902@embedded-brains.de>
On 04/04/17 12:50, Sebastian Huber wrote:
> On 04/04/17 12:41, Ramana Radhakrishnan wrote:
>> [dropping devel at rtems dot org as I don't want more bounces]
>>
>> On Tue, Apr 4, 2017 at 10:07 AM, Sebastian Huber
>> <sebastian.huber@embedded-brains.de> wrote:
>>> >On 04/04/17 11:00, Ramana Radhakrishnan wrote:
>>>>> >>>
>>>>>> >>> > static bool
>>>>>> >>> > arm_default_short_enums (void)
>>>>>> >>> > {
>>>>>> >>> >- return TARGET_AAPCS_BASED && arm_abi != ARM_ABI_AAPCS_LINUX;
>>>>>> >>> >+ return ARM_DEFAULT_SHORT_ENUMS;
>>>>>> >>> > }
>>>>>> >>> >
>>>>>> >>> >
>>>>>> >>> >diff --git a/gcc/config/arm/rtems.h b/gcc/config/arm/rtems.h
>>>>>> >>> >index 53cd987..b34bbe8 100644
>>>>>> >>> >--- a/gcc/config/arm/rtems.h
>>>>>> >>> >+++ b/gcc/config/arm/rtems.h
>>>>>> >>> >@@ -27,3 +27,5 @@
>>>>>> >>> > builtin_assert ("system=rtems"); \
>>>>>> >>> > TARGET_BPABI_CPP_BUILTINS(); \
>>>>>> >>> > } while (0)
>>>>>> >>> >+
>>>>>> >>> >+#define ARM_DEFAULT_SHORT_ENUMS false
>>>> >>
>>>> >>It's a change in ABI for the RTEMS platform but it certainly needs a
>>>> >>documentation update in the release notes . Also, is it necessary
>>>> that
>>>> >>you need this in for GCC-7 or can you wait for stage-1 since we
>>>> are in
>>>> >>regression fixes mode ?
>>> >
>>> >
>>> >For RTEMS, ABI changes are not really critical. I would like to get
>>> this
>>> >into GCC 6.4. For GCC 7 its not urgent.
>>> >
>> The usual policy is not to have ABI changes within sub-releases of a
>> GCC release cycle. However if the RTEMs community is happy with it, I
>> have no particular objections. I would however strongly suggest that
>> if you are fixing it for GCC 6.4 to then fix it for GCC-7*and*
>> document it in the release notes.
>
> For RTEMS ABI changes are not a big deal. Its more important that we
> don't carry GCC patches around and can use a particular FSF release
> unmodified. I will add this change to the GCC 6.4 and 7.1 release
> notes, if this is all right for Jakub.
v2 of the patch is here:
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00138.html
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
prev parent reply other threads:[~2017-04-04 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 11:32 Sebastian Huber
2017-04-04 7:43 ` Bernhard Reutner-Fischer
2017-04-04 7:48 ` Sebastian Huber
2017-04-04 8:54 ` Ramana Radhakrishnan
2017-04-04 9:01 ` Ramana Radhakrishnan
2017-04-04 9:07 ` Sebastian Huber
2017-04-04 10:41 ` Ramana Radhakrishnan
2017-04-04 10:50 ` Sebastian Huber
2017-04-04 10:52 ` Sebastian Huber [this message]
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=58E37AF7.4050300@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=ramana.gcc@googlemail.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).