[llvm-dev] CodeExtractor buggy?
Florian Hahn via llvm-dev
llvm-dev at lists.llvm.org
Mon Dec 4 02:42:23 PST 2017
On 04/12/2017 08:38, keita abdoul-kader via llvm-dev wrote:
> I second this observation.
>
> On Sun, Dec 3, 2017 at 9:07 AM, serge guelton via llvm-dev
> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>
> On Tue, Nov 28, 2017 at 08:26:18PM -0500, Pei Wang via llvm-dev wrote:
> > Now, because the loop is coalesced into a function, the definition of %.ph (derived from %17 in the previous version of IR) in .loopexit becomes funny: two different incoming values for the same incoming block. I was wondering if this is a bug of CodeExtractor or the extractor makes assumptions about the code to be extracted which I’m not aware of.
>
> From my experience, the CodeExtractor is buggy in various corner
> cases :-/
In order to improve on that, it would be great if you could file bug
reports for the buggy edge cases, to keep track of them :)
Cheers,
Florian
More information about the llvm-dev
mailing list