Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
On 11.07.2018 11:46, Richard Earnshaw (lists) wrote: > On 10/07/18 18:53, Kamil Rytarowski wrote: >> 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 --- > 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. >> > > From whom? StrongARM is ARMv4. It is *not* ARMv4t as it does not > support Thumb. Whatever, GCC can support both ARMv4 and ARMv4t. > > R. > CC: Joerg who was involved in the work on switch to Clang/LLVM. signature.asc Description: OpenPGP digital signature
Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
On 10/07/18 18:53, Kamil Rytarowski wrote: > 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 --- 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. > >From whom? StrongARM is ARMv4. It is *not* ARMv4t as it does not support Thumb. Whatever, GCC can support both ARMv4 and ARMv4t. R.
Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
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 --- >>> 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. signature.asc Description: OpenPGP digital signature
Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
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 --- >> 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.
Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
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 --- > 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. signature.asc Description: OpenPGP digital signature
Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
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 --- 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.
Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
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 --- >>> 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. signature.asc Description: OpenPGP digital signature
Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
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 --- >> 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.
Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
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 --- > 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. signature.asc Description: OpenPGP digital signature
