Hi,
Commit 235763 removed support for versions of MPFR below 3.1.0 which have
a flat directory structure, however it did not introduce any safety check
for such an unhandled library version present in the tree. Consequently
the system-installed version is silently chosen, which if too old, ca
On 07/22/2016 04:12 PM, Jeff Law wrote:
Working through the new pass... Overall it looks pretty good. There's
a certain level of trust I'll extend WRT getting the low level details
right -- a thorough testsuite obviously helps there.
In the latest patch where I add the return value optimizati
On 08/11/2016 10:59 PM, Andrew Pinski wrote:
On Thu, Aug 11, 2016 at 1:49 PM, Denys Vlasenko wrote:
falign-functions=N is too simplistic.
Ingo Molnar ran some tests and it looks on latest x86 CPUs, 64-byte alignment
runs fastest (he tried many other possibilites).
However, developers are le
On Thu, Aug 11, 2016 at 07:15:17PM -0400, Michael Meissner wrote:
> This patch was originally part of patch #3, but I separated it out as I rework
> what used to be part of patch #3 to fix some issues.
>
> This patch adds support for using the ISA 3.0 MTVSRDD instruction when
> initializing vector
On Thu, Aug 11, 2016 at 5:19 PM, Denys Vlasenko wrote:
>
>
> On 08/11/2016 10:59 PM, Andrew Pinski wrote:
>>
>> On Thu, Aug 11, 2016 at 1:49 PM, Denys Vlasenko
>> wrote:
>>>
>>> falign-functions=N is too simplistic.
>>>
>>> Ingo Molnar ran some tests and it looks on latest x86 CPUs, 64-byte
>>> a
On 08/11/2016 02:34 PM, David Malcolm wrote:
I sometimes find myself scouring assembler output from the compiler
and trying to figure out which instructions correspond to which
lines of source code; I believe this is a common activity for some
end-users.
The following patch adds a new -fasm-show
Hi Richard,
On 11/08/16 20:04, Richard Biener wrote:
On Thu, Aug 11, 2016 at 6:11 AM, kugan
wrote:
[SNIP]
+two_valued_val_range_p (tree var, tree *a, tree *b)
+{
+ value_range *vr = get_value_range (var);
+ if ((vr->type != VR_RANGE
+ && vr->type != VR_ANTI_RANGE)
+ || !range
>
> If sym1 results in a return value that is some useful tree and inv1
> is true and cst1 is true via this call:
The only way for get_single_symbol to return a non NULL tree
is to hit the return at the end -- and that always initializes
inv and neg.
And when the return is NULL the && prevents e
On 08/12/16, Maciej W. Rozycki wrote:
> Hi,
>
> Commit 235763 removed support for versions of MPFR below 3.1.0 which have
> a flat directory structure, however it did not introduce any safety check
> for such an unhandled library version present in the tree. Consequently
> the system-installed v
On 12 August 2016 at 02:04, David Malcolm wrote:
> I sometimes find myself scouring assembler output from the compiler
> and trying to figure out which instructions correspond to which
> lines of source code; I believe this is a common activity for some
> end-users.
Hi David,
I usually use gcc -g
On August 11, 2016 8:41:53 PM GMT+02:00, Jeff Law wrote:
>On 08/11/2016 08:27 AM, Jan Hubicka wrote:
>>
>> On tramp3d all VRP passes threads together 730 branches, all DOM
>passes 393, so
>> FSM threading (with 1957 branches) is the most effective one. Perhaps
>eventually
>> early VRP can also do
101 - 111 of 111 matches
Mail list logo