Fwd: GCC 4.7.0 Release Candidate available from gcc.gnu.org

[Ralf Corsepius]

On 03/05/2012 09:22 PM, Joel Sherrill wrote:
> On 03/05/2012 10:11 AM, Sebastian Huber wrote:
>> On 03/05/2012 04:39 PM, Ralf Corsepius wrote:
>>> On 03/05/2012 12:14 PM, Sebastian Huber wrote:
>>>> On 03/05/2012 12:03 PM, Ralf Corsepius wrote:
>>>>> arm-rtems* fails with this:
>>>>> ...
>>>>> *** Configuration arm-unknown-rtems4.11 is obsolete.
>>>>> *** Specify --enable-obsolete to build it anyway.
>>>>> *** Support will be REMOVED in the next major release of GCC,
>>>>> *** unless a maintainer comes forward.
>>>>> ...
>>>>>
>>>>> ... I am speechless about this jerkery :(

>>> I read this as "wishful thinking outrules reason and practice".
>> You should read this as "it is past time to abandon an obsolete and
>> unmaintained configuration". The EABI for ARM is available in GCC
>> since 2004.
>>
>> http://gcc.gnu.org/ml/gcc-patches/2011-12/msg00692.html
>>
> This was only for the development head. Even if it was less mature,
> it looked reasonably good and it wasn't a big deal.
>
> It is only an issue because of the target naming choice.
>
> It isn't a big deal. Fix the names so EABI is the arm-rtems.

This doesn't match with GCC's intention.

They have "obsoleted" "arm*-*" and are enforcing "arm*-*eabi*.

 From gcc/config.gcc:
...
# Obsolete configurations.
case ${target} in
  # Avoid special cases that are not obsolete
    arm*-*-*eabi*                        \
  )
      ;;
    alpha*-dec-osf5.1*                   \
  | arm*-*-ecos-elf                      \
  | arm*-*-elf                           \
  | arm*-*-freebsd*                      \
  | arm*-*-linux*                        \
  | arm*-*-rtems*                        \
  | arm*-*-uclinux*                      \
  | arm*-wince-pe*                       \
  | mips-sgi-irix6.5                     \
  | mips*-*-openbsd*                     \
  | score-*                              \
  | *-*-solaris2.8*                      \
  )
     if test "x$enable_obsolete" != xyes; then
       echo "*** Configuration ${target} is obsolete." >&2
       echo "*** Specify --enable-obsolete to build it anyway." >&2
       echo "*** Support will be REMOVED in the next major release of 
GCC," >&2
       echo "*** unless a maintainer comes forward." >&2
       exit 1
     fi;;
esac
...

=> They have "obsoleted" all "arm*-*" targets but "arm*-*eabi*.

Like I said in my other mail, if we follow their wish, we need to stop 
supporting "arm-rtems*", which would mean us to remove "arm-rtems" from 
our toolchain portfolio and from RTEMS-4.11/RTEMS-master.

I'd rather not do so, but would prefer to either hack GCC-4.7.0 to 
continue accepting "arm-rtems" or to let "arm-rtems" stay with GCC-4.6.x.

Ralf