This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New assert in haifa-sched.c
- From: Eric Botcazou <ebotcazou at adacore dot com>
- To: Maxim Kuvyrkov <maxim at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org, Adam Nemet <anemet at caviumnetworks dot com>, abel at ispras dot ru
- Date: Tue, 16 Sep 2008 20:40:52 +0200
- Subject: Re: New assert in haifa-sched.c
- References: <18624.50875.177784.531100@foo.home> <48C14545.5060400@codesourcery.com>
> Yes, the assert is really checking exactly that. Several pieces of
> haifa-sched.c assume that the instruction has been recognized during
> scheduler initialization to speed up checking if instruction is normal
> or some kind of use/clobber/asm.
What happens if an instruction hasn't been recognized upon reaching these
parts of haifa-sched.c? Will it be only mis-scheduled, i.e. will this only
result in inferior, but still correct code? If so, the assertion shouldn't
be enabled in release mode but only if ENABLE_CHECKING is defined.
--
Eric Botcazou