On 04/30/2014 05:00 PM, Jeff Law wrote:
> On 04/30/14 02:16, Richard Biener wrote:
>>
>> Testing coverage for non-64bit hwi configs is really low these
>> days (I know of only 32bit hppa-*-* that is still built and
>> tested semi-regularly - Dave, I suppose the host compiler
>> has a 64bit long lon
On 04/30/14 21:56, Wolf wrote:
Since the original MinGW refuses to support 64-bit, I would like to
discuss whether we should remove i686-mingw32 from the secondary
platforms list and replace it with MinGW-w64.
Kai should probably chime in here with his recommendation on the
technical side. If/w
2014-05-01 17:23 GMT+02:00 Jeff Law :
> On 04/30/14 21:56, Wolf wrote:
>>
>> Since the original MinGW refuses to support 64-bit, I would like to
>> discuss whether we should remove i686-mingw32 from the secondary
>> platforms list and replace it with MinGW-w64.
>
> Kai should probably chime in here
> I think its more natural to generate user-space code by default.
Well, the other architectures I know of think differently so we'll follow them.
--
Eric Botcazou
> Thanks for the reminder. I've now pushed rpms to
>
> http://people.redhat.com/~rth/
>
> That's a 4.9 backport of the changes now on mainline, on top of the current
> fedora rawhide package. The srpm of course contains the backport patch.
Thanks for the link. I'll backport the changes to t
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:
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/2013-12/msg00036.html
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 noticed and mentioned this already a while ago:
>
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 using clang. I am hoping someone
>>> has some ideas about th
Snapshot gcc-4.8-20140501 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20140501/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
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
11 matches
Mail list logo
