From owner-freebsd-current Sun Sep 22 7:29:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04EB137B401 for ; Sun, 22 Sep 2002 07:29:53 -0700 (PDT) Received: from mx10.mail.ru (mx10.mail.ru [194.67.57.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id C086A43E65 for ; Sun, 22 Sep 2002 07:29:51 -0700 (PDT) (envelope-from kan@mail.ru) Received: from drweb by mx10.mail.ru with drweb-scanned (Exim MX.A) id 17t7k5-000KnI-00; Sun, 22 Sep 2002 18:29:49 +0400 Received: from [141.154.55.48] (helo=kan.dnsalias.net) by mx10.mail.ru with esmtp (Exim SMTP.A) id 17t7k5-000Kma-00; Sun, 22 Sep 2002 18:29:49 +0400 Received: from kan.dnsalias.net (localhost [IPv6:::1]) by kan.dnsalias.net (8.12.6/8.12.5) with ESMTP id g8METkQ3015403; Sun, 22 Sep 2002 10:29:46 -0400 (EDT) (envelope-from kan@kan.dnsalias.net) Received: (from kan@localhost) by kan.dnsalias.net (8.12.6/8.12.6/Submit) id g8METeWa015402; Sun, 22 Sep 2002 10:29:40 -0400 (EDT) Date: Sun, 22 Sep 2002 10:29:40 -0400 From: Alexander Kabaev To: Mike Silbersack Cc: current@FreeBSD.ORG Subject: Re: -mcpu=pentiumpro still evil? Message-Id: <20020922102940.5b3cfc26.kabaev@bellatlantic.net> In-Reply-To: <20020921230908.A4834-100000@patrocles.silby.com> References: <20020921230908.A4834-100000@patrocles.silby.com> Reply-To: ak03@gte.com X-Mailer: Sylpheed version 0.8.2claws30 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Envelope-To: silby@silby.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 21 Sep 2002 23:10:51 -0500 (CDT) Mike Silbersack wrote: > > Is anyone else still seeing Sig 11's from GCC when mcpu=pentiumpro is > enabled (as it appears to be by default now)? I get a segfault in the > same place every time when compiling a DIAGNOSTIC kernel when I leave > it enabled. > > Just curious if this is just me or not... > > Mike "Silby" Silbersack > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Please post an error message and a traceback from GCC if possible. I might have the patch for that. -- Alexander Kabaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message