Re: [Flex-devel] Spurious compiler warning when building PostgreSQL

[Peter G. <pe...@2n...>]

On 15 August 2011 22:59, Peter Martini <pet...@gm...> wrote:
> Can you confirm scan.c was regenerated?  I believe if postgres doesn't find a supported flex it uses the one included in the postgresql source instead of regenerating it.  There's a check in configure to see if flex $1 = 2 and $2 = 5 and $3 >= 31 which should be == in both places and also add a check if $1 == 2 && $2 > 5.
>

Forgive me. scan.c was not regenerated, despite a "make distclean". I
have manually rm'd scan.c, and tried again. However, the warning is
still seen, in exactly the same context:

/* yy_try_NUL_trans - try to make a transition on the NUL character
 *
 * synopsis
 *      next_state = yy_try_NUL_trans( current_state );
 */
    static yy_state_type yy_try_NUL_trans  (yy_state_type
yy_current_state , yyscan_t yyscanner)
{
        register int yy_is_jam;
    struct yyguts_t * yyg = (struct yyguts_t*)yyscanner; /* This var
may be unused depending upon options. */

        register int yy_c = 256;
        register yyconst struct yy_trans_info *yy_trans_info;

        yy_trans_info = &yy_current_state[(unsigned int) yy_c];
        yy_current_state += yy_trans_info->yy_nxt;
        yy_is_jam = (yy_trans_info->yy_verify != yy_c);

        return yy_is_jam ? 0 : yy_current_state;
}

Thanks

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services