Displaying 4 results from an estimated 4 matches for "r96265".
2010 Feb 15
2
[LLVMdev] Botched Build
On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote:
> David Greene <dag at cray.com> writes:
> > Sorry, I botched a commit and broke the build. I've just committed a
> > fix.
> >
> > So expect to see some buildbot churning.
>
> Don't hurry. A buildbot already decided that I am the only culprit of
> the breakage. :-/
Hmm...given that
2010 Feb 15
0
[LLVMdev] Botched Build
...on't hurry. A buildbot already decided that I am the only culprit of
>> the breakage. :-/
>
> Hmm...given that MC/AsmParser/X86/x86_32-encoding.s has been failing
> for a while, maybe someone should mark it XFAIL?
It passed for me until you applied your patch, I reverted it in r96265.
-Chris
2010 Feb 15
2
[LLVMdev] Botched Build
...already decided that I am the only culprit of
>>> the breakage. :-/
>>
>> Hmm...given that MC/AsmParser/X86/x86_32-encoding.s has been failing
>> for a while, maybe someone should mark it XFAIL?
>
> It passed for me until you applied your patch, I reverted it in r96265.
FWIW, this is because you broke the encoding of an instruction in your patch. This is incorrect:
+def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst, VR128:$src),
+ "movntdq\t{$src, $dst|$dst, $src}",
+ [(alignednontemporalstore...
2010 Feb 15
0
[LLVMdev] Botched Build
...he only culprit of
> >>> the breakage. :-/
> >>
> >> Hmm...given that MC/AsmParser/X86/x86_32-encoding.s has been failing
> >> for a while, maybe someone should mark it XFAIL?
> >
> > It passed for me until you applied your patch, I reverted it in r96265.
>
> FWIW, this is because you broke the encoding of an instruction in your
> patch. This is incorrect:
>
> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst,
> VR128:$src), + "movntdq\t{$src, $dst|$dst, $src}",
> +...