public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: James Michael DuPont <mdupont777@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8235: Problem compiling gengtype-yacc.y with bison
Date: Thu, 31 Oct 2002 23:46:00 -0000	[thread overview]
Message-ID: <20021101074602.8631.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/8235; it has been noted by GNATS.

From: James Michael DuPont <mdupont777@yahoo.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: Joe Buck <Joe.Buck@synopsys.COM>, gcc-gnats@gcc.gnu.org,
  gcc-bugs@gcc.gnu.org
Subject: Re: c/8235: Problem compiling gengtype-yacc.y with bison
Date: Thu, 31 Oct 2002 23:43:22 -0800 (PST)

 --- Joe Buck <jbuck@synopsys.com> wrote:
 > 
 > > It is very simple,
 > > the problem is that the newest version of bison chokes on the gcc
 > > gengtype-yacc.y code. This silly bug tracker... 
 > > 
 > > Are you sure i did not send you anything usfull?
 > 
 > I've been testing the branch, and it has no file by that name,
 > evidently
 > you are referring to the gcc code on the trunk.
 > 
 > Could you please send a group reply to this message, saying:
 > 
 > 1) exactly which gcc version you tested;
 > 2) what bison version;
 > 3) the error output
 
 Even if the ast-optimizer is broken, 
 here is the bug report 
 
 Bison version  : unstable 1.75-1, this is the problem 
 but it i working with the stable 1.35-3.
 
 The file in question is
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/gengtype-yacc.y
 
 The error output got lost, I will retry it with the main branch was
 about this construction
 typedef_struct: ENT_TYPEDEF_STRUCT options '{' struct_fields '}' ID
 		   {
 		     new_structure ($1->u.s.tag, UNION_P ($1), &lexer_line,
 				    $4, $2);
 		     do_typedef ($6, $1, &lexer_line);
 		     lexer_toplevel_done = 1;
 		   }
 		 ';'
 		   {}
 		| ENT_STRUCT options '{' struct_fields '}'
 		   {
 		     new_structure ($1->u.s.tag, UNION_P ($1), &lexer_line,
 				    $4, $2);
 		     lexer_toplevel_done = 1;
 		   }
 		 ';'
 		   {}
 		;
 
 
 there was some conflict between the two.
 I am just compiling the new bison locally to avoid de-installing 1.35,
 and will report the exact bug tonight (Timezone: GMT +1 )
 
 I will also be looking into doing the switch over to the tree simplied
 version. it looks interesting.
 
 Mike
 
 
 
 
 
 
 
 =====
 James Michael DuPont
 http://introspector.sourceforge.net/
 
 __________________________________________________
 Do you Yahoo!?
 HotJobs - Search new jobs daily now
 http://hotjobs.yahoo.com/


             reply	other threads:[~2002-11-01  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 23:46 James Michael DuPont [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 22:14 neroden
2002-10-31 16:56 Pop Sébastian
2002-10-31 15:16 Joe Buck
2002-10-31 15:10 jbuck
2002-10-31 15:06 Joe Buck
2002-10-31 15:06 James Michael DuPont
2002-10-31 14:46 Joe Buck
2002-10-31 14:39 jbuck
2002-10-15 14:26 mdupont777

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021101074602.8631.qmail@sources.redhat.com \
    --to=mdupont777@yahoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).