On 1 May 2014 22:17, Joel Sherrill wrote:
> This seems to fix it. I am not sure why sh.c is the only file in
> gcc/config which includes sstream though. Is this a violation
> of some new rule?
A rule that a feature can only be used if it's in more than one file? ;-)
> Is there a PR for this?
ht
On May 1, 2014, at 11:17 PM, Joel Sherrill wrote:
>
> On 5/1/2014 3:29 PM, Oleg Endo wrote:
>> On 01 May 2014, at 22:08, Joel Sherrill wrote:
>>
>>> Hi
>>>
>>> gcc-4.8.2 targeting sh-*-* fails to compile on
>>> FreeBSD 10 which is usi
On 5/1/2014 3:29 PM, Oleg Endo wrote:
> On 01 May 2014, at 22:08, Joel Sherrill wrote:
>
>> Hi
>>
>> gcc-4.8.2 targeting sh-*-* fails to compile on
>> FreeBSD 10 which is using clang. I am hoping someone
>> has some ideas about these.
> Yes, I've no
On 01 May 2014, at 22:08, Joel Sherrill wrote:
> Hi
>
> gcc-4.8.2 targeting sh-*-* fails to compile on
> FreeBSD 10 which is using clang. I am hoping someone
> has some ideas about these.
Yes, I've noticed and mentioned this already a while ago:
http://gcc.gnu.org/ml/gcc/2
Hi
gcc-4.8.2 targeting sh-*-* fails to compile on
FreeBSD 10 which is using clang. I am hoping someone
has some ideas about these.
In file included from ../../gcc-4.8.2/gcc/config/sh/sh.c:63:
In file included from /usr/include/c++/v1/sstream:174:
In file included from /usr/include/c++/v1/ostream
