From: Paul Hilfinger <hilfingr@gnat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: ada vs identical flex
Date: Fri, 08 Oct 2004 11:00:00 -0000 [thread overview]
Message-ID: <20041008102741.322A7F29FF@nile.gnat.com> (raw)
> For yyrealloc, I'm finding that some cases are wrapped in #ifndef
> YY_USES_REJECT, while others are not vis:
> NBSD FC3
> declaration yes no
> definition yes no
> reference yes yes
> ada_flex_use no no
> On NetBSD, since ada_flex_use tries to refer to a function wrapped in
> #ifndef YY_USE_REJECT (i.e., #ifdef'ed out) the build barfs.
Andrew,
I think I can get rid of the yyrealloc stuff altogether. It seems that
one of the rules in ada-lex is not really used, but causes the non-use
of yyrealloc as a side-effect. If you could, would you try the following
patch with the problematic platform/flex version? Thanks.
Paul Hilfinger
Index: merge.224/gdb/ada-lex.l
--- merge.224/gdb/ada-lex.l Wed, 06 Oct 2004 02:59:24 -0700 hilfingr
+++ merge.224(w)/gdb/ada-lex.l Fri, 08 Oct 2004 03:18:25 -0700 hilfingr
@@ -154,8 +154,6 @@ static int find_dot_all (const char *);
return CHARLIT;
}
-\"{OPER}\"/{WHITE}*"(" { return processId (yytext, yyleng); }
-
<INITIAL>\" {
tempbuf_len = 0;
BEGIN IN_STRING;
@@ -926,5 +924,5 @@ yywrap(void)
typedef void (*dummy_function) ();
dummy_function ada_flex_use[] =
{
- (dummy_function) yyrealloc, (dummy_function) yyunput
+ (dummy_function) yyunput
};
next reply other threads:[~2004-10-08 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 11:00 Paul Hilfinger [this message]
2004-10-09 0:29 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 23:17 Andrew Cagney
2004-10-08 2:32 ` Paul Hilfinger
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=20041008102741.322A7F29FF@nile.gnat.com \
--to=hilfingr@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
/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