This is the mail archive of the gcc-bugs@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]

Re: Your change





On Sat, 18 Mar 2000, Mark Mitchell wrote:

> 
> Jason --
> 
>   Sat Mar 18 14:38:00 2000  Jason Eckhardt  <jle@cygnus.com>
> 
> 	* bb-reorder.c (reorder_basic_blocks): Update PREV_INSN as well as
> 	NEXT_INSN. Update last insn in chain.
> 
> This change broke g++.jason/inline3.C on i686-pc-linux-gnu.
> 
> 

  Please tell me what flags you used, etc. I am unable to reproduce
  this with the latest CVS tree including my change:

FAIL: g++.dg/special/conpr-1.C execution test
FAIL: g++.dg/special/conpr-2.C execution test
FAIL: g++.dg/special/conpr-3.C execution test
FAIL: g++.dg/special/conpr-3.C execution test
FAIL: g++.eh/crash3.C caused compiler crash
FAIL: g++.ext/initp1.C  Execution test
FAIL: g++.oliva/template7.C caused compiler crash
FAIL: g++.pt/memtemp64.C (test for excess errors)

		=== g++ Summary ===

# of expected passes		5795
# of unexpected failures	8
# of expected failures		90
# of untested testcases		8
/home/jle/trees/egcs_bp/b1/gcc/testsuite/../g++ version 2.96 20000318 (experimental)


BTW, are you testing with -freorder-blocks always (that is the only way you
could have exercised this code path)? While I do want any
feedback on problems, it is still considered preliminary code. It probably
should not be part of nightly testing (yet).

jason.


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