Displaying 5 results from an estimated 5 matches for "wrto".
Did you mean:
wrt
2006 Jun 20
1
[R] Function hints
[This is not about the feasibility of a "hints" function-- which would
be incredibly useful, but perhaps very very hard to do-- but about some
of the other documentation issues raised in Hadley's post and in
Duncan's reply]
WRTO documentation & code together: for several years, I've successfully
used the 'mvbutils' package to keep every function definition & its
documentation together, editing them together in the same file--
function first, then documentation in plain-text (basically the format
you see...
2006 Jun 20
2
Documentation issues [Was: Function hints]
...Bravington at csiro.au> 06/20/06 01:43am >>>
[This is not about the feasibility of a "hints" function-- which would
be incredibly useful, but perhaps very very hard to do-- but about some
of the other documentation issues raised in Hadley's post and in
Duncan's reply]
WRTO documentation & code together: for several years, I've successfully
used the 'mvbutils' package to keep every function definition & its
documentation together, editing them together in the same file--
function first, then documentation in plain-text (basically the format
you see...
2009 Aug 04
0
[LLVMdev] disabling combining load/stores in optimizer.
On Aug 4, 2009, at 12:19 AM, Alireza.Moshtaghi at microchip.com wrote:
> Well, for one thing, our port has no native operation other than 8-bit
> so it does not make sense to promote operations to higher precisions.
> Eventually all those operations will be lowered and the resulting code
> is most likely worse than if it was not promoted in the first place.
> So
> I think it
2009 Aug 04
2
[LLVMdev] disabling combining load/stores in optimizer.
> > We are currently doing this, however I think disabling such
> > optimizations is a much better solution.
>
> An LLVM design goal is that backends should be able to outsmart
> instcombine when necessary, rather than having instcombine be able
> to disable parts of itself in order to avoid foiling the backends.
> Practicality sometimes steers elsewhere of course.
2009 Aug 04
4
[LLVMdev] disabling combining load/stores in optimizer.
...ortion of the
> optimization suite is unlikely at best, to be honest.
>
I can see the benefits of this approach at a macro-level, however at
micro-level the impact is visible especially in embedded targets with
limited memory and register resources (such as pic16)
We see the impact not only wrto code quality but also compile time (to
recover the damage that the optimizer has done). The other problem is
that our port never seem to be stable because as such generic
optimizations get added, something new will break in our port and as
more and more higher end targets are being ported to llvm I...