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

Re: Impact assessment of dse.c:emit_inc_dec_insn_before (Was: Re: Use of FLAGS_REGNUM clashes with generates insn)

From: DJ Delorie <dj at redhat dot com>
To: Joern Rennecke <amylaar at spamcop dot net>
Cc: gcc at gcc dot gnu dot org
Date: Tue, 25 Oct 2011 21:55:19 -0400
Subject: Re: Impact assessment of dse.c:emit_inc_dec_insn_before (Was: Re: Use of FLAGS_REGNUM clashes with generates insn)
References: <j5fv45$ge7$1@dough.gmane.org> <20110923032116.4fzwmhwd44ckgwwk-nzlynne@webmail.spamcop.net> <alpine.BSF.2.00.1110170004190.39960@dair.pair.com> <20111018062749.ff87vnia88g0kkc8-nzlynne@webmail.spamcop.net> <20111025202444.4fr6ofn1kogkc0co-nzlynne@webmail.spamcop.net>

> m32c.c:m32c_legitimate_address_p allows any rubbish inside a
> PRE_MODIFY, as long as the address register is the stack pointer.
> OTOH, it does not define any HAVE_*_MODIFY_* macro.

m32c has push/pop and no other pre/post modify

Follow-Ups:
- Re: Impact assessment of dse.c:emit_inc_dec_insn_before (Was: Re: Use of FLAGS_REGNUM clashes with generates insn)
  - From: Joern Rennecke

References:
- Re: Use of FLAGS_REGNUM clashes with generates insn
  - From: Hans-Peter Nilsson
- Re: Use of FLAGS_REGNUM clashes with generates insn
  - From: amylaar
- Impact assessment of dse.c:emit_inc_dec_insn_before (Was: Re: Use of FLAGS_REGNUM clashes with generates insn)
  - From: Joern Rennecke

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