public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/6539: 3.2 bootstrap failure on irix6.5 - fixproto Date: Tue, 07 May 2002 22:06:00 -0000 [thread overview] Message-ID: <20020508050601.13983.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/6539; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.demon.co.uk> To: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, ghazi@caip.rutgers.edu Subject: Re: bootstrap/6539: 3.2 bootstrap failure on irix6.5 - fixproto Date: Wed, 8 May 2002 06:01:32 +0100 Billinghurst, David (CRTS) wrote:- > This failure occurs after > > 2002-04-28 Neil Booth <neil@daikokuya.demon.co.uk> > > * cppexp.c (lex): Update to use state.skip_eval. > (struct op): Remove prio and flags members. > (FLAG_BITS, FLAG_MASK, PRIO_SHIFT, EXTRACT_PRIO, EXTRACT_FLAGS, > SHORT_CIRCUIT, RIGHT_ASSOC, ..._PRIO, op_to_prio): Remove. > (LEFT_ASSOC): New macro. > (optab): New table of operator priorities and flags. > (SHIFT): Update. > (_cpp_parse_expr): Clean up logic. Return bool. Use a > malloc-ed parser stack. > (reduce): New; reduce the operator stack. > (_cpp_expand_op_stack): Expand the operator stack as necessary. > * cpphash.h (struct op): Predeclare. > (struct cpp_reader): New members op_stack, op_limit. > (struct lexer_state): New member skip_eval. > (_cpp_parse_expr): Update. > (_cpp_expand_op_stack): New. > * cpplib.c (do_if): Update. > * cppinit.c (cpp_create_reader): Create op stack. > (cpp_destroy): And destroy it. > * cpplib.h (CPP_LAST_CPP_OP): Correct. > (TTYPE_TABLE): Correct. > > Let me know how I can help track this down. Hmm. Dunno. Can you mail me the file that is being fix-header-ed? Neil.
next reply other threads:[~2002-05-08 5:06 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-07 22:06 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-09 19:06 Kaveh R. Ghazi 2002-05-09 17:32 billingd 2002-05-09 15:06 Neil Booth 2002-05-09 14:36 Neil Booth 2002-05-09 14:26 Kaveh R. Ghazi 2002-05-09 13:46 Neil Booth 2002-05-09 13:36 Neil Booth 2002-05-09 13:26 Kaveh R. Ghazi 2002-05-07 22:16 Neil Booth 2002-05-07 20:56 Billinghurst, David (CRTS) 2002-05-07 20:56 Billinghurst, David (CRTS) 2002-05-07 6:06 Kaveh R. Ghazi 2002-05-05 21:26 Kaveh R. Ghazi 2002-05-02 16:06 Billinghurst, David (CRTS) 2002-05-02 3:06 Jakub Jelinek 2002-05-01 21:06 Billinghurst, David (CRTS) 2002-05-01 19:26 David.Billinghurst
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=20020508050601.13983.qmail@sources.redhat.com \ --to=neil@daikokuya.demon.co.uk \ --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: linkBe 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).