Displaying 7 results from an estimated 7 matches for "r173176".
2013 Mar 12
0
[LLVMdev] Help needed on debugging llvm
...r is not fixed yet (even with fix mentioned in PR15040
http://llvm.org/bugs/show_bug.cgi?id=15040#c4)
With the updated trunk, clang still gives an error when FMA4 is
enabled but does fine when -no-integrated-as is used. So that's a bug
with LLVM's integrated assembler.
On a related note, r173176 mentioned in
http://llvm.org/bugs/show_bug.cgi?id=15282 does not fix the gromacs
miscompare error either. However -no-integrated-as helps in all cases.
I am not sure if r173176 is incomplete or the issue is something else.
-Anitha
>
> On Mon, Mar 11, 2013 at 4:49 AM, Anitha B Gollamud...
2013 Mar 13
1
[LLVMdev] Help needed on debugging llvm
...mentioned in PR15040
> http://llvm.org/bugs/show_bug.cgi?id=15040#c4)
>
> With the updated trunk, clang still gives an error when FMA4 is
> enabled but does fine when -no-integrated-as is used. So that's a bug
> with LLVM's integrated assembler.
>
> On a related note, r173176 mentioned in
> http://llvm.org/bugs/show_bug.cgi?id=15282 does not fix the gromacs
> miscompare error either. However -no-integrated-as helps in all cases.
>
> I am not sure if r173176 is incomplete or the issue is something else.
>
>
>
> -Anitha
>
>
> >
> &...
2013 Mar 12
2
[LLVMdev] Help needed on debugging llvm
I'm still slightly confused. Is the error now fixed or is there still a bug
in LLVM's integrated assembler?
On Mon, Mar 11, 2013 at 4:49 AM, Anitha B Gollamudi <
anitha.boyapati at gmail.com> wrote:
> On 11 March 2013 17:00, Duncan Sands <baldrick at free.fr> wrote:
> > Hi Anitha,
> >
> >
> >> Ah, I am taking back my above words w.r.t encoding.
2013 Mar 11
2
[LLVMdev] Help needed on debugging llvm
...2013 10:06, Anitha B Gollamudi <anitha.boyapati at gmail.com> wrote:
> On 23 January 2013 00:20, Craig Topper <craig.topper at gmail.com> wrote:
>>
>> Are you still having issues with FMA4? I wonder if PR15040 is related. A
>> fix was just committed.
Unfortunately r173176 does not fix this. I have updated the trunk and
ran...Miscompare still persists.
Going by http://llvm.org/bugs/show_bug.cgi?id=14185#c12 , I am
inclined to think that it is an optimization. (If it is an encoding
issue, dragonegg would have failed as well...). or maybe I am missing
something here....
2013 Mar 11
0
[LLVMdev] Help needed on debugging llvm
...lamudi <anitha.boyapati at gmail.com> wrote:
>> On 23 January 2013 00:20, Craig Topper <craig.topper at gmail.com> wrote:
>>>
>>> Are you still having issues with FMA4? I wonder if PR15040 is related. A
>>> fix was just committed.
>
> Unfortunately r173176 does not fix this. I have updated the trunk and
> ran...Miscompare still persists.
>
> Going by http://llvm.org/bugs/show_bug.cgi?id=14185#c12 , I am
> inclined to think that it is an optimization. (If it is an encoding
> issue, dragonegg would have failed as well...). or maybe I am...
2013 Jan 22
1
[LLVMdev] Help needed on debugging llvm
Are you still having issues with FMA4? I wonder if PR15040 is related. A
fix was just committed.
On Wed, Nov 7, 2012 at 3:22 AM, Anitha Boyapati
<anitha.boyapati at gmail.com>wrote:
>
>
> On 7 November 2012 15:29, Duncan Sands <baldrick at free.fr> wrote:
>
>>
>> That way the output should be exactly the same as the output dragonegg
>> would
>>
2013 Mar 11
0
[LLVMdev] Help needed on debugging llvm
On 23 January 2013 00:20, Craig Topper <craig.topper at gmail.com> wrote:
>
> Are you still having issues with FMA4? I wonder if PR15040 is related. A
> fix was just committed.
It seems to be so! I will look into it immediately.
Apologies for the late e-mail. I ran out of time devoted for this PR
and moved on. Coincidentally, only today I came back to this PR for
further