Displaying 5 results from an estimated 5 matches for "td37560".
2019 Apr 16
4
Disable combining of loads and stores in instcombine
LLVM's optimizer combines stores to consecutive characters into a write of a single word. For instance, if I have char A[4] and I write some static value to each element, these writes would be combined into a single 32-bit word write. I found this thread from 2009 -- it seems like it wasn't possible then. Has anything changed since?
Neil
-------------- next part --------------
An HTML
2019 Apr 17
3
Disable combining of loads and stores in instcombine
...nsecutive characters into a write of a single word. For instance, if I have char A[4] and I write some static value to each element, these writes would be combined into a single 32-bit word write. I found this thread <http://llvm.1065342.n5.nabble.com/disabling-combining-load-stores-in-optimizer-td37560.html> from 2009 -- it seems like it wasn't possible then. Has anything changed since?
> >
>
> Why do you want to disable this optimization?
>
> -Tom
>
>
> > Neil
> >
> >
> > _______________________________________________
> > LLVM Develop...
2019 Apr 18
2
Disable combining of loads and stores in instcombine
...nsecutive characters into a write of a single word. For instance, if I have char A[4] and I write some static value to each element, these writes would be combined into a single 32-bit word write. I found this thread <http://llvm.1065342.n5.nabble.com/disabling-combining-load-stores-in-optimizer-td37560.html> from 2009 -- it seems like it wasn't possible then. Has anything changed since?
> >
> > Why do you want to disable this optimization?
> >
> > -Tom
> >
> >
> >
> > > Neil
> > >
> > >
> > > ____________________...
2019 Apr 17
5
Disable combining of loads and stores in instcombine
...secutive characters into a write of a single word. For instance, if I have char A[4] and I write some static value to each element, these writes would be combined into a single 32-bit word write. I found this thread <http://llvm.1065342.n5.nabble.com/disabling-combining-load-stores-in-optimizer-td37560.html> from 2009 -- it seems like it wasn't possible then. Has anything changed since?
>
> Neil
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev...
2019 Apr 17
2
Disable combining of loads and stores in instcombine
So, volatile’s been a fine solution — the issue is volatile pointers would perform the load every time; ideally memory accesses would be able to be cached. This is why I’ve been leaning towards disabling the part of instcombine that combines memory accesses instead of using volatile — there should be better performance.
On Apr 17, 2019, 9:54 AM -0700, Jameson Nash <vtjnash at gmail.com>,