On Mon, 2016-04-18 at 14:15 -0500, Joel Sherrill wrote:
> Since I stated that, we decided to use the 6.1 branch for a while.
> So I decided to look at config/sh/linux.h and see what it was doing.
> Copying if on the 6.1 branch seemed liked an option. But it only
> appears to address SH3 and SH1 fo
On 4/18/2016 6:11 AM, Oleg Endo wrote:
On Sun, 2016-04-17 at 13:33 -0500, Joel Sherrill wrote:
Thanks for the quick and thorough reply.
This doesn't happen with GCC 4.9 which we are using on our newest
release branch. With any luck your work will be in gcc 7 before we
make another release br
On Sun, 2016-04-17 at 13:33 -0500, Joel Sherrill wrote:
> Thanks for the quick and thorough reply.
>
> This doesn't happen with GCC 4.9 which we are using on our newest
> release branch. With any luck your work will be in gcc 7 before we
> make another release branch.
That's probably because of
On April 16, 2016 7:50:21 PM CDT, Oleg Endo wrote:
>Hi,
>
>On Sat, 2016-04-16 at 18:58 -0500, Joel Sherrill wrote:
>
>> I am hoping the solution to this is obvious to someone
>> more familiar with the C++ libraries. Recently the
>> sh4 BSP for RTEMS began to have undefined symbols
>> like this w
Hi,
On Sat, 2016-04-16 at 18:58 -0500, Joel Sherrill wrote:
> I am hoping the solution to this is obvious to someone
> more familiar with the C++ libraries. Recently the
> sh4 BSP for RTEMS began to have undefined symbols
> like this when linking a C++ test:
>
> /data/home/joel/rtems-4.11-work/t
Hi
I am hoping the solution to this is obvious to someone
more familiar with the C++ libraries. Recently the
sh4 BSP for RTEMS began to have undefined symbols
like this when linking a C++ test:
/data/home/joel/rtems-4.11-work/tools/4.12/bin/../lib/gcc/sh-rtems4.12/6.0.0/ml/m4/libstdc++.a(cxx11-s
