This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] fix 20031201-1.c breakage


Hi,

We have a new FAIL on mainline:
FAIL: gcc.dg/20031201-1.c (test for excess errors)

This happens because we need to run reg_scan() after GCSE before
initializing alias analysis.  With the options for this test case,
this doesn't happen.

Bootstrapped & tested on i686-pc-linux-gnu.  OK?

Gr.
Steven

	* toplev.c (rest_of_handle_cfg): Call reg_stack() before
	initializing alias analysis for mark_constant_funcion ().
Index: toplev.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/toplev.c,v
retrieving revision 1.858
diff -c -3 -p -r1.858 toplev.c
*** toplev.c	5 Jan 2004 09:35:05 -0000	1.858
--- toplev.c	5 Jan 2004 21:30:22 -0000
*************** rest_of_handle_cfg (tree decl, rtx insns
*** 2505,2512 ****
    if (rtl_dump_file)
      dump_flow_info (rtl_dump_file);
    if (optimize)
!     cleanup_cfg (CLEANUP_EXPENSIVE
! 		 | (flag_thread_jumps ? CLEANUP_THREADING : 0));
  
    /* It may make more sense to mark constant functions after dead code is
       eliminated by life_analysis, but we need to do it early, as -fprofile-arcs
--- 2505,2515 ----
    if (rtl_dump_file)
      dump_flow_info (rtl_dump_file);
    if (optimize)
!     {
!       cleanup_cfg (CLEANUP_EXPENSIVE
! 		   | (flag_thread_jumps ? CLEANUP_THREADING : 0));
!       reg_scan (insns, max_reg_num (), 1);
!     }
  
    /* It may make more sense to mark constant functions after dead code is
       eliminated by life_analysis, but we need to do it early, as -fprofile-arcs


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]