From owner-freebsd-stable  Fri May  8 10:47:36 1998
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA01345
          for freebsd-stable-outgoing; Fri, 8 May 1998 10:47:36 -0700 (PDT)
          (envelope-from owner-freebsd-stable@FreeBSD.ORG)
Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01283
          for <stable@FreeBSD.ORG>; Fri, 8 May 1998 10:47:02 -0700 (PDT)
          (envelope-from kline@tera.tera.com)
Received: from athena.tera.com (athena.tera.com [207.224.230.127])
	by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id KAA21722;
	Fri, 8 May 1998 10:32:32 -0700 (PDT)
From: Gary Kline <kline@tera.tera.com>
Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id KAA28883; Fri, 8 May 1998 10:32:30 -0700 (PDT)
Date: Fri, 8 May 1998 10:32:30 -0700 (PDT)
Message-Id: <199805081732.KAA28883@athena.tera.com>
To: stable@FreeBSD.ORG
Subject: gcc quandry
Cc: kline@tera.tera.com, kline@thought.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk


	After several evenings trying to chase down an 
	impossible bug in an X application it finally 
	occured to me to try compiling on my SunOS at work
	and compare.

	Bingo!  Same code, different logical results.  Here,
	we've got v2.7.2.3.f.1; on tao (still at 2.2-R) it
	is slightly earlier.   At work, my trace was bug-free;
	at home, not.

	One solution would be up upgrade to gcc 2.8.X, but
	the note about this latest rev being buggy have 
	me a bit concerned.... esp'ly since I frequency 
	mod my kernel.

	Has anybody seen significant bugs with the latest 
	gcc?

	thanks,

	gary



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message