> From: Andrew Pinski
> To: Jamie Prescott
> Cc: Ian Lance Taylor ; gcc@gcc.gnu.org
> Sent: Thursday, May 21, 2009 8:22:00 AM
> Subject: Re: nops
>
> On Thu, May 21, 2009 at 8:13 AM, Jamie Prescott wrote:
> > My target does not have anything special WRT alignment.
On Thu, May 21, 2009 at 8:13 AM, Jamie Prescott wrote:
> My target does not have anything special WRT alignment. I even set the
> function
> alignment to 8, and it still issues gen_nop().
> This seem to happen only with -O0, or at least I noticed it only under such
> condition
> so far.
so it h
- Original Message
> From: Ian Lance Taylor
> To: Jamie Prescott
> Cc: gcc@gcc.gnu.org
> Sent: Wednesday, May 20, 2009 9:50:50 PM
> Subject: Re: nops
>
> Jamie Prescott writes:
>
> > Under which conditions GCC generates nops?
>
> It depends entir
Jamie Prescott writes:
> Under which conditions GCC generates nops?
It depends entirely on the target. For many targets, gcc will never
generate a nop instruction, except as a byproduct of alignment.
> I noticed that with 4.4.0, gen_nop() is required, thing that wasn't with
> 4.3.3.
> Can I
"Ling-hua Tseng" <[EMAIL PROTECTED]> writes:
> Because I need to use the feature of `length' attribute (i.e., use
> get_attr_length() in machine description),
> I have to insert NOPs explicitly before performing the pass 58
> (shorten) such that the shorten pass can calculate the length of insns
Sorry.
The example of previous post was wrong.
I just corrected it in this post.
I'm porting GCC 4.1.1 to a VLIW processor.
The processor couldn't solve any hazards itself so we should insert explicit
NOPs after insn scheduling.
I have implemented this functionality in the hook
`TARGET_MACHINE
