Hello!
x86-specific part of this patch was committed to the trunk recently.
There is also target-independent part, which covers memset/memcopy for
the smallest sizes (from 1 to ~256 bytes). In contrast to existing
implementation, it has a cost model to choose the fastest move-mode
(which could be
Hi Jakub et al.,
We prepared a draft for design document for offloading support in GCC - could
you please take a look? It is intended to give a common comprehension of what
is going on in this part.
We might publish it to a GCC wiki, if it is ok. And later we could fill it with
more details if n
Hi Walter,
I faced with similar problem when I worked on optimizing memcpy
expanding for x86.
x86-specific expander also needed alignment info and it was also
incorrect (i.e. too conservative). Routine get_mem_align_offset () is
used there to determine alignment, but after some moment it started to
done adding new subcodes for operations with
rounding shouldn't cause any new fails (as we won't change behavior of
'default' operations).
Michael
On 19 December 2012 03:18, Joseph S. Myers wrote:
> On Fri, 14 Dec 2012, Michael Zolotukhin wrote:
>
>> Currently,
as
something that could change result of FP-operations) and it definitely
needs a test, but I don't see any need in many tests here.
---
Thanks, Michael
On 10 January 2013 22:04, Joseph S. Myers wrote:
> On Thu, 10 Jan 2013, Michael Zolotukhin wrote:
>
>> Thanks for the res
Sure, the tests are of utmost importance here. By the way, in what
suite should they be?
As for the changes in the compiler itself - what do you think about
introduction of a fake variable, reflecting rounding mode (similar
variables could be introduced for exception flags and other
properties). H
