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]

Re: [PATCH]: New peepholes for 68HC11 and 68HC12


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Kazu,

Kazu Hirata wrote:
| Hi Stephane,
|
|
|>2004-03-02  Stephane Carrez  <stcarrez@nerim.fr>
|>
|>	* config/m68hc11/m68hc11.md (move peephole2): New peepholes to optimize
|>	sequences of moves.
|>	(add peepholes): New peepholes to optimize sequences adding small
|>	constants.
|>	(bset peepholes): New peepholes to transform an OR in a bset form
|>	(bclr peepholes): Likewise for bclr form.
|>	(cmp peepholes): New peepholes to avoid register copies when comparing.
|>
|
|
|>+(define_peephole
|
|
| Do you think you can use peephole2 for this?  Or maybe not as I recall
| that m68hc11 port lowers soft registers into hard registers or
| something in TARGET_MACHINE_DEPENDENT_REORG.
|
| Kazu Hirata
|

No because these 2 particular peepholes operate on insns that are created after
the peephole2 are applied (as result of the Z register replacement that the
machine reorg does).  All other peepholes are peephole2.

	Stephane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFARQ/jNyQxO2LzKT0RAh8uAJ9wqmwuCO0E06I8GPQqCbuI/jncKwCfZoIu
49Dblbdr5lCZ+orTr2EGdn4=
=Pes1
-----END PGP SIGNATURE-----


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