This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Bugs in gcc-2.95.1
- To: HPENNER at de dot ibm dot com
- Subject: Re: Bugs in gcc-2.95.1
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 04 Jan 2000 22:45:07 -0700
- cc: gcc-patches at gcc dot gnu dot org, bezold1 at de dot ibm dot com
- Reply-To: law at cygnus dot com
In message <C125685C.003AD2AC.00@d12mta05.de.ibm.com>you write:
>
> Hello,
> while writing the new gcc backend for Linux for S/390 I found some bug
> s in
> the generic code
> of gcc.
> The (hopefully complete) fixes are included in the bellow appended patchfil
> es.
>
> The bugs are:
>
> reload1.c line 5987:
> A register which is clobbered in an insn (asm) cannot be used as reloa
> d
> register.
> caller-save.c:
> The function 'mark_referenced_regs' does not work properly, not all
> referenced register
> are found. This leads to incorrect restore code, some registers are
> restored at the end
> of the block were the function is called, but used before.
> I tried to fix this completely, but there are still some holes left, s
> ome
> packages need to be
> compiled with -fno-caller-saves
> except.c line 1343:
> assign_stack_local must be called with size+2 and not size+1, because
> jmpbuf starts two
> words into the area allocated.
> flow.c line 1846:
> The function 'can_delete_label_p' should return 0, if label is used.
Unfortunately we can not use any of your patches.
1. No explanation or testcase.
2. Not submitted in the right form (see the web page for
instructions for submitting patches).
http://gcc.gnu.org/contribute.html
3. Diffs against gcc-2.95. The development tree is wildly different from
gcc-2.95.
4. Each patch should be a separate message with a separate testcase
and/or explanation.