[llvm] r247700 - 80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC...

[Sanjay Patel via llvm-commits]

Heh...not sure how that happened. :)
80-cols or bust!

On Tue, Sep 15, 2015 at 9:28 AM, Aaron Ballman <aaron at aaronballman.com>
wrote:

> On Tue, Sep 15, 2015 at 11:26 AM, Sanjay Patel via llvm-commits
> <llvm-commits at lists.llvm.org> wrote:
> > Author: spatel
> > Date: Tue Sep 15 10:26:25 2015
> > New Revision: 247700
> >
> > URL: http://llvm.org/viewvc/llvm-project?rev=247700&view=rev
> > Log:
> > 80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols; NFC80-cols;
> NFC80-cols; NFC80-cols; NFC
>
> I'm confused, is this an 80-col, NFC fix? ;-)
>
> ~Aaron
>
> >
> > Modified:
> >     llvm/trunk/lib/Analysis/InlineCost.cpp
> >
> > Modified: llvm/trunk/lib/Analysis/InlineCost.cpp
> > URL:
> http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Analysis/InlineCost.cpp?rev=247700&r1=247699&r2=247700&view=diff
> >
> ==============================================================================
> > --- llvm/trunk/lib/Analysis/InlineCost.cpp (original)
> > +++ llvm/trunk/lib/Analysis/InlineCost.cpp Tue Sep 15 10:26:25 2015
> > @@ -967,13 +967,14 @@ bool CallAnalyzer::analyzeBlock(BasicBlo
> >      if (isa<ExtractElementInst>(I) || I->getType()->isVectorTy())
> >        ++NumVectorInstructions;
> >
> > -    // If the instruction is floating point, and the target says this
> operation is
> > -    // expensive or the function has the "use-soft-float" attribute,
> this may
> > -    // eventually become a library call.  Treat the cost as such.
> > +    // If the instruction is floating point, and the target says this
> operation
> > +    // is expensive or the function has the "use-soft-float" attribute,
> this may
> > +    // eventually become a library call. Treat the cost as such.
> >      if (I->getType()->isFloatingPointTy()) {
> >        bool hasSoftFloatAttr = false;
> >
> > -      // If the function has the "use-soft-float" attribute, mark it as
> expensive.
> > +      // If the function has the "use-soft-float" attribute, mark it as
> > +      // expensive.
> >        if (F.hasFnAttribute("use-soft-float")) {
> >          Attribute Attr = F.getFnAttribute("use-soft-float");
> >          StringRef Val = Attr.getValueAsString();
> >
> >
> > _______________________________________________
> > llvm-commits mailing list
> > llvm-commits at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150915/b1024c45/attachment.html>