The site referenced in the 1.2.x configuration is no longer accessible.
The new configuration gives both an updated version and a more
permanent location.
---
bare/config/devel/dtc-1.4.1.cfg | 18 ++
rtems/config/4.11/rtems-moxie.bset | 2 +-
rtems/config/unst
On 1/9/2015 11:04 AM, Sebastian Huber wrote:
> On 01/09/2015 04:34 PM, Joel Sherrill wrote:
>> Is this patch on the gcc 4.9 branch and head?
> Yes, I committed this today. It is for the e6500 processor support used
> by the Freescale T-Series (e.g. T4240). It is a 64-bit PowerPC core with
> an A
On 01/09/2015 04:34 PM, Joel Sherrill wrote:
Is this patch on the gcc 4.9 branch and head?
Yes, I committed this today. It is for the e6500 processor support used
by the Freescale T-Series (e.g. T4240). It is a 64-bit PowerPC core with
an AltiVec unit and FPU. We use currently only the 32-bit
Is this patch on the gcc 4.9 branch and head?
--joel
On 1/9/2015 8:37 AM, Sebastian Huber wrote:
> Module:rtems-tools
> Branch:master
> Commit:3f4717852dddcf8ba56478ba98b9dbda32d87182
> Changeset:
> http://git.rtems.org/rtems-tools/commit/?id=3f4717852dddcf8ba56478ba98b9dbda32d87182
On January 9, 2015 3:05:11 AM CST, Sebastian Huber
wrote:
>Hello Joel,
>
>this is not a GCC bug. There is no BSP that uses the -mthumb
>-march=armv6-m yet, so this option is untested. You do you build the
>RTEMS multilibs?
This turned up building rtems in multilib mode.
So there is at lea
Hello Joel,
this is not a GCC bug. There is no BSP that uses the -mthumb
-march=armv6-m yet, so this option is untested. You do you build the
RTEMS multilibs?
On 08/01/15 17:57, Joel Sherrill wrote:
Hi
I think this is actually an RTEMS conditional issue but filed it as
a GCC PR anyway for
