egcs-19990718 ICE for Hitachi SH target
joel@OARcorp.com
joel@OARcorp.com
Tue Aug 31 22:45:00 GMT 1999
On Mon, 2 Aug 1999, Jeffrey A Law wrote:
>
> In message < Pine.LNX.4.10.9908021403430.13457-100000@oar3remote >you write:
> >
> >
> >
> > On Sun, 1 Aug 1999, Jeffrey A Law wrote:
> >
> > >
> > > In message <99072019252700.00333@hallo>you write:
> > > > sh23bug1.i: In function `foo':
> > > > sh23bug1.i:9: continue statement not within a loop
> > > > sh23bug1.i:14: Internal compiler error in `make_edges', at flow.c:967
> > > > Please submit a full bug report.
> > > > See <URL: http://egcs.cygnus.com/faq.html#bugreport > for instructions.
> > > Thanks. I'm installing a fix for this onto the release branch, so these
> > > tests should work fine with gcc-2.95.1 when its released.
> > >
> > > The patch should also fix the newlib/RTEMS builds for the sh.
> >
> > I just checked the cvs web interface and did not notice any recent changes
> > in the gcc/config/sh directory.
> >
> > What did it change?
> Are you sure you were looking on the branch? The patch has been in the
> mainline
> tree for a few weeks. The patch was to sh.c, sh.h & sh.md.
My bad. I thought based on your comment that I was looking for a VERY
recent change. Your comment was simply that you merged it onto the
release branch -- the change itself is from June. I am assuming that this
is the change in question:
Fri Jun 4 03:20:40 1999 J"orn Rennecke <amylaar@cygnus.co.uk>
* sh.c (fixup_addr_diff_vecs): Emit braf reference label.
(braf_label_ref_operand): Delete.
* sh.h (PREDICATE_CODES): Remove braf_label_ref_operand.
* sh.md (casesi_jump_2): Operand1 is now the inside of a
label_ref, and has no predicate.
The patten has a predicate to guard against invalid substitutions.
(dummy_jump): Delete.
(casesi): Update use of casesi_jump_2.
Bring over from the mainline tree.
Sorry. I misread what you said.
--joel
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
More information about the Gcc-bugs
mailing list