On Tue, 7 Mar 2017, Jeff Law wrote:
>> When/if this has been accepted, is it okay to pull the latest config.guess
>> into GCC even at this stage of the release process? (We're only looking
>> at this change and the addition of nsx-tandem compared to what we have
>> right now.)
> If it's just those
On 03/04/2017 09:40 AM, Gerald Pfeifer wrote:
On Tue, 24 May 2016, Richard Biener wrote:
As Jeff noted, i386 actually is the "marketing" name used for the
platform, GCC has been defaulting to i486 for ages, and I upgraded
to i586 last year:
2015-11-15 Gerald Pfeifer
* config/i38
On 03/04/2017 09:44 AM, Gerald Pfeifer wrote:
On Tue, 24 May 2016, Richard Biener wrote:
Can we update to a non-marketing name then, like i586-unknown-freebsd
please? config.gcc accepts i[34567]86-*-freebsd*. It at least confused
me.
Of course, once I hacked config.gcc, I realized that the si
=
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/criteria.html,v
retrieving revision 1.2
diff -u -r1.2 criteria.html
--- gcc-7/criteria.html 1 Mar 2017 16:07:23 - 1.2
+++ gcc-7/criteria.html 4 Mar 2017 16:41:02 -
@@ -103,7 +103,7 @@
aarch64-none-linux-gnu
arm-linux-gnueabi
-i386-unknown
On Tue, 24 May 2016, Richard Biener wrote:
>> As Jeff noted, i386 actually is the "marketing" name used for the
>> platform, GCC has been defaulting to i486 for ages, and I upgraded
>> to i586 last year:
>>
>> 2015-11-15 Gerald Pfeifer
>>
>> * config/i386/freebsd.h (SUBTARGET32_DEFAU
