I am pleased to announce that the GCC Steering Committee has
appointed Jan Hubicka as GCC IPA Maintainer and LTO Reviewer. Honza
has been the maintainer of the components of IPA and this appointment
clarifies his role.
Please join me in congratulating Honza on his new role.
Honza,
Today I find that function haifa_change_pattern also will call function
update_insn_after_change.
/* Change pattern of INSN to NEW_PAT. Invalidate cached haifa
instruction data. */
static bool
haifa_change_pattern (rtx_insn *insn, rtx new_pat)
{
int t;
t = validate_change (insn, &PATTER
Snapshot gcc-9-20200425 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20200425/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Sat, 25 Apr 2020, Eric Botcazou wrote:
> > I very much disagree with this. I think my approach was possibly the
> > only viable one, and definitely the most sensible one for this target.
> > Not only is there nothing meaningful to be gained from separating cc
> > setters and users on m68k given
> I very much disagree with this. I think my approach was possibly the
> only viable one, and definitely the most sensible one for this target.
> Not only is there nothing meaningful to be gained from separating cc
> setters and users on m68k given that almost all instructions (including
> moves) c
On 4/23/20 8:31 AM, Eric Botcazou wrote:
Thanks, I will take a look at Bernd's work. IIRC, he took a
different approach from what was suggested in the wiki, right?
Yes, let's say that it's a half-baked conversion, probably a consequence of
the bounty. This might be good enough, depending on th
