From cmascott@world.std.com  Thu Aug 27 09:23:24 1998
Received: from europe.std.com (europe.std.com [199.172.62.20])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02959
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 27 Aug 1998 09:23:23 -0700 (PDT)
          (envelope-from cmascott@world.std.com)
Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0)
	id MAA28718; Thu, 27 Aug 1998 12:22:31 -0400 (EDT)
Received: from europa.local (world-f.std.com) by world.std.com (TheWorld/Spike-2.0)
	id AA18857; Thu, 27 Aug 1998 12:22:29 -0400
Received: (from cmascott@localhost)
	by europa.local (8.8.8/8.8.8) id MAA00552;
	Thu, 27 Aug 1998 12:22:24 -0400 (EDT)
	(envelope-from cmascott)
Message-Id: <199808271622.MAA00552@europa.local>
Date: Thu, 27 Aug 1998 12:22:24 -0400 (EDT)
From: cmascott@world.std.com
Reply-To: cmascott@world.std.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: xlint/gcc: "warning: integral constant too large"
X-Send-Pr-Version: 3.2

>Number:         7757
>Category:       bin
>Synopsis:       xlint/gcc: "warning: integral constant too large"
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 27 09:30:00 PDT 1998
>Closed-Date:    Fri Oct 30 01:55:34 PST 1998
>Last-Modified:  Fri Oct 30 02:00:20 PST 1998
>Originator:     Carl Mascott
>Release:        FreeBSD 2.2.7-RELEASE i386
>Organization:
>Environment:

FreeBSD europa.local 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Mon Aug 24 20:48:25 EDT 1998
cmascott@europa.local:/usr/src/sys/compile/EUR980824  i386

>Description:

I submitted this before as bin/7066.
That PR was closed without doing anything to fix the problem.

I just upgraded to 2.2.7 and had to apply the same fix to xlint
for the second time.

There is a bug in gcc 2.7.2.x.
This bug results in the spurious xlint warning above.
No fix for this bug is forthcoming from FSF.
There is a workaround for it in lint1/cgram.y rev 1.2 in 3.0-current.
You need to migrate this file into 2.2-stable.

>How-To-Repeat:

>Fix:
	
Migrate lint1/cgram.y rev 1.2 into 2.2-stable.
This time, please don't close this PR until this is done.
Thanks.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jkoshy 
State-Changed-When: Fri Oct 30 01:55:34 PST 1998 
State-Changed-Why:  
Fixed in rev 1.1.1.1.2.1 of "src/usr.bin/xlint/lint1/cgram.y", thanks! 
Thanks for refiling this PR when 7066 was closed; in general however, 
if a problem is fixed in -current it is treated as `fixed' as the volunteer 
effort needed to track fixes across all the active branches in the source 
tree would otherwise grow rapidly out of control! 
>Unformatted:
