public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "richard.earnshaw at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
Date: Tue, 10 Jul 2018 17:51:00 -0000	[thread overview]
Message-ID: <bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-86383-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383

--- Comment #7 from richard.earnshaw at arm dot com ---
On 10/07/18 10:57, Kamil Rytarowski wrote:
> On 06.07.2018 15:26, Richard Earnshaw (lists) wrote:
>> On 06/07/18 12:11, Kamil Rytarowski wrote:
>>> On 06.07.2018 12:38, Richard Earnshaw (lists) wrote:
>>>> On 06/07/18 11:32, Kamil Rytarowski wrote:
>>>>> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>>>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>>>>>
>>>>>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>>>>>> I'm not sure how relevant the netbsd-elf port is these days.  I believe they've
>>>>>> now moved onto an EABI based ABI.  But no GCC port of that has been
>>>>>> contributed.
>>>>>>
>>>>>
>>>>> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
>>>>> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
>>>>> ARMv4 CPUs use OABI only.
>>>>>
>>>>
>>>> GCC-9 will drop support for pre-armv4 CPUs.  Such support has been
>>>> marked as deprecated for about 3 years now.
>>>>
>>>
>>> We verify these ports on real hardware.
>>>
>>> NetBSD/shark is prepared to be switched to Clang/LLVM as GCC is
>>> obsoleting it and surprisingly LLVM soon might have support for a wider
>>> range of ARM CPUs.
>>>
>>
>> Shark's use strongARM cpus, which are ARMv4.  That's not been obsoleted,
>> but it is considered deprecated these days.
>>
> 
> Shark doesn't use all instructions that are generated by GCC (I forgot
> the CPU property name of it) and thus it has to be switched to Clang/LLVM.
> 

You're not making sense.  Please be more explicit as to what you mean
and give an example.  GCC can generate instructions for ARMv4 and
StrongARM (used by the shark) is an ARMv4 part.

I've run gcc generated code on shark boards for years and not seen problems.

R.
>From gcc-bugs-return-609563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 17:51:54 2018
Return-Path: <gcc-bugs-return-609563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127123 invoked by alias); 10 Jul 2018 17:51:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127098 invoked by uid 89); 10 Jul 2018 17:51:52 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-7.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,GIT_PATCH_2,KAM_SHORT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy\x10072018, Hx-languages-length:2097, 10.07.2018
X-HELO: mout.gmx.net
Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Jul 2018 17:51:50 +0000
Received: from [192.168.0.241] ([89.78.252.225]) by mail.gmx.com (mrgmx101 [212.227.17.174]) with ESMTPSA (Nemesis) id 0M3NEK-1fuLC72S1Y-00qxrK; Tue, 10 Jul 2018 19:51:47 +0200
Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
To: "richard.earnshaw at arm dot com" <gcc-bugzilla@gcc.gnu.org>, gcc-bugs@gcc.gnu.org
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/> <bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/>
From: Kamil Rytarowski <n54@gmx.com>
Message-ID: <88abee64-0dba-a0f3-3fe6-2f5bc1b48338@gmx.com>
Date: Tue, 10 Jul 2018 17:58:00 -0000
User-Agent: Mozilla/5.0 (X11; NetBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="l3lP98rnts7fcqiEzEfmJCHEzylvYWjsS"
X-IsSubscribed: yes
X-SW-Source: 2018-07/txt/msg00668.txt.bz2

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--l3lP98rnts7fcqiEzEfmJCHEzylvYWjsS
Content-Type: multipart/mixed; boundary="KGzHY4kyuzOvQcp9dLJhgxVIRc80oxzTK";
 protected-headers="v1"
From: Kamil Rytarowski <n54@gmx.com>
To: "richard.earnshaw at arm dot com" <gcc-bugzilla@gcc.gnu.org>,
 gcc-bugs@gcc.gnu.org
Message-ID: <88abee64-0dba-a0f3-3fe6-2f5bc1b48338@gmx.com>
Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler
 fails in selftests
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/>
 <bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/>


--KGzHY4kyuzOvQcp9dLJhgxVIRc80oxzTK
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Content-length: 2045

On 10.07.2018 19:49, richard.earnshaw at arm dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
> 
> --- Comment #7 from richard.earnshaw at arm dot com ---
> On 10/07/18 10:57, Kamil Rytarowski wrote:
>> On 06.07.2018 15:26, Richard Earnshaw (lists) wrote:
>>> On 06/07/18 12:11, Kamil Rytarowski wrote:
>>>> On 06.07.2018 12:38, Richard Earnshaw (lists) wrote:
>>>>> On 06/07/18 11:32, Kamil Rytarowski wrote:
>>>>>> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>>>>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>>>>>>
>>>>>>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>>>>>>> I'm not sure how relevant the netbsd-elf port is these days.  I believe they've
>>>>>>> now moved onto an EABI based ABI.  But no GCC port of that has been
>>>>>>> contributed.
>>>>>>>
>>>>>>
>>>>>> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
>>>>>> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
>>>>>> ARMv4 CPUs use OABI only.
>>>>>>
>>>>>
>>>>> GCC-9 will drop support for pre-armv4 CPUs.  Such support has been
>>>>> marked as deprecated for about 3 years now.
>>>>>
>>>>
>>>> We verify these ports on real hardware.
>>>>
>>>> NetBSD/shark is prepared to be switched to Clang/LLVM as GCC is
>>>> obsoleting it and surprisingly LLVM soon might have support for a wider
>>>> range of ARM CPUs.
>>>>
>>>
>>> Shark's use strongARM cpus, which are ARMv4.  That's not been obsoleted,
>>> but it is considered deprecated these days.
>>>
>>
>> Shark doesn't use all instructions that are generated by GCC (I forgot
>> the CPU property name of it) and thus it has to be switched to Clang/LLVM.
>>
> 
> You're not making sense.  Please be more explicit as to what you mean
> and give an example.  GCC can generate instructions for ARMv4 and
> StrongARM (used by the shark) is an ARMv4 part.
> 
> I've run gcc generated code on shark boards for years and not seen problems.
> 
> R.
> 

