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: Remove some of optimize_size checks in i386 backend

From: Paolo Bonzini <bonzini at gnu dot org>
To: Jan Hubicka <jh at suse dot cz>
Cc: gcc-patches at gcc dot gnu dot org
Date: Wed, 06 Aug 2008 13:39:12 +0200
Subject: Re: Remove some of optimize_size checks in i386 backend
References: <20080806080045.GR9952@kam.mff.cuni.cz> <48995E16.3080602@gnu.org> <20080806104620.GT9952@kam.mff.cuni.cz>

It is just post-reload pattern, so I think we are safe here.

I don't think so, because:

1) you can have a non-cached recog in eliminate_regs_in_insn. That recog will change the code of the insn and xor will always be emitted.

2) new instructions generated after reload will always be emitted as xors. it can happen in reload_combine, for example.

Paolo

Follow-Ups:
- Re: Remove some of optimize_size checks in i386 backend
  - From: Jan Hubicka

References:
- Remove some of optimize_size checks in i386 backend
  - From: Jan Hubicka
- Re: Remove some of optimize_size checks in i386 backend
  - From: Paolo Bonzini
- Re: Remove some of optimize_size checks in i386 backend
  - From: Jan Hubicka

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