search for: pr15040

On 12 March 2013 09:51, Craig Topper <craig.topper at gmail.com> wrote: > I'm still slightly confused. Is the error now fixed or is there still a bug > in LLVM's integrated assembler? > The error 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...

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 ou...

...> On 12 March 2013 09:51, Craig Topper <craig.topper at gmail.com> wrote: > > I'm still slightly confused. Is the error now fixed or is there still a > bug > > in LLVM's integrated assembler? > > > > The error 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...

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 debugging. Thanks! > > On Wed, Nov 7, 2012 at 3...

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.

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 > normally run the LLVM optimizers on, e.g. GCC constant folding and other > such > optimizations which get turned on at -O2 will still have happened > (dragonegg > turns off almost all GCC optimizations by default,

On 11 March 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...

...t;anitha.boyapati at gmail.com> wrote: > On 11 March 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...