This is the mail archive of the
mailing list for the GCC project.
Re: porting to lra
- From: Vladimir Makarov <vmakarov at redhat dot com>
- To: shmeel gutl <shmeelgutl at shmuelhome dot mine dot nu>, gcc at gcc dot gnu dot org
- Date: Mon, 24 Aug 2015 14:14:39 -0400
- Subject: Re: porting to lra
- Authentication-results: sourceware.org; auth=none
- References: <55DB65D5 dot 7080408 at shmuelhome dot mine dot nu>
On 08/24/2015 02:43 PM, shmeel gutl wrote:
Unfortunately, switching from reload to LRA can be a difficult task.
Reload pass is driven by many machine target hooks. As LRA uses
different algorithms these hooks might be misleading for it.
are there any guidelines as to what needs to be done in the backend to
enable lra for 5.2?
I did several LRA ports and they had different problems and changes were
made in different code of machine-dependent files. I can say only that
porting mostly needs to rework (sometimes to switch off) hooks used by
reload. Sometimes very small changes in hooks are necessary, sometimes
it needs a lot of changes (powerpc required the biggest efforts as the
port uses a lot of tricks).
when I turn it on I get two types of errors. 1) insn
not recognized because fp hasn't been converted yet, and 2) max number
of generated reload insns.
any pointers will be appreciated
Could I ask you what target you are trying to port to LRA. I can look
at it and evaluate how many efforts will be needed to do the port.