From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30101 invoked by alias); 29 Sep 2002 20:59:28 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 30090 invoked from network); 29 Sep 2002 20:59:27 -0000 Received: from unknown (HELO windlord.stanford.edu) (171.64.13.23) by sources.redhat.com with SMTP; 29 Sep 2002 20:59:27 -0000 Received: (qmail 1421 invoked by uid 50); 29 Sep 2002 20:59:27 -0000 To: gcc@gcc.gnu.org Subject: Re: module level flags References: <20020929201031.DB673F2D5D@nile.gnat.com> <3D9761E6.8E3A4210@pacbell.net> In-Reply-To: <3D9761E6.8E3A4210@pacbell.net> (Bruce Korb's message of "Sun, 29 Sep 2002 13:26:14 -0700") From: Russ Allbery Organization: The Eyrie Date: Sun, 29 Sep 2002 14:05:00 -0000 Message-ID: User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Honest Recruiter, sparc-sun-solaris2.6) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-09/txt/msg01221.txt.bz2 Bruce Korb writes: > On which platform? The answer is: it depends. > On my particular platform, the compliler "t_word". > It has previously seen, "typedef int t_word;". > On my Solaris 2.8 box, it would be a 64 bit sized bucket. It sounds like your yacc source file is missing a %union directive. If you add one and make the corresponding changes to your source code, I believe that gcc will understand what you're intending to do because the result will be correct C code. This was how I was taught to write yacc parsers nearly ten years ago. It's certainly not a new concept. -- Russ Allbery (rra@stanford.edu)