19 GCC regressions, 16 new, with your patch on 2003-07-01T21:17:02Z.

[Mark Mitchell]

Yes, your patch is OK.  Thanks!

----- Original Message ----- 
From: "Devang Patel" <dpatel@apple.com>
To: "Andrew Pinski" <pinskia@physics.uc.edu>
Cc: <gcc-regression@gcc.gnu.org>; <aj@suse.de>; <bkoz@redhat.com>;
<edelsohn@gnu.org>; <ghazi@caip.rutgers.edu>; <law@redhat.com>;
<mark@codesourcery.com>; <pcarlini@unitus.it>; <roger@eyesopen.com>;
<zack@codesourcery.com>
Sent: Thursday, July 03, 2003 12:17 PM
Subject: Re: 19 GCC regressions, 16 new, with your patch on
2003-07-01T21:17:02Z.


> Following patch addresses this failures.
>
> http://gcc.gnu.org/ml/gcc-patches/2003-07/msg00364.html
>
> -Devang
>
> On Tuesday, July 1, 2003, at 7:43 PM, Andrew Pinski wrote:
>
> > I think all of these are caused by Devang Patel's patch:
> > +2003-07-01  Devang Patel  <dpatel@apple.com>
> > +
> > + * dbxout.c (DBXOUT_DECR_NESTING): Emit pending bincls, if required.
> > + (binclstatus): New.
> > + (struct dbx_file): New members - bincl_status, pending_bincl_name and
> > + prev.
> > + (pending_bincls): New.
> > + (dbxout_init): Initialize new dbx_file members.
> > + (dbxout_start_source_file): Same.
> > + (emit_bincl_stab): New function.
> > + (emit_pending_bincls): Same.
> > + (emit_pending_bincls_if_required): Same.
> > + (dbxout_end_source_file): Emit EINCL stab only if BINCL is  already
> > + processed.
> > + (dbxout_begin_block): Emit pending BINCL stabs.
> > + (dbxout_end_block): Same.
> > + (dbxout_function_decl): Same.
> > + (dbxout_continue): Same.
> > + (dbxout_type): Same.
> > + (dbxout_class_name_qualifiers): Same.
> > + (dbxout_symbol): Same.
> > + (dbxout_symbol_location): Same.
> > + (dbxout_parms): Same.
> >
> > they all have an comparison like this one:
> > <       .stabs
> > "/Users/regress/tbox/cvs-gcc/gcc/gcc/testsuite/gcc.dg/pch/decl
> > -3.c",130,0,0,0
> > >       .stabs  "decl-3.h",130,0,0,0
> > FAIL: gcc.dg/pch/decl-3.c -O0 -g assembly comparison
> >
> >
> > On Tuesday, Jul 1, 2003, at 22:10 US/Eastern, GCC regression checker
> > wrote:
> >
> >> With your recent patch, GCC has some regression test failures, which
> >> used to pass.  There are 16 new failures, and 3
> >> failures that existed before and after that patch; 0 failures
> >> have been fixed.
> >>
> >> The new failures are:
> >> native gcc.sum gcc.dg/pch/common-1.c
> >> native gcc.sum gcc.dg/pch/decl-1.c
> >> native gcc.sum gcc.dg/pch/decl-2.c
> >> native gcc.sum gcc.dg/pch/decl-3.c
> >> native gcc.sum gcc.dg/pch/decl-4.c
> >> native gcc.sum gcc.dg/pch/decl-5.c
> >> native gcc.sum gcc.dg/pch/empty.c
> >> native gcc.sum gcc.dg/pch/except-1.c
> >> native gcc.sum gcc.dg/pch/global-1.c
> >> native gcc.sum gcc.dg/pch/inline-1.c
> >> native gcc.sum gcc.dg/pch/macro-1.c
> >> native gcc.sum gcc.dg/pch/macro-2.c
> >> native gcc.sum gcc.dg/pch/macro-3.c
> >> native gcc.sum gcc.dg/pch/static-1.c
> >> native gcc.sum gcc.dg/pch/static-2.c
> >> native gcc.sum gcc.dg/pch/system-1.c
> >>
> >> The old failures, which were not fixed or introduced by your patch,
> >> are:
> >> native g77.sum g77.f-torture/execute/980520-1.f
> >> native gcc.sum gcc.c-torture/execute/20000412-3.c
> >> native gcc.sum gcc.dg/warn-1.c
> >>
> >> For more information, see http://gcc.gnu.org/regtest/.
> >> <ChangeLog.diff>--
> >> Geoffrey Keating <geoffk@apple.com>
> >> (via an automated GCC regression-testing script.)
> >
>
>