On 18/10/2023 8:48 pm, Sebastian Huber wrote:
> On 18.10.23 12:29, Heinz Junkes wrote:
>> unfortunately also with the GCC 13.2 configuration still the same error:
>> nclude -g -O2 -mthumb -O2
>> -I../../../../gcc-13.2.0/libgcc/../newlib/libc/sys/rtems/include -g -O2
>> -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings
>> -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
>> -isystem ./include -fno-inline -g -DIN_LIBGCC2 -fbuilding-libgcc
>> -fno-stack-protector -Dinhibit_libc -fno-inline -I. -I. -I../../.././gcc
>> -I../../../../gcc-13.2.0/libgcc -I../../../../gcc-13.2.0/libgcc/.
>> -I../../../../gcc-13.2.0/libgcc/../gcc
>> -I../../../../gcc-13.2.0/libgcc/../include -DHAVE_CC_TLS -o _divtc3.o -MT
>> _divtc3.o -MD -MP -MF _divtc3.dep -DL_divtc3 -c
>> ../../../../gcc-13.2.0/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS
>> ../../../../gcc-13.2.0/libgcc/libgcc2.c: In function '__divdc3':
>> ../../../../gcc-13.2.0/libgcc/libgcc2.c:2063:7: internal compiler error:
>> Segmentation fault: 11 2063 | if (FABS (d) >= RBIG) | ^~ Please submit a full
>> bug report, with preprocessed source (by using -freport-bug). See
>> <https://gcc.gnu.org/bugs/> for instructions. make[4]: *** [_divdc3.o] Error 
>> 1
> 
> Ok, great. At least it is consistent. Maybe GCC 10 works.
> 
> This bug should be reported to the GCC project.

I have just built the RSB master on a Sonoma (14.0) MacBook M2 Pro ....

(r-py3) chris@weka rtems %  /Users/chris/development/rtems/6/bin/arm-rtems6-gcc
--version
arm-rtems6-gcc (GCC) 12.3.1 20231012 (RTEMS 6, RSB
633023de6517998ee3b84e7ed172b1c5f2bf502b, Newlib fbc5496)
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I am only using Xocde tools and related command line bits and pieces and a
python.org installed Python with a virtual env.

I do not have an Intel Mac with me to test on that. I will when I return home.

Chris
_______________________________________________
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Reply via email to