This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, middle-end - RTL]: scheduling, UNSPEC_VOLATILEs should also represent insn blockage for insns with mem only operands
Uros Bizjak <ubizjak@gmail.com> writes:
> This was in fact done intentionally. I think that inside volatile asm
> statements, it is quite well described, what the statement is doing,
> and adding memory to the list of clobbers intuitively follows this
> description. OTOH, the unspec_volatile instructions are modelling
> something that can't be well described, i.e. the instruction changes
> some global machine state that isn't modelled in the machine
> description.
Your patch for UNSPEC_VOLATILE is OK.
Thanks.
Ian
- References:
- [PATCH, middle-end - RTL]: scheduling, UNSPEC_VOLATILEs should also represent insn blockage for insns with mem only operands
- Re: [PATCH, middle-end - RTL]: scheduling, UNSPEC_VOLATILEs should also represent insn blockage for insns with mem only operands
- Re: [PATCH, middle-end - RTL]: scheduling, UNSPEC_VOLATILEs should also represent insn blockage for insns with mem only operands
- Re: [PATCH, middle-end - RTL]: scheduling, UNSPEC_VOLATILEs should also represent insn blockage for insns with mem only operands
- Re: [PATCH, middle-end - RTL]: scheduling, UNSPEC_VOLATILEs should also represent insn blockage for insns with mem only operands