On 04/14/2014 10:32 AM, Marek Polacek wrote:
> + if (TREE_CODE (val) != IDENTIFIER_NODE
> + && TREE_CODE (val) != FUNCTION_DECL)
> + val = default_conversion (val);
> + else if (TREE_CODE (val) == IDENTIFIER_NODE)
> + {
> + tree t = lookup_name (val);
> + if (t &
Thomas Schwinge, le Wed 09 Apr 2014 09:36:42 +0200, a écrit :
> Well, the first step is to verify that TARGET_THREAD_SPLIT_STACK_OFFSET
> and similar configury is correct for the Hurd,
I have added the corresponding field, so we can just use the same offset
as on Linux.
Samuel
The alignment code in final.c uses some heuristics to decide what alignment a
block must be given. For the loop alignment, it's:
/* In case block is frequent and reached mostly by non-fallthru edge,
align it. It is most likely a first block of loop. */
An immediate counter-exa
Hi,
On 04/16/2014 05:47 PM, Rüdiger Sonderfeld wrote:
+ template
Please avoid _ + Uppercase, those are badnames for many targets.
Normally we add a p at the end. Also, I would mention in a comment the
front-end bug preventing a much more straightforward implementation.
Thanks,
Paolo.
.. also, per the GNU conventions, ? of a conditional expression should
be at the beginning of a line (not at the end of the previous one).
Paolo.
Thanks, Paolo!
On Wed, Apr 16, 2014 at 02:45:28PM -0600, Jeff Law wrote:
> Isn't the problem that operands 1 is a MEM which use the same register
> as operands 3 in the memory address?
Yes, exactly.
> ISTM either removing the memory constraint entirely, or splitting it off
> into a separate alternative and on
> Thanks, I was wrong about that.
>
> Then I think we should just bite the bullet and provide the new
> behaviour. If we do have an abi_tag on those types in the next release
> then we can preserve the old behaviour in the old ABI and use the
> C++11 semantics for the abi_tagged type, which will be
Doing some work on the msp430 failures, I discovered that this patch:
> --- gcc/expmed.c.jj 2013-05-07 10:26:46.0 +0200
> +++ gcc/expmed.c 2013-05-11 09:11:54.087412982 +0200
> @@ -2181,14 +2182,22 @@ expand_shift_1 (enum tree_code code, enu
> rtx temp1;
>
>
Hi,
the testcase shows problem where cpp implicit alias is always inline and
symtab_remove_unreachable_nodes removes the body of aliased function before
inlininghappens. The real problem is that cgraph_state is set too early
and not as the comment says after inlinig, but for release branch I think
Hi,
this is stand alone testcase for that PR.
Comitted to mainline.
PR lto/60820
* gcc.dg/lto/pr60820_0.c: New testcase.
* gcc.dg/lto/pr60820_1.c: New testcase.
Index: testsuite/gcc.dg/lto/pr60820_1.c
Hi,
this patch is a revision of the patch I proposed for BINFO_ABSTRACT_P.
Basically it teaches ipa-devirt that CXX destructors are never called for types
in construction and it also makes it to properly handle vtables of types that
may not have instance. In this case we need to consider them only
On Wed, Apr 16, 2014 at 4:51 PM, Pat Haugen wrote:
> Updated patch with above comments incorporated. Bootstrap/regtest on BE/LE
> with no new regressions. Ok for trunk?
2014-04-08 Pat Haugen
* config/rs6000/rs6000.md (addti3, subti3): New.
gcc/testsuite:
* gcc.target/powerpc
> GCOT_TOOL needs to use this function to read the string in gcda file
> to memory to construct gcov_info objects.
> As you noticed, gcov runtime does not need this interface. But
> gcov-tool links with gcov runtime and it also uses the function.
> We could make it available in gcov_runtime, but th
> From: Richard Biener [mailto:richard.guent...@gmail.com]
>
> With handling only the outermost handled-component and then only a
> selected subset you'll catch many but not all cases. Why not simply
> use get_inner_reference () here (plus stripping the constant offset
> from an innermost MEM_REF
On 03/18/14 04:13, bin.cheng wrote:
Hi,
After control flow graph change made by
http://gcc.gnu.org/ml/gcc-patches/2014-02/msg01492.html, case
gcc.dg/tree-ssa/ssa-dom-thread-4.c is broken on logical_op_short_circuit
targets including cortex-m3/cortex-m0.
The regression reveals a missed opportunity
On 03/26/14 17:44, Teresa Johnson wrote:
Recently I discovered that the profile updates being performed by jump
threading were incorrect in many cases, particularly in the case where
the threading path contains a joiner. Some of the duplicated
blocks/edges were not getting any counts, leading to
Thanks!
> I'd actually do this down at the gimple level. You'll have an SSA graph you
> can use to identify the masking and verify its producing a single bit result.
> You'll also have canonicalized comparisons, so there'll be fewer things to
> test. Depending on exactly where you put the op
Hi,
while compiling firefox I noticed that -fprofile-generage -flto goes to 8GB.
It turns out that this is caused by ipa_reference no longer being disabled
becaus in_lto_p became flag that is set later (it is not clear to me why it
needs to be this way).
I however do not see reason why not disable
101 - 119 of 119 matches
Mail list logo