Re: gcc 4.9.0 do not build on OSX

2014-05-03 Thread Chris Johns
On 3/05/2014 10:57 pm, Franzi Edo. wrote: Hi, I am trying to build a gcc-4.9.0 ARM cross compiler on OSX Mavericks unsuccessfully. My toolchain works fine with the previous version 4.8.2 but on the 4.9.0 I have this error during the gcc building pass 1. /opt/uKOS/Packages/gcc-4.9.0/gcc/config/

Re: gcc 4.9.0 do not build on OSX

2014-05-03 Thread Chris Johns
On 4/05/2014 12:34 pm, Andrew Pinski wrote: On Sat, May 3, 2014 at 5:48 PM, Chris Johns wrote: On 3/05/2014 10:57 pm, Franzi Edo. wrote: Hi, I am trying to build a gcc-4.9.0 ARM cross compiler on OSX Mavericks unsuccessfully. My toolchain works fine with the previous version 4.8.2 but on the

Re: gcc 4.9.0 do not build on OSX

2014-05-05 Thread Chris Johns
On 4/05/2014 12:34 pm, Andrew Pinski wrote: On Sat, May 3, 2014 at 5:48 PM, Chris Johns wrote: On 3/05/2014 10:57 pm, Franzi Edo. wrote: Hi, I am trying to build a gcc-4.9.0 ARM cross compiler on OSX Mavericks unsuccessfully. My toolchain works fine with the previous version 4.8.2 but on the

Re: GCC 4.9.1 Status Report (2014-07-10)

2014-07-11 Thread Chris Johns
On 12/07/2014 4:52 am, Franzi Edo. wrote: make CFLAGS="-g -O2 -fbracket-depth=512” (512, 1024, 2048 … no way)! For a cross-compiler I think this should be BUILD_CFLAGS and I suggest 1024 rather than 512 ? Chris

Re: GCC 4.9.1 Status Report (2014-07-10)

2014-07-13 Thread Chris Johns
On 13/07/2014 3:38 am, Franzi Edo. wrote: Hi James (all), Thank you for all of your suggestions. I tried everything unsuccessfully. Unfortunately, the make CFLAGS="-g -O2 -fbracket-depth=1024” and the make BUILD_CFLAGS="-g -O2 -fbracket-depth=1024” do not solve the problem. Please add 'BUILD_

Re: Obscure crashes due to gcc 4.9 -O2 => -fisolate-erroneous-paths-dereference

2015-02-19 Thread Chris Johns
On 20/02/2015 8:23 am, Joel Sherrill wrote: On 2/19/2015 2:56 PM, Sandra Loosemore wrote: Jakub Jelinek wrote: On Wed, Feb 18, 2015 at 11:21:56AM -0800, Jeff Prothero wrote: Starting with gcc 4.9, -O2 implicitly invokes -fisolate-erroneous-paths-dereference: which https://gcc.gnu

Re: Obscure crashes due to gcc 4.9 -O2 => -fisolate-erroneous-paths-dereference

2015-03-03 Thread Chris Johns
On 28/02/2015 9:12 am, Manuel López-Ibáñez wrote: On 02/19/15 14:56, Chris Johns wrote: My main concern is not knowing the trap has been added to the code. If I could build an application and audit it somehow then I can manage it. We have a similar issue with the possible use of FP registers

Building gcc 12 cross-compiler with --enable-lto on FreeBSD fails

2022-06-15 Thread Chris Johns
Hi, I am trying to build a cross-compiler on FreeBSD with --enable-lto because a chip vendor is using it when building controller software that is part of a system. The build I am using symlinks gmp, mpfr etc as source so they are built as part of the gcc build. The mpfr package is reporting ..

Re: Building gcc 12 cross-compiler with --enable-lto on FreeBSD fails

2022-06-15 Thread Chris Johns
On 15/6/22 7:56 pm, Richard Biener wrote: > On Wed, Jun 15, 2022 at 11:27 AM Chris Johns > wrote: >> >> Hi, >> >> I am trying to build a cross-compiler on FreeBSD with --enable-lto because a >> chip vendor is using it when building controller software tha

Building gcc-12 on MacOS Ventura (aarch64)

2023-03-24 Thread Chris Johns
Hi, I am sorting out some issues building RTEMS on MacOS including the M processors. The building gcc-12.2.1 for the few architectures I tested fail with sig faults in xgcc when building the runtime. I tried arm, aarch64 and sparc. As a result I wondered about bootstrapping gcc and using that to b

Re: Building gcc-12 on MacOS Ventura (aarch64)

2023-03-24 Thread Chris Johns
On 25/3/2023 10:07 am, Jonathan Wakely wrote: > On Fri, 24 Mar 2023, 23:07 Jonathan Wakely, <mailto:jwakely@gmail.com>> wrote: > On Fri, 24 Mar 2023, 23:03 Chris Johns, <mailto:ch...@contemporary.net.au>> wrote: > > Hi, > > I

Re: Building gcc-12 on MacOS Ventura (aarch64)

2023-03-25 Thread Chris Johns
On 25/3/2023 11:08 am, Stuff Received wrote: > On 2023-03-24 19:51, Chris Johns wrote: >> On 25/3/2023 10:07 am, Jonathan Wakely wrote: >>> On Fri, 24 Mar 2023, 23:07 Jonathan Wakely, >> <mailto:jwakely@gmail.com>> wrote: >>>      On Fri, 24 Mar 2