I got a feedback that it's called: armv4t.


--KGzHY4kyuzOvQcp9dLJhgxVIRc80oxzTK--

--l3lP98rnts7fcqiEzEfmJCHEzylvYWjsS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
Content-length: 850

-----BEGIN PGP SIGNATURE-----

iQJABAEBCAAqFiEELaxVpweEzw+lMDwuS7MI6bAudmwFAltE8pUMHG41NEBnbXgu
Y29tAAoJEEuzCOmwLnZsv2sP/3a6F7DZfGbA5bMdYOe1MF0uNKhTp6bHvXwZfAhI
FKALWnvgMzcMVb2Me9j8w+fem6ZtDntkyZCWeEOz+ATu7r4KiNV4Zrds6MjrsBZd
7sHyIkPZVnDeBml9tUCGF9IBwvpS4YJkipBEVGa6jNf06yXV24if9KmlkchoxS7D
zckeo+odR5HTDWYUfXfbBv+yMaxHtTUtLVUkkeVh06RJ5lRmgm9z6mmoK2HKjdxP
vIJnnT4POYcv6TO9TFTIqZ1a+olClexgCJB6lVkb+EKVJVCCfjDFYlMvcc5IV4/G
inQFKzArWof6slb9S2WbNX6uBI921FgcDYWE7GOfMemmKYioGXLzs0TTIKIMt+rY
i4OEu681duoqVrvmJ3CqJzvnGly4YQ1Sl0Zrlb78Ha885Ojk3JU2vaYlNEyUDK+D
OBm6P8oIpd6LS6fmYq/5UfwdEfkJgLw+ykGcAIbkdeKOKLkU++uLTSluMqRaxapF
lPzTQ+M14f2LGt9mXDvY5S7N55e21jtDuo9tCXsCHg5jfZJeKlS3nRi9MCStv+Kp
7wqk+etRCjhsZ7PkXQQQa/d5arXj6+wKN3QwKOdZOjFJPUmYMxkVYasIQi3Hl1AE
KLyfwM7E80mRdaBaOp+Ii9cjjJMSsXWAWFK1xyefjseuxNIrZZUcrbz0OEY6veT4
bs0/
=NlK1
-----END PGP SIGNATURE-----

--l3lP98rnts7fcqiEzEfmJCHEzylvYWjsS--


      parent reply	other threads:[~2018-07-10 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-86383-4@http.gcc.gnu.org/bugzilla/>
     [not found] ` <bug-86383-4-roe7g6Jp7o@http.gcc.gnu.org/bugzilla/>
     [not found]   ` <ab84a63d-cc85-0cfd-a3a6-d6deab95488c@gmx.com>
2018-07-06 10:38     ` Richard Earnshaw (lists)
2018-07-06 10:39 ` richard.earnshaw at arm dot com
2018-07-06 13:26 ` richard.earnshaw at arm dot com
2018-07-10 17:51 ` richard.earnshaw at arm dot com [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=bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).