* [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7
@ 2016-05-23 9:17 Ramana Radhakrishnan
2016-05-23 9:26 ` Richard Biener
0 siblings, 1 reply; 12+ messages in thread
From: Ramana Radhakrishnan @ 2016-05-23 9:17 UTC (permalink / raw)
To: gcc-patches
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
Hi,
The Steering Committee has decided to add aarch64-none-linux-gnu as a primary platform for GCC-7. This reflects the increasing popularity of the port and the increased general availability of hardware. I also took the opportunity of creating a GCC-7 criteria page at the same time.
Applied.
Thanks,
Ramana
[-- Attachment #2: gcc7-criteria.txt --]
[-- Type: text/plain, Size: 6778 bytes --]
Index: htdocs/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.1008
diff -a -u -r1.1008 index.html
--- htdocs/index.html 18 May 2016 12:50:06 -0000 1.1008
+++ htdocs/index.html 20 May 2016 23:17:54 -0000
@@ -167,7 +167,7 @@
</dd>
<dt><span class="version">Development:</span>
- GCC 7.0 (<a href="gcc-6/criteria.html">release criteria</a>)
+ GCC 7.0 (<a href="gcc-7/criteria.html">release criteria</a>)
</dt><dd>
Status:
<!--GCC 7 status below-->
--- /dev/null 2016-05-06 10:43:58.436131027 +0100
+++ htdocs/gcc-7/criteria.html 2016-05-21 00:06:34.530921981 +0100
@@ -0,0 +1,149 @@
+<html>
+
+<head>
+<title>GCC 7 Release Criteria</title> </head>
+
+<body>
+
+<h1>GCC 7 Release Criteria</h1>
+
+<p>This page provides the release criteria for GCC 7.</p>
+
+<p>The GCC team (and, in particular, the Release Managers) will attempt
+to meet these criteria before the release of GCC 7.</p>
+
+<p>In all cases, these criteria represent the minimum functionality
+required in order to make the release. If this level of minimum
+functionality is not provided by a release candidate, then that
+candidate will probably not become the eventual release. However, a
+release candidate that does meet these criteria may not necessarily
+become the official release; there may be other unforeseen issues that
+prevent release. For example, if support for the Intel Pentium II is
+required by the release criteria, it is nevertheless unlikely that GCC
+would be released even though it did not support the Intel Pentium.</p>
+
+<p>Because the development of GCC is largely dependent on volunteers,
+the Release Managers and/or Steering Committee may eventually have to
+decide whether to make a release, even if the criteria here are not
+met. For example, if no volunteer can be found to verify correct
+operation of a particular application program on a particular system,
+then that criterion may be abandoned.</p>
+
+<h1>Languages</h1>
+
+<p>GCC supports several programming languages, including Ada, C, C++,
+Fortran, Objective-C, Objective-C++, Go and Java.
+For the purposes of making releases,
+however, we will consider primarily C and C++, as those are the
+languages used by the vast majority of users. Therefore, if, below,
+the criteria indicate, for example, that there should be no DejaGNU
+regressions on a particular platform, that criteria should be read as
+applying only to DejaGNU regressions within the C, C++, and C++
+runtime library testsuites.</p>
+
+<h1>Primary and Secondary Platforms</h1>
+
+<p>GCC targets a vast number of platforms. We have classified these
+platforms into three categories: primary, secondary, and tertiary.
+Primary platforms are popular systems, both in the sense that there
+are many such systems in existence and in the sense that GCC is used
+frequently on those systems. Secondary platforms are also popular
+systems, but are either somewhat less popular than the primary
+systems, or are considered duplicative from a testing perspective.
+All platforms that are neither primary nor secondary are tertiary
+platforms.</p>
+
+<p>Our release criteria for primary platforms is:</p>
+<ul>
+
+<li>
+<p>All regressions open in Bugzilla have been analyzed, and all are
+deemed as either unlikely to affect most users, or are determined to
+have a minimal impact on affected users. For example, a
+typographical error in a diagnostic might be relatively common, but
+also has minimal impact on users.</p>
+
+<p>In general, regressions where the compiler generates incorrect
+code, or refuses to compile a valid program, will be considered to
+be sufficiently severe to block the release, unless there are
+substantial mitigating factors.</p>
+</li>
+
+<li>The DejaGNU testsuite has been run, and compared with a run of
+the testsuite on the previous release of GCC, and no regressions are
+observed.</li>
+</ul>
+
+<p>Our release criteria for the secondary platforms is:</p>
+<ul>
+<li>The compiler bootstraps successfully, and the C++ runtime library
+builds.</li>
+
+<li>The DejaGNU testsuite has been run, and a substantial majority of
+the tests pass.</li>
+</ul>
+
+<p>There are no release criteria for tertiary platforms.</p>
+
+<p>In general bugs blocking the release are marked with priority P1
+(<a href="../bugs/management.html">Maintaining the GCC Bugzilla database</a>).</p>
+
+<p>In contrast to previous releases, we have removed all mention of
+explicit application testing. It is our experience that, with the
+resources available, it is very difficult to methodically carry out
+such testing. However, we expect that interested users will submit
+bug reports for problems encountered building and using popular
+packages. Therefore, we do not intend the elimination of application
+testing from our criteria to imply that we will not pay attention to
+application testing.</p>
+
+<h2>Primary Platform List</h2>
+
+<p>The primary platforms are:</p>
+<ul>
+<li>aarch64-none-linux-gnu</li>
+<li>arm-linux-gnueabi</li>
+<li>i386-unknown-freebsd</li>
+<li>i686-pc-linux-gnu</li>
+<li>mipsisa64-elf</li>
+<li>powerpc64-unknown-linux-gnu</li>
+<li>sparc-sun-solaris2.10</li>
+<li>x86_64-unknown-linux-gnu</li>
+</ul>
+
+<h2>Secondary Platform List</h2>
+
+<p>The secondary platforms are:</p>
+<ul>
+<li>aarch64-elf</li>
+<li>i686-apple-darwin</li>
+<li>i686-pc-cygwin</li>
+<li>i686-mingw32</li>
+<li>powerpc-ibm-aix7.1.0.0</li>
+<li>s390x-linux-gnu</li>
+</ul>
+
+<h1>Code Quality and Compilation Time</h1>
+
+<p>In addition to correctness issues (e.g., generating incorrect code,
+or issuing an invalid diagnostic, or refusing to compile valid code),
+we will also consider code quality (i.e., the speed with which the
+generated code executes) and compilation time (i.e., the speed with
+which the compiler executes).</p>
+
+<p>It is difficult, if not impossible, to set out specific criteria
+for determining what level of regression is acceptable for these issues.
+In contrast to most correctness issues, where nothing short of correct
+is acceptable, it is reasonable to trade off behavior for code quality
+and compilation time. For example, it may be acceptable, when
+compiling with optimization, if the compiler is slower, but generates
+superior code. It may also be acceptable for the compiler to generate
+inferior code on some test cases if it generates substantially
+superior code on other test cases. Therefore, the Release Manager, or
+parties to whom he or she delegates responsibility, will make
+determinations on a case-by-case basis as to whether or not a code
+quality or compilation time regression is sufficiently severe as to
+merit blocking the release.</p>
+
+</body>
+</html>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7
2016-05-23 9:17 [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7 Ramana Radhakrishnan
@ 2016-05-23 9:26 ` Richard Biener
2016-05-23 15:47 ` Jeff Law
2016-05-23 22:21 ` Gerald Pfeifer
0 siblings, 2 replies; 12+ messages in thread
From: Richard Biener @ 2016-05-23 9:26 UTC (permalink / raw)
To: Ramana Radhakrishnan, Gerald Pfeifer, Andreas Tobler; +Cc: gcc-patches
On Mon, May 23, 2016 at 11:16 AM, Ramana Radhakrishnan
<ramana.radhakrishnan@foss.arm.com> wrote:
> Hi,
>
> The Steering Committee has decided to add aarch64-none-linux-gnu as a primary platform for GCC-7. This reflects the increasing popularity of the port and the increased general availability of hardware. I also took the opportunity of creating a GCC-7 criteria page at the same time.
>
> Applied.
Sorry to hijack the thread but I continue to notice that we have
i386-unknown-freebsd as a primary target. I notice here
the 'i386' (the only primary target still explicitely listing that
sub-target) and the fact that freebsd switched to LLVM as
far as I know.
So I propose to demote -freebsd to secondary and use
i686-unknown-freebsd (or x86_64-unknown-freebsd?).
Gerald, Andreas, can you comment on both issues? Esp. i386 is putting
quite some burden on libstdc++ and atomics support
for example.
Thanks,
Richard.
> Thanks,
> Ramana
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7
2016-05-23 9:26 ` Richard Biener
@ 2016-05-23 15:47 ` Jeff Law
2016-05-23 22:21 ` Gerald Pfeifer
1 sibling, 0 replies; 12+ messages in thread
From: Jeff Law @ 2016-05-23 15:47 UTC (permalink / raw)
To: Richard Biener, Ramana Radhakrishnan, Gerald Pfeifer, Andreas Tobler
Cc: gcc-patches
On 05/23/2016 03:26 AM, Richard Biener wrote:
> On Mon, May 23, 2016 at 11:16 AM, Ramana Radhakrishnan
> <ramana.radhakrishnan@foss.arm.com> wrote:
>> Hi,
>>
>> The Steering Committee has decided to add aarch64-none-linux-gnu as a primary platform for GCC-7. This reflects the increasing popularity of the port and the increased general availability of hardware. I also took the opportunity of creating a GCC-7 criteria page at the same time.
>>
>> Applied.
>
> Sorry to hijack the thread but I continue to notice that we have
> i386-unknown-freebsd as a primary target. I notice here
> the 'i386' (the only primary target still explicitely listing that
> sub-target) and the fact that freebsd switched to LLVM as
> far as I know.
>
> So I propose to demote -freebsd to secondary and use
> i686-unknown-freebsd (or x86_64-unknown-freebsd?).
>
> Gerald, Andreas, can you comment on both issues? Esp. i386 is putting
> quite some burden on libstdc++ and atomics support
> for example.
The target may claim i386, but it's actually i486+ so we don't have any
real issues around atomics. This came up in 2014.
We can look at demoting FreeBSD again; when we looked at it in 2014 it
wasn't seen as a particularly useful thing to do. But I'm open to
revisiting.
jeff
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7
2016-05-23 9:26 ` Richard Biener
2016-05-23 15:47 ` Jeff Law
@ 2016-05-23 22:21 ` Gerald Pfeifer
2016-05-24 9:01 ` Richard Biener
1 sibling, 1 reply; 12+ messages in thread
From: Gerald Pfeifer @ 2016-05-23 22:21 UTC (permalink / raw)
To: Richard Biener; +Cc: Ramana Radhakrishnan, Andreas Tobler, gcc-patches
On Mon, 23 May 2016, Richard Biener wrote:
> So I propose to demote -freebsd to secondary and use
> i686-unknown-freebsd (or x86_64-unknown-freebsd?).
>
> Gerald, Andreas, can you comment on both issues? Esp. i386
> is putting quite some burden on libstdc++ and atomics support
> for example.
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 <gerald@pfeifer.com>
* config/i386/freebsd.h (SUBTARGET32_DEFAULT_CPU): Change to i586.
Remove support for FreeBSD 5 and earlier.
And, yes, the system compiler on current versions of FreeBSD is
LLVM (for most platforms including x86). There is still a fair
user base, though.
Given the above, do you still see a desire to make this change?
Gerald
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7
2016-05-23 22:21 ` Gerald Pfeifer
@ 2016-05-24 9:01 ` Richard Biener
2017-03-04 16:40 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
2017-03-04 16:45 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
0 siblings, 2 replies; 12+ messages in thread
From: Richard Biener @ 2016-05-24 9:01 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: Ramana Radhakrishnan, Andreas Tobler, GCC Patches
On Tue, May 24, 2016 at 12:20 AM, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> On Mon, 23 May 2016, Richard Biener wrote:
>> So I propose to demote -freebsd to secondary and use
>> i686-unknown-freebsd (or x86_64-unknown-freebsd?).
>>
>> Gerald, Andreas, can you comment on both issues? Esp. i386
>> is putting quite some burden on libstdc++ and atomics support
>> for example.
>
> 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 <gerald@pfeifer.com>
>
> * config/i386/freebsd.h (SUBTARGET32_DEFAULT_CPU): Change to i586.
> Remove support for FreeBSD 5 and earlier.
>
> And, yes, the system compiler on current versions of FreeBSD is
> LLVM (for most platforms including x86). There is still a fair
> user base, though.
>
> Given the above, do you still see a desire to make this change?
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.
Richard.
> Gerald
^ permalink raw reply [flat|nested] 12+ messages in thread
* i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7)
2016-05-24 9:01 ` Richard Biener
@ 2017-03-04 16:40 ` Gerald Pfeifer
2017-03-07 16:34 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
2017-03-04 16:45 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
1 sibling, 1 reply; 12+ messages in thread
From: Gerald Pfeifer @ 2017-03-04 16:40 UTC (permalink / raw)
To: Richard Biener; +Cc: Ramana Radhakrishnan, Andreas Tobler, gcc-patches
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 <gerald@pfeifer.com>
>>
>> * config/i386/freebsd.h (SUBTARGET32_DEFAULT_CPU): Change to i586.
>> Remove support for FreeBSD 5 and earlier.
> 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.
Sooo, I finally got to submitting the patch below to the config.guess
maintainers.
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.)
Gerald
2017-03-04 Gerald Pfeifer <gerald@pfeifer.com>
* config.guess (*:FreeBSD:*:*): Refactor CPU handling.
Canonicalize i386-*-freebsd* to i586-*-freebsd*.
diff --git a/config.guess b/config.guess
index 1000e2b..180375c 100755
--- a/config.guess
+++ b/config.guess
@@ -837,10 +837,11 @@ EOF
UNAME_PROCESSOR=`/usr/bin/uname -p`
case ${UNAME_PROCESSOR} in
amd64)
- echo x86_64-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
- *)
- echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
+ UNAME_PROCESSOR=x86_64 ;;
+ i386)
+ UNAME_PROCESSOR=i586 ;;
esac
+ echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`
exit ;;
i*:CYGWIN*:*)
echo ${UNAME_MACHINE}-pc-cygwin
^ permalink raw reply [flat|nested] 12+ messages in thread
* i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7)
2016-05-24 9:01 ` Richard Biener
2017-03-04 16:40 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
@ 2017-03-04 16:45 ` Gerald Pfeifer
2017-03-07 16:33 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
1 sibling, 1 reply; 12+ messages in thread
From: Gerald Pfeifer @ 2017-03-04 16:45 UTC (permalink / raw)
To: Richard Biener; +Cc: Ramana Radhakrishnan, Andreas Tobler, gcc-patches
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 simple
patch below is all you actually may have had in mind. ;-)
Applied.
But let's still consider the config.guess change for GCC 7 as
well, or people might not be _appearing_ to use it, even if it
is practically the same?
Gerald
Index: gcc-7/criteria.html
===================================================================
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 -0000 1.2
+++ gcc-7/criteria.html 4 Mar 2017 16:41:02 -0000
@@ -103,7 +103,7 @@
<ul>
<li>aarch64-none-linux-gnu</li>
<li>arm-linux-gnueabi</li>
-<li>i386-unknown-freebsd</li>
+<li>i586-unknown-freebsd</li>
<li>i686-pc-linux-gnu</li>
<li>mipsisa64-elf</li>
<li>powerpc64-unknown-linux-gnu</li>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: i386-unknown-freebsd -> i586-unknown-freebsd
2017-03-04 16:45 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
@ 2017-03-07 16:33 ` Jeff Law
0 siblings, 0 replies; 12+ messages in thread
From: Jeff Law @ 2017-03-07 16:33 UTC (permalink / raw)
To: Gerald Pfeifer, Richard Biener
Cc: Ramana Radhakrishnan, Andreas Tobler, gcc-patches
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 simple
> patch below is all you actually may have had in mind. ;-)
>
> Applied.
>
> But let's still consider the config.guess change for GCC 7 as
> well, or people might not be _appearing_ to use it, even if it
> is practically the same?
No strong opinions here. Certainly fixing the triplet on the critera
page is a good thing.
Jeff
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: i386-unknown-freebsd -> i586-unknown-freebsd
2017-03-04 16:40 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
@ 2017-03-07 16:34 ` Jeff Law
2017-03-07 20:01 ` Updating config.guess (was: i386-unknown-freebsd -> i586-unknown-freebsd) Gerald Pfeifer
0 siblings, 1 reply; 12+ messages in thread
From: Jeff Law @ 2017-03-07 16:34 UTC (permalink / raw)
To: Gerald Pfeifer, Richard Biener
Cc: Ramana Radhakrishnan, Andreas Tobler, gcc-patches
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 <gerald@pfeifer.com>
>>>
>>> * config/i386/freebsd.h (SUBTARGET32_DEFAULT_CPU): Change to i586.
>>> Remove support for FreeBSD 5 and earlier.
>> 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.
>
> Sooo, I finally got to submitting the patch below to the config.guess
> maintainers.
>
> 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, I'd think it'd be reasonable.
jeff
^ permalink raw reply [flat|nested] 12+ messages in thread
* Updating config.guess (was: i386-unknown-freebsd -> i586-unknown-freebsd)
2017-03-07 16:34 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
@ 2017-03-07 20:01 ` Gerald Pfeifer
2017-03-13 15:33 ` Updating config.guess Jeff Law
0 siblings, 1 reply; 12+ messages in thread
From: Gerald Pfeifer @ 2017-03-07 20:01 UTC (permalink / raw)
To: Jeff Law, Richard Biener
Cc: Ramana Radhakrishnan, Andreas Tobler, gcc-patches
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, I'd think it'd be reasonable.
Here is the entire difference between the config.guess we have
and upstream.
Aye? :-)
Gerald
--- /home/gp/src/gcc/config.guess 2016-12-10 13:37:44.536966833 +0100
+++ ./config.guess 2017-03-04 16:07:52.863302161 +0100
@@ -1,8 +1,8 @@
#! /bin/sh
# Attempt to guess a canonical system name.
-# Copyright 1992-2016 Free Software Foundation, Inc.
+# Copyright 1992-2017 Free Software Foundation, Inc.
-timestamp='2016-10-02'
+timestamp='2017-03-04'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
@@ -50,7 +50,7 @@
GNU config.guess ($timestamp)
Originally written by Per Bothner.
-Copyright 1992-2016 Free Software Foundation, Inc.
+Copyright 1992-2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -837,10 +837,11 @@
UNAME_PROCESSOR=`/usr/bin/uname -p`
case ${UNAME_PROCESSOR} in
amd64)
- echo x86_64-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
- *)
- echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
+ UNAME_PROCESSOR=x86_64 ;;
+ i386)
+ UNAME_PROCESSOR=i586 ;;
esac
+ echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`
exit ;;
i*:CYGWIN*:*)
echo ${UNAME_MACHINE}-pc-cygwin
@@ -1343,6 +1344,9 @@
NSR-?:NONSTOP_KERNEL:*:*)
echo nsr-tandem-nsk${UNAME_RELEASE}
exit ;;
+ NSX-?:NONSTOP_KERNEL:*:*)
+ echo nsx-tandem-nsk${UNAME_RELEASE}
+ exit ;;
*:NonStop-UX:*:*)
echo mips-compaq-nonstopux
exit ;;
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Updating config.guess
2017-03-07 20:01 ` Updating config.guess (was: i386-unknown-freebsd -> i586-unknown-freebsd) Gerald Pfeifer
@ 2017-03-13 15:33 ` Jeff Law
2017-03-18 18:23 ` Gerald Pfeifer
0 siblings, 1 reply; 12+ messages in thread
From: Jeff Law @ 2017-03-13 15:33 UTC (permalink / raw)
To: Gerald Pfeifer, Richard Biener
Cc: Ramana Radhakrishnan, Andreas Tobler, gcc-patches
On 03/07/2017 01:01 PM, Gerald Pfeifer wrote:
> 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, I'd think it'd be reasonable.
>
> Here is the entire difference between the config.guess we have
> and upstream.
>
Yea, fine with me.
Jeff
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Updating config.guess
2017-03-13 15:33 ` Updating config.guess Jeff Law
@ 2017-03-18 18:23 ` Gerald Pfeifer
0 siblings, 0 replies; 12+ messages in thread
From: Gerald Pfeifer @ 2017-03-18 18:23 UTC (permalink / raw)
To: Jeff Law, Richard Biener
Cc: Ramana Radhakrishnan, Andreas Tobler, gcc-patches
On Mon, 13 Mar 2017, Jeff Law wrote:
>> Here is the entire difference between the config.guess we have
>> and upstream.
> Yea, fine with me.
Cool, here is what I just installed.
(Richi, i386-unknown-freebsd* is now "gone", both in terms of
our release documentation and automatic target detection.)
Gerald
2017-03-18 Gerald Pfeifer <gerald@pfeifer.com>
* config.guess: Import latest from upstream.
Index: config.guess
===================================================================
--- config.guess (revision 246257)
+++ config.guess (working copy)
@@ -1,8 +1,8 @@
#! /bin/sh
# Attempt to guess a canonical system name.
-# Copyright 1992-2016 Free Software Foundation, Inc.
+# Copyright 1992-2017 Free Software Foundation, Inc.
-timestamp='2016-10-02'
+timestamp='2017-03-05'
# This file is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
@@ -50,7 +50,7 @@
GNU config.guess ($timestamp)
Originally written by Per Bothner.
-Copyright 1992-2016 Free Software Foundation, Inc.
+Copyright 1992-2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
@@ -837,10 +837,11 @@
UNAME_PROCESSOR=`/usr/bin/uname -p`
case ${UNAME_PROCESSOR} in
amd64)
- echo x86_64-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
- *)
- echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'` ;;
+ UNAME_PROCESSOR=x86_64 ;;
+ i386)
+ UNAME_PROCESSOR=i586 ;;
esac
+ echo ${UNAME_PROCESSOR}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`
exit ;;
i*:CYGWIN*:*)
echo ${UNAME_MACHINE}-pc-cygwin
@@ -1343,6 +1344,9 @@
NSR-?:NONSTOP_KERNEL:*:*)
echo nsr-tandem-nsk${UNAME_RELEASE}
exit ;;
+ NSX-?:NONSTOP_KERNEL:*:*)
+ echo nsx-tandem-nsk${UNAME_RELEASE}
+ exit ;;
*:NonStop-UX:*:*)
echo mips-compaq-nonstopux
exit ;;
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2017-03-18 18:23 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-23 9:17 [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7 Ramana Radhakrishnan
2016-05-23 9:26 ` Richard Biener
2016-05-23 15:47 ` Jeff Law
2016-05-23 22:21 ` Gerald Pfeifer
2016-05-24 9:01 ` Richard Biener
2017-03-04 16:40 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
2017-03-07 16:34 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
2017-03-07 20:01 ` Updating config.guess (was: i386-unknown-freebsd -> i586-unknown-freebsd) Gerald Pfeifer
2017-03-13 15:33 ` Updating config.guess Jeff Law
2017-03-18 18:23 ` Gerald Pfeifer
2017-03-04 16:45 ` i386-unknown-freebsd -> i586-unknown-freebsd (was: [Patch wwwdocs] Add aarch64-none-linux-gnu as a primary platform for GCC-7) Gerald Pfeifer
2017-03-07 16:33 ` i386-unknown-freebsd -> i586-unknown-freebsd Jeff Law
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).