From: Richard Earnshaw <rearnsha@arm.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, ARM] require 64-bit hw-int for all arm targets
Date: Wed, 07 Aug 2013 13:52:00 -0000 [thread overview]
Message-ID: <5202510C.4030401@arm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1308070024500.16397@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On 07/08/13 01:25, Joseph S. Myers wrote:
> On Tue, 30 Jul 2013, Richard Earnshaw wrote:
>
>> Most arm target configs now require a 64-bit HW-int. Unfortunately a few of
>> the older, less commonly used config targets do not. The code in arm.c now
>> pretty much requires that a 64-bit HW-int is used, especially for
>> vectorization to work.
>>
>> This patch makes 64-bit HW-int the default for all arm configs and cleans up
>> the configure script accordingly.
>>
>> * config.gcc (arm): Require 64-bit host-wide-int for all ARM
>> target configs.
>
> The configuration in libcpp/configure.ac of which targets need 64-bit
> HOST_WIDE_INT always needs to be kept in sync with that in gcc/config.gcc.
>
Oops. Fixed thusly:
2013-08-07 Richard Earnshaw <rearnsha@arm.com>
* configure.ac: Set need_64bit_hwint for all arm targets.
* configure: Regenerated.
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 569 bytes --]
--- configure (revision 201547)
+++ configure (local)
@@ -7152,9 +7152,7 @@ fi
case $target in
aarch64*-*-* | \
alpha*-*-* | \
- arm*-*-*eabi* | \
- arm*-*-rtems* | \
- arm*-*-symbianelf* | \
+ arm*-*-* | \
x86_64-*-* | \
ia64-*-* | \
hppa*64*-*-* | \
--- configure.ac (revision 201547)
+++ configure.ac (local)
@@ -184,9 +184,7 @@ m4_changequote(,)
case $target in
aarch64*-*-* | \
alpha*-*-* | \
- arm*-*-*eabi* | \
- arm*-*-rtems* | \
- arm*-*-symbianelf* | \
+ arm*-*-* | \
x86_64-*-* | \
ia64-*-* | \
hppa*64*-*-* | \
prev parent reply other threads:[~2013-08-07 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 16:16 Richard Earnshaw
2013-08-07 0:26 ` Joseph S. Myers
2013-08-07 13:52 ` Richard Earnshaw [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=5202510C.4030401@arm.com \
--to=rearnsha@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).