This is the mail archive of the gcc@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: Help on loop peeling

From: Eric Fisher <joefoxreal at gmail dot com>
To: Sebastian Pop <sebpop at gmail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 17 Aug 2009 16:44:29 +0800
Subject: Re: Help on loop peeling
References: <d6afecde0908130202n2ea34c04ub26c7e08d073326f@mail.gmail.com> <cb9d34b20908130741y2bf009bfwa67d2999c8ac6ed4@mail.gmail.com> <d6afecde0908140320g4bbf5fc6m367530f9892ab92@mail.gmail.com> <cb9d34b20908141002j2ea383cfi51338eae01bfc18c@mail.gmail.com>

2009/8/15 Sebastian Pop <sebpop@gmail.com>:

> You should put a TODO_update_ssa in the flags of prefetching pass.
> With the attached patch I don't see an error.

Thanks. Finally, I figure out that it's because that after copying the
loop, I should have created a preheader to ensure that new_loop's
preheader has only one successor.

> Also, why don't you use trunk for your developments?

I will use trunk when it's ready and able to be committed. For now, I
just begin to try implementing and testing. :-)

Eric

References:
- Help on loop peeling
  - From: Eric Fisher
- Re: Help on loop peeling
  - From: Sebastian Pop
- Re: Help on loop peeling
  - From: Eric Fisher
- Re: Help on loop peeling
  - From: Sebastian Pop

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