Re: [PATCH] newlib patch for OpenRISC

[Joel Sherrill <joel dot sherrill at oarcorp dot com>]

On 7/15/2014 4:14 PM, Hesham Moustafa wrote:
> On Mon, Jul 14, 2014 at 3:44 PM, Corinna Vinschen <vinschen@redhat.com> wrote:
>> On Jul 12 00:07, Hesham ALMatary wrote:
>>> From: hesham <hesham@hesham-laptop.(none)>
>>>
>>> The following patch is part of my GSoC project--Porting RTEMS to OpenRISC. It
>>> adds minimal OpenRISC port to newlib without any libgloss stuff.
>> A ChangeLog entry would be nice. 
Once that's posted, is this OK to merge?

The OpenRISC folks have libgloss code they can submit. This lets
the RTEMS port move forward.
>>  The patch looks basically ok, but
>> what happened with or16 and or32 target names?  Can you provide some
>> background why it's ok to nuke them?
>>
> All or32 targets has been renamed to or1k now (I believe because of
> the new 64 bit
> addition). Also, the new binutils patch here [1] did this renaming. GCC, GDB
> and RTEMS also follow or1k target name. or32, or16 are no longer used/defined by
> any of them.
>
> [1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=73589c9dbddc7906fa6a150f2a2a0ff6b746e8ba
Yeah.. this was easy to sleep through but it happened. :)
>> Thanks,
>> Corinna
>>
>> --
>> Corinna Vinschen
>> Cygwin Maintainer
>> Red Hat

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