| Message ID | 20241213-upstream-intelgt-mvp-v2-1-5c4caeb7b33d@intel.com |
|---|---|
| State | New |
| Headers |
Return-Path: <binutils-bounces~patchwork=sourceware.org@sourceware.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 7A6243858414 for <patchwork@sourceware.org>; Fri, 13 Dec 2024 16:09:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7A6243858414 Authentication-Results: sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=XNMtaTJP X-Original-To: binutils@sourceware.org Delivered-To: binutils@sourceware.org Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.15]) by sourceware.org (Postfix) with ESMTPS id 12F2E3857BA9; Fri, 13 Dec 2024 16:00:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 12F2E3857BA9 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=intel.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 12F2E3857BA9 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=192.198.163.15 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1734105656; cv=none; b=Up6DjxS75C6dT/6SaA4M00j6yGW0/m7ynkxQ2ImmhlEs8SwoiSgnoOhc9lX6upF2FZFCTemXB2gRxwC70eSNoUlsMHkkoXxMtgN3dKhqBzdtqNVRy01BA72sZ1LjCUs9LFI/GSSsimcGei3qXIwuhbWcBOKiXF+WHjSLHNCvQeg= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1734105656; c=relaxed/simple; bh=bVrsMTGM2mtDjEcSAFo6tXHaVT99WgeHSqGBA/wwRRI=; h=DKIM-Signature:From:To:Subject:Date:Message-Id:MIME-Version; b=APqCGyAnf5ZNyiwum5YnnFql3bH8sL3bdufDgHr5wq9GDB4CcgkbQj/d5PfgcX8+If3XJI0jnQDMM1cVefb8cKadA+LofxqfsyUtfzc/uYS3xGd0K+4/8SObQqV6fEcVeI/3KEUVRdfuZEY5ipgh3sFD9IDKeXgbuIT+uF7Lims= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 12F2E3857BA9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1734105656; x=1765641656; h=from:to:subject:date:message-id:in-reply-to:references: mime-version:content-transfer-encoding; bh=bVrsMTGM2mtDjEcSAFo6tXHaVT99WgeHSqGBA/wwRRI=; b=XNMtaTJPeTIsoZePHq8QVhVgaRkm3dYaBD17vt4I5kSQdIZ+v/ExY1Zu AUKg1LNpyLXs16x7sfaDS7rnUFHe7TEj5OPvjT99xkSnp3/0EXsUt4B4q 7ueb/SoXYCGde5UOpY8cl7IBFoVLe2ASpheLVekpc+IC4H9poIQb3494x eGC5KDVRiEujnkXCF5x+XK8UCLSq+x6Zqo3lbDB84ruRm/FkELEItGuGN mw9W7bpn+KCU0VY8KnjsCS8JXizU39HZ+Ku8bN0qsDi/69CrLQCnz/u3m 0NNVSuX4wPDPNE32EPq0tyeF9FQ4iZdEwUEhE/86+cvGevtM7AISdFBo4 w==; X-CSE-ConnectionGUID: 5TPjRRxGTuWLcw87OAB89Q== X-CSE-MsgGUID: dWYQDbDmQAuE33KcJDZ6xw== X-IronPort-AV: E=McAfee;i="6700,10204,11285"; a="34696314" X-IronPort-AV: E=Sophos;i="6.12,231,1728975600"; d="scan'208";a="34696314" Received: from orviesa010.jf.intel.com ([10.64.159.150]) by fmvoesa109.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2024 08:00:56 -0800 X-CSE-ConnectionGUID: rZqKoMdGRGOTYRkCgUKm7A== X-CSE-MsgGUID: bIKocJVfRRy3qUZZ5c/TPQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.12,224,1728975600"; d="scan'208";a="96434272" Received: from gkldtt-dev-004.igk.intel.com (HELO localhost) ([10.123.221.202]) by orviesa010-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2024 08:00:54 -0800 From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com> To: gdb-patches@sourceware.org, Markus Metzger <markus.t.metzger@intel.com>, config-patches@gnu.org, binutils@sourceware.org Subject: [PATCH v2 01/47] gdb, intelgt: add intelgt as a basic machine Date: Fri, 13 Dec 2024 16:59:18 +0100 Message-Id: <20241213-upstream-intelgt-mvp-v2-1-5c4caeb7b33d@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20241213-upstream-intelgt-mvp-v2-0-5c4caeb7b33d@intel.com> References: <20241213-upstream-intelgt-mvp-v2-0-5c4caeb7b33d@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Mailer: b4 0.14.2 Content-Transfer-Encoding: base64 X-Spam-Status: No, score=-11.0 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Binutils mailing list <binutils.sourceware.org> List-Unsubscribe: <https://sourceware.org/mailman/options/binutils>, <mailto:binutils-request@sourceware.org?subject=unsubscribe> List-Archive: <https://sourceware.org/pipermail/binutils/> List-Post: <mailto:binutils@sourceware.org> List-Help: <mailto:binutils-request@sourceware.org?subject=help> List-Subscribe: <https://sourceware.org/mailman/listinfo/binutils>, <mailto:binutils-request@sourceware.org?subject=subscribe> Errors-To: binutils-bounces~patchwork=sourceware.org@sourceware.org |
| Series |
[v2,01/47] gdb, intelgt: add intelgt as a basic machine
|
|
Commit Message
Aktemur, Tankut Baris
Dec. 13, 2024, 3:59 p.m. UTC
Add 'intelgt' as a basic machine to config.sub. To: <config-patches@gnu.org> To: <binutils@sourceware.org> --- config.sub | 1 + 1 file changed, 1 insertion(+)
Comments
On 13.12.2024 16:59, Tankut Baris Aktemur wrote: > Add 'intelgt' as a basic machine to config.sub. > > To: <config-patches@gnu.org> > To: <binutils@sourceware.org> > --- > config.sub | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/config.sub b/config.sub > index 2c6a07ab3c34eabed8318ec0a37c0cc23b77a63f..63ff958ec125e543674e9b261d5e5bb2fa749c4e 100755 > --- a/config.sub > +++ b/config.sub > @@ -1205,6 +1205,7 @@ case $cpu-$vendor in > | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ > | hexagon \ > | i370 | i*86 | i860 | i960 | ia16 | ia64 \ > + | intelgt \ > | ip2k | iq2000 \ > | k1om \ > | kvx \ > Patch 3 enables ld, but I can't spot any gas enabling (sadly the cover letter wasn't Cc-ed to the binutils list). Don't you further need to exclude gas from attempts of configuring? I'm also puzzled by that difference: The series supposedly is about enabling gdb. Why enable ld there? Just because it's (seemingly) easy? Jan
On Monday, December 16, 2024 8:54 AM, Jan Beulich wrote: > On 13.12.2024 16:59, Tankut Baris Aktemur wrote: > > Add 'intelgt' as a basic machine to config.sub. > > > > To: <config-patches@gnu.org> > > To: <binutils@sourceware.org> > > --- > > config.sub | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/config.sub b/config.sub > > index 2c6a07ab3c34eabed8318ec0a37c0cc23b77a63f..63ff958ec125e543674e9b261d5e5bb2fa749c4e > 100755 > > --- a/config.sub > > +++ b/config.sub > > @@ -1205,6 +1205,7 @@ case $cpu-$vendor in > > | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ > > | hexagon \ > > | i370 | i*86 | i860 | i960 | ia16 | ia64 \ > > + | intelgt \ > > | ip2k | iq2000 \ > > | k1om \ > > | kvx \ > > > > Patch 3 enables ld, but I can't spot any gas enabling (sadly the cover letter > wasn't Cc-ed to the binutils list). Sorry, this is my bad. I'll Cc binutils in the next revision submission. For the time being, the link to the cover letter is https://sourceware.org/pipermail/gdb-patches/2024-December/214029.html > Don't you further need to exclude gas from > attempts of configuring? > > I'm also puzzled by that difference: The series supposedly is about enabling > gdb. Why enable ld there? Just because it's (seemingly) easy? > > Jan Without enabling ld, when configured as <src>/configure --enable-targets="intelgt-elf" 'make' gives *** ld does not support target intelgt-unknown-elf *** see ld/configure.tgt for supported targets Regards -Baris Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
On 17.12.2024 19:48, Aktemur, Tankut Baris wrote: > On Monday, December 16, 2024 8:54 AM, Jan Beulich wrote: >> On 13.12.2024 16:59, Tankut Baris Aktemur wrote: >>> Add 'intelgt' as a basic machine to config.sub. >>> >>> To: <config-patches@gnu.org> >>> To: <binutils@sourceware.org> >>> --- >>> config.sub | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff --git a/config.sub b/config.sub >>> index 2c6a07ab3c34eabed8318ec0a37c0cc23b77a63f..63ff958ec125e543674e9b261d5e5bb2fa749c4e >> 100755 >>> --- a/config.sub >>> +++ b/config.sub >>> @@ -1205,6 +1205,7 @@ case $cpu-$vendor in >>> | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ >>> | hexagon \ >>> | i370 | i*86 | i860 | i960 | ia16 | ia64 \ >>> + | intelgt \ >>> | ip2k | iq2000 \ >>> | k1om \ >>> | kvx \ >>> >> >> Patch 3 enables ld, but I can't spot any gas enabling (sadly the cover letter >> wasn't Cc-ed to the binutils list). > > Sorry, this is my bad. I'll Cc binutils in the next revision submission. > For the time being, the link to the cover letter is > > https://sourceware.org/pipermail/gdb-patches/2024-December/214029.html > >> Don't you further need to exclude gas from >> attempts of configuring? >> >> I'm also puzzled by that difference: The series supposedly is about enabling >> gdb. Why enable ld there? Just because it's (seemingly) easy? >> >> Jan > > Without enabling ld, when configured as > > <src>/configure --enable-targets="intelgt-elf" > > 'make' gives > > *** ld does not support target intelgt-unknown-elf > *** see ld/configure.tgt for supported targets Like I think I said for gas, that imo wants dealing with by a top level configure change, adding ld to noconfigtargets for intelgt. Jan
Hi, On Wednesday, December 18, 2024 8:20 AM, Jan Beulich wrote: > On 17.12.2024 19:48, Aktemur, Tankut Baris wrote: > > On Monday, December 16, 2024 8:54 AM, Jan Beulich wrote: > >> On 13.12.2024 16:59, Tankut Baris Aktemur wrote: > >>> Add 'intelgt' as a basic machine to config.sub. > >>> > >>> To: <config-patches@gnu.org> > >>> To: <binutils@sourceware.org> > >>> --- > >>> config.sub | 1 + > >>> 1 file changed, 1 insertion(+) > >>> > >>> diff --git a/config.sub b/config.sub > >>> index > 2c6a07ab3c34eabed8318ec0a37c0cc23b77a63f..63ff958ec125e543674e9b261d5e5bb2fa749c4e > >> 100755 > >>> --- a/config.sub > >>> +++ b/config.sub > >>> @@ -1205,6 +1205,7 @@ case $cpu-$vendor in > >>> | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ > >>> | hexagon \ > >>> | i370 | i*86 | i860 | i960 | ia16 | ia64 \ > >>> + | intelgt \ > >>> | ip2k | iq2000 \ > >>> | k1om \ > >>> | kvx \ > >>> > >> > >> Patch 3 enables ld, but I can't spot any gas enabling (sadly the cover letter > >> wasn't Cc-ed to the binutils list). > > > > Sorry, this is my bad. I'll Cc binutils in the next revision submission. > > For the time being, the link to the cover letter is > > > > https://sourceware.org/pipermail/gdb-patches/2024-December/214029.html > > > >> Don't you further need to exclude gas from > >> attempts of configuring? > >> > >> I'm also puzzled by that difference: The series supposedly is about enabling > >> gdb. Why enable ld there? Just because it's (seemingly) easy? > >> > >> Jan > > > > Without enabling ld, when configured as > > > > <src>/configure --enable-targets="intelgt-elf" > > > > 'make' gives > > > > *** ld does not support target intelgt-unknown-elf > > *** see ld/configure.tgt for supported targets > > Like I think I said for gas, that imo wants dealing with by a top level > configure change, adding ld to noconfigtargets for intelgt. Our overall goal at this step is to enable GDB. A GPU workload executes by being submitted to the device from a host/native process. Therefore, although enabling GDB only for the GPU target is possible, in general it needs to be enabled in addition to the native target. That is, it makes sense that a x86-64 target is the primary one whereas the intelgt target is enabled as a secondary target, so that GDB is able to debug native processes as usual, plus the GPU workloads. The $noconfigdirs approach works for the primary target only. Hence, we cannot use it for an 'enabled-targets' target. Another approach we can take is to not touch ld and let it fail. The expectation would be then: 1. either configure GDB with "--disable-ld --disable-gas ..." and then use "make" to build it, or 2. configure without disabling components but then use "make all-gdb" to build. Our case is in fact similar to AMD GPU (ROCm) debug support in GDB. The online documentation at https://rocm.docs.amd.com/projects/ROCgdb/en/latest/install/installation.html#build suggests using "--disable-ld --disable-gas ...". Otherwise ld would fail with *** ld does not support target amdgcn-amd-amdhsa *** see ld/configure.tgt for supported targets Regards, -Baris Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
Hello Jan, On Friday, December 20, 2024 10:55 AM, Aktemur, Tankut Baris wrote: > Hi, > > On Wednesday, December 18, 2024 8:20 AM, Jan Beulich wrote: > > On 17.12.2024 19:48, Aktemur, Tankut Baris wrote: > > > On Monday, December 16, 2024 8:54 AM, Jan Beulich wrote: > > >> On 13.12.2024 16:59, Tankut Baris Aktemur wrote: > > >>> Add 'intelgt' as a basic machine to config.sub. > > >>> > > >>> To: <config-patches@gnu.org> > > >>> To: <binutils@sourceware.org> > > >>> --- > > >>> config.sub | 1 + > > >>> 1 file changed, 1 insertion(+) > > >>> > > >>> diff --git a/config.sub b/config.sub > > >>> index > > 2c6a07ab3c34eabed8318ec0a37c0cc23b77a63f..63ff958ec125e543674e9b261d5e5bb2fa749c4e > > >> 100755 > > >>> --- a/config.sub > > >>> +++ b/config.sub > > >>> @@ -1205,6 +1205,7 @@ case $cpu-$vendor in > > >>> | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ > > >>> | hexagon \ > > >>> | i370 | i*86 | i860 | i960 | ia16 | ia64 \ > > >>> + | intelgt \ > > >>> | ip2k | iq2000 \ > > >>> | k1om \ > > >>> | kvx \ > > >>> > > >> > > >> Patch 3 enables ld, but I can't spot any gas enabling (sadly the cover letter > > >> wasn't Cc-ed to the binutils list). > > > > > > Sorry, this is my bad. I'll Cc binutils in the next revision submission. > > > For the time being, the link to the cover letter is > > > > > > https://sourceware.org/pipermail/gdb-patches/2024-December/214029.html > > > > > >> Don't you further need to exclude gas from > > >> attempts of configuring? > > >> > > >> I'm also puzzled by that difference: The series supposedly is about enabling > > >> gdb. Why enable ld there? Just because it's (seemingly) easy? > > >> > > >> Jan > > > > > > Without enabling ld, when configured as > > > > > > <src>/configure --enable-targets="intelgt-elf" > > > > > > 'make' gives > > > > > > *** ld does not support target intelgt-unknown-elf > > > *** see ld/configure.tgt for supported targets > > > > Like I think I said for gas, that imo wants dealing with by a top level > > configure change, adding ld to noconfigtargets for intelgt. > > Our overall goal at this step is to enable GDB. > > A GPU workload executes by being submitted to the device from a > host/native process. Therefore, although enabling GDB only for the > GPU target is possible, in general it needs to be enabled in addition > to the native target. That is, it makes sense that a x86-64 target is > the primary one whereas the intelgt target is enabled as a secondary > target, so that GDB is able to debug native processes as usual, plus > the GPU workloads. > > The $noconfigdirs approach works for the primary target only. Hence, > we cannot use it for an 'enabled-targets' target. > > Another approach we can take is to not touch ld and let it fail. The > expectation would be then: > > 1. either configure GDB with "--disable-ld --disable-gas ..." and > then use "make" to build it, or > > 2. configure without disabling components but then use "make > all-gdb" to build. > > Our case is in fact similar to AMD GPU (ROCm) debug support in GDB. > The online documentation at > > https://rocm.docs.amd.com/projects/ROCgdb/en/latest/install/installation.html#build > > suggests using "--disable-ld --disable-gas ...". Otherwise ld would > fail with > > *** ld does not support target amdgcn-amd-amdhsa > *** see ld/configure.tgt for supported targets Any further comments? Regards, -Baris Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928
On 03.02.2025 18:17, Aktemur, Tankut Baris wrote: > Hello Jan, > > On Friday, December 20, 2024 10:55 AM, Aktemur, Tankut Baris wrote: >> Hi, >> >> On Wednesday, December 18, 2024 8:20 AM, Jan Beulich wrote: >>> On 17.12.2024 19:48, Aktemur, Tankut Baris wrote: >>>> On Monday, December 16, 2024 8:54 AM, Jan Beulich wrote: >>>>> On 13.12.2024 16:59, Tankut Baris Aktemur wrote: >>>>>> Add 'intelgt' as a basic machine to config.sub. >>>>>> >>>>>> To: <config-patches@gnu.org> >>>>>> To: <binutils@sourceware.org> >>>>>> --- >>>>>> config.sub | 1 + >>>>>> 1 file changed, 1 insertion(+) >>>>>> >>>>>> diff --git a/config.sub b/config.sub >>>>>> index >>> 2c6a07ab3c34eabed8318ec0a37c0cc23b77a63f..63ff958ec125e543674e9b261d5e5bb2fa749c4e >>>>> 100755 >>>>>> --- a/config.sub >>>>>> +++ b/config.sub >>>>>> @@ -1205,6 +1205,7 @@ case $cpu-$vendor in >>>>>> | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ >>>>>> | hexagon \ >>>>>> | i370 | i*86 | i860 | i960 | ia16 | ia64 \ >>>>>> + | intelgt \ >>>>>> | ip2k | iq2000 \ >>>>>> | k1om \ >>>>>> | kvx \ >>>>>> >>>>> >>>>> Patch 3 enables ld, but I can't spot any gas enabling (sadly the cover letter >>>>> wasn't Cc-ed to the binutils list). >>>> >>>> Sorry, this is my bad. I'll Cc binutils in the next revision submission. >>>> For the time being, the link to the cover letter is >>>> >>>> https://sourceware.org/pipermail/gdb-patches/2024-December/214029.html >>>> >>>>> Don't you further need to exclude gas from >>>>> attempts of configuring? >>>>> >>>>> I'm also puzzled by that difference: The series supposedly is about enabling >>>>> gdb. Why enable ld there? Just because it's (seemingly) easy? >>>>> >>>>> Jan >>>> >>>> Without enabling ld, when configured as >>>> >>>> <src>/configure --enable-targets="intelgt-elf" >>>> >>>> 'make' gives >>>> >>>> *** ld does not support target intelgt-unknown-elf >>>> *** see ld/configure.tgt for supported targets >>> >>> Like I think I said for gas, that imo wants dealing with by a top level >>> configure change, adding ld to noconfigtargets for intelgt. >> >> Our overall goal at this step is to enable GDB. >> >> A GPU workload executes by being submitted to the device from a >> host/native process. Therefore, although enabling GDB only for the >> GPU target is possible, in general it needs to be enabled in addition >> to the native target. That is, it makes sense that a x86-64 target is >> the primary one whereas the intelgt target is enabled as a secondary >> target, so that GDB is able to debug native processes as usual, plus >> the GPU workloads. >> >> The $noconfigdirs approach works for the primary target only. Hence, >> we cannot use it for an 'enabled-targets' target. >> >> Another approach we can take is to not touch ld and let it fail. The >> expectation would be then: >> >> 1. either configure GDB with "--disable-ld --disable-gas ..." and >> then use "make" to build it, or >> >> 2. configure without disabling components but then use "make >> all-gdb" to build. >> >> Our case is in fact similar to AMD GPU (ROCm) debug support in GDB. >> The online documentation at >> >> https://rocm.docs.amd.com/projects/ROCgdb/en/latest/install/installation.html#build >> >> suggests using "--disable-ld --disable-gas ...". Otherwise ld would >> fail with >> >> *** ld does not support target amdgcn-amd-amdhsa >> *** see ld/configure.tgt for supported targets > > Any further comments? No; as you copy pre-existing behavior, I'm okay(ish). Jan
diff --git a/config.sub b/config.sub index 2c6a07ab3c34eabed8318ec0a37c0cc23b77a63f..63ff958ec125e543674e9b261d5e5bb2fa749c4e 100755 --- a/config.sub +++ b/config.sub @@ -1205,6 +1205,7 @@ case $cpu-$vendor in | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] | hppa64 \ | hexagon \ | i370 | i*86 | i860 | i960 | ia16 | ia64 \ + | intelgt \ | ip2k | iq2000 \ | k1om \ | kvx \