GCC Version Questions

[Joel Sherrill]

On 04/27/2012 06:43 AM, Ralf Corsepius wrote:
> On 04/27/2012 01:35 PM, Sebastian Huber wrote:
>> On 04/27/2012 01:29 PM, Ralf Corsepius wrote:
>>> On 04/27/2012 01:15 PM, Sebastian Huber wrote:
>>>> On 04/27/2012 12:06 PM, Ralf Corsepius wrote:
>>>>> On 04/27/2012 11:57 AM, Sebastian Huber wrote:
>>>>>> On 04/27/2012 11:47 AM, Ralf Corsepius wrote:
>>>>>>> Or differently:
>>>>>>> Do _you_ (Sebastian) want to force the RTEMS-4.11 users to using
>>>>>>> arm-eabi and
>>>>>>> tell them the target they have been using in their products for years
>>>>>>> will now
>>>>>>> face a sudden death?
>>>>>> Yes, this is exactly what I want to tell the RTEMS 4.11 users.
>>>>>>
>>>>> OK, the arm-rtems is gone from rtems-crossrpms.
>>>>>
>>>>> I'll remove the packages from the repositories, ASAP.
>>>> Ok, thanks for this. Can you please also rename the arm-rtemseabi into
>>>> arm-rtems to be in line with all other RTEMS targets.
>>> Errr? Upstream GCC _forces_ us to use arm-rtemseabi.
>>>
>>> We *can* not change this into arm-rtems
>> Oh, sorry. I will provide a patch for GCC to remove the old arm-rtems
>> target and rename arm-rtemseabi into arm-rtems.
> This would contradict the working principles of way they are using the
> canonicalization tuple - Anybody with a sane mind would reject such a
> proposal.
I call bull on this Ralf. We can call the tuple anything we want
as long as it follows the form.  The form is

CPU-VENDOR-OS<VERSION>

CPU = arm
VENDOR = unknown (implied since not specified)
OS = rtems
VERSION = 4.xx

Sometimes you see a "distinguishing phrase" after the OS
to denote something odd like an old object format.  How about
this one?

$ ./config.sub i386-linuxaout
i386-pc-linux-gnuaout

And in the middle of the EABI switch in config.gcc, I see
"arm*-*-symbianelf*" which is an EABI target.

Upstream gcc did away with vanilla arm ELF support
and now have only EABI ABI format support. It did not
force any naming changes on anyone. It was up to
us to manage the naming of the ELF and EABI targets
during the transition.

Individual projects select what target names make sense
for their users. The RTEMS Project standard naming convention
is <CPU>-rtems<VERSION>.

The bottom line is that a mistake was made in not renaming
arm-rtems to arm-rtemself and using arm-rtemseabi as
arm-rtems PRIOR to 4.7 branching.

I have prepared patches for 4.7 and the GCC head which
do this. Sebastian is testing them and will post about
that when he is ready.

At that point,
> Ralf
>
>
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel


-- 
Joel Sherrill, Ph.D.             Director of Research&   Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
     Support Available             (256) 722-9985