Hi,
When shrink-wrap is enabled, the "returns" from simple-return path and
normal return path can be merged. The code is like:
tst ...
/ \
| push ...
| ...
| pop ...
\ /
bx lr
If the dwarf info after "pop ..." is incorrect, the dwarf checks will
fail at dwarf
On Wed, Mar 20, 2013 at 11:30:58PM -0600, Jeff Law wrote:
> On 03/20/2013 10:33 AM, Aldy Hernandez wrote:
> >As I'd mentioned, you have .exp files named compile.exp and execute.exp
> >which seem to be causing ambiguity problems in parallel checks (make
> >check -jN). For some reason, with this pat
Jason Merrill writes:
| Previous attempts to build the compiler as C++ had problems with stage
| comparison due to anonymous namespaces having random names. This was
| necessary in the past because of string comparison of type_info names
| on targets that didn't support unification of the nodes
On 03/20/2013 10:33 AM, Aldy Hernandez wrote:
As I'd mentioned, you have .exp files named compile.exp and execute.exp
which seem to be causing ambiguity problems in parallel checks (make
check -jN). For some reason, with this patch, the rest of dg.exp fails
to run after Cilkplus' compile/execu
This was something I spotted while looking at why certain redundant
conditionals were not eliminated. In particular this affects the
compiler's ability to eliminate a variety of gimple checking tests.
Consider an equality comparison
if (a == 10)
true arm
else
else arm
We obviously want
On 03/17/2013 11:45 PM, Jason Merrill wrote:
This patch caused c++/56639: when within a function we were trying to
parse something that could be either a declaration or an expression, we
went to set current_class_ptr and failed the assertion that it wasn't
already set. We could save and restore
While a class is still being defined, we don't know the offsets of the
members, so a pointer-to-member expression can't be lowered to an
integer, it needs to stay as a PTRMEM_CST. But it's still a constant as
far as the language is concerned, so we need to allow it and then lower
it when the c
Previous attempts to build the compiler as C++ had problems with stage
comparison due to anonymous namespaces having random names. This was
necessary in the past because of string comparison of type_info names on
targets that didn't support unification of the nodes for address
comparison, but
And this is a robustness change that I ended up not needing, but still
makes sense.
commit 3099f644d5427e1db3b4041ca4ed779ef213b6a0
Author: Jason Merrill
Date: Tue Mar 19 11:34:46 2013 -0400
* pt.c (retrieve_specialization): Handle null tmpl argument.
diff --git a/gcc/cp/pt.c b/gcc/cp/pt
On 03/17/2013 04:33 PM, Jason Merrill wrote:
On 03/16/2013 03:38 PM, Jason Merrill wrote:
In SFINAE context, we need to instantiate a class so that we can tell
whether or not is abstract. Doing this in non-SFINAE context caused
problems, so I've made it conditional.
But it still causes proble
This patch adds an atomic test and set pattern on tilegx. Without
this pattern, libatomic currently fails to build on tilegx. Do I need
permission to backport this to the 4.8 branch?
Thanks,
Walter
* config/tilegx/sync.md (atomic_test_and_set): New pattern.
Index: gcc/config/tilegx/sy
On 20/03/2013, at 1:35 AM, rbmj wrote:
> On 19-Mar-13 03:04, Maxim Kuvyrkov wrote:
>>
>> Will commit to trunk once the server is up.
The patch is now committed.
>>
>> Regarding 4.8, we should've really tried to work it out earlier. If you
>> want to pursue backport to 4.8, please attach the
HI Aldy, Joseph et al.,
Attached, please find a fixed patch. Please see my responses to Aldy's
questions below:
> -Original Message-
> From: Aldy Hernandez [mailto:al...@redhat.com]
> Sent: Wednesday, March 20, 2013 12:33 PM
> To: Joseph S. Myers
> Cc: Iyer, Balaji V; gcc-patches
Hi Richard,
I'm sorry for wasting your time. I accidentally posted an older version of the
patch earlier this afternoon.
This is the version that I meant to post and is hopefully a lot closer to what
you are looking for.
I named some of the predicates/constraints differently than your current
s
Thanks for the prompt review!
On Tue, Mar 19, 2013 at 7:30 PM, Tobias Burnus wrote:
> Am 19.03.2013 13:15, schrieb Janne Blomqvist:
>
>> now that the Fortran frontend is C++ we can use the primitive bool
>> type instead of inventing our own.
>
>
> Well, C99's "bool" (_Bool) was already used befor
I have found some little nits that I will point out in a reply to this
message.
Balaji:
In Joseph's review on October 19, 2012
(http://gcc.gnu.org/ml/gcc-patches/2012-10/msg01838.html) he mentioned:
Say expr1 through expr9 are expressions with side effects, and you have:
expr1[expr2:expr
"Moore, Catherine" writes:
> Index: gcc/config/mips/constraints.md
> ===
> --- gcc/config/mips/constraints.md(revision 196638)
> +++ gcc/config/mips/constraints.md(working copy)
> @@ -43,6 +43,9 @@
> (define_register_constrai
Hi all,
here is a simple patch which fixes some problems with IMPLICT
CLASS(...) statements. Actually that's not a feature I would seriously
recommend anyone to use, but the Fortran standard allows it, so I
guess we should better support it ;)
The short patch attached here replaces all previous d
The gfortran testsuite on PowerPC now produces a number of new ICEs
when vectorization is enabled:
/tmp/20130320/gcc/testsuite/gfortran/../../gfortran
-B/tmp/20130320/gcc/testsuite/gfortran/../../
-B/tmp/20130320/powerpc-ibm-aix7.1.0.0/./libgfortran/
/nasfarm/dje/src/src/gcc/testsuite
> -Original Message-
> From: Richard Sandiford [mailto:rdsandif...@googlemail.com]
> Sent: Tuesday, March 19, 2013 4:38 PM
> To: Moore, Catherine
> Cc: gcc-patches@gcc.gnu.org; Rozycki, Maciej
> Subject: Re: FW: [PATCH] [MIPS] microMIPS gcc support
>
> "Moore, Catherine" writes:
> >> --
Hello!
The patch changes move insn patterns to output insn template depending
on their type attribute, not which_alternative.
2013-03-20 Uros Bizjak
* config/i386/i386.md (*movoi_internal_avx): Emit insn template
depending on type attribute.
(*movti_internal): Ditto.
On 03/20/2013 02:03 PM, James Greenhalgh wrote:
The argument would be; if we found an unexpected tree code then
it must have been introduced by folding. If it was a constant,
folding would have returned the constant not the expression. So it must
not be a constant.
Unless the operands involve c
On Wed, Mar 20, 2013 at 1:03 PM, James Greenhalgh
wrote:
> Is that be sensible? It certainly seems like someone intended to
> explicitly enumerate all the possible cases and ensure that they were
> correctly handled.
That someone would be me.
We need to catch loudly any front-end tree code, e.g
> Now that Stage 1 reopened, is this ok for 4.9?
Looks OK to me; I just had a few comments on the code readability.
> + if (lookup_decl_die (decl))
> +return rtl;
> +
> + len = TREE_STRING_LENGTH (t);
> + vec_safe_push (used_rtx_array, rtl);
> + ref = new_die (DW_TAG_dwarf_procedure, comp
> From: Jakub Jelinek [mailto:ja...@redhat.com]
> Sent: 15 March 2013 13:06
> On Fri, Mar 15, 2013 at 08:00:50AM -0500, Gabriel Dos Reis wrote:
> > On Fri, Mar 15, 2013 at 3:51 AM, Richard Biener
> > wrote:
> > > On Thu, Mar 14, 2013 at 10:08 PM, Marc Glisse
> wrote:
> > >> On Thu, 14 Mar 2013, J
On Mon, Mar 18, 2013 at 6:51 PM, H.J. Lu wrote:
> ix86_function_arg sets cfun->machine->callee_pass_avx256_p from the
> current argument. It clears callee_pass_avx256_p when ix86_function_arg
> is called to generate a library call to passs an argument. This patch
> adds callee_pass_avx256_p and
MOVK should not be generated with a negative immediate, which
the assembler rightfully rejects.
This patch makes MOVK output its 2nd operand in hex instead.
Tested on bare-metal and linux.
OK for trunk?
Cheers,
Ian
2013-03-20 Ian Bolton
gcc/
* config/aarch64/aarch64.c (aarch64_pri
On 03/18/2013 05:48 AM, David Holsgrove wrote:
> * gcc/config/microblaze/sync.md: New file.
> * gcc/config/microblaze/microblaze.md: Add UNSPEC_SYNC_CAS,
>UNSPEC_SYNC_XCHG and include sync.md.
> * gcc/config/microblaze/microblaze.c: Add print_operand 'y'.
> * gcc/config/microblaze/constrain
On 03/20/13 10:30, Aldy Hernandez wrote:
I have found some little nits that I will point out in a reply to this
message.
Joseph, folks, et al... How does this look?
Thanks.
Balaji:
+void
+array_notation_init_builtins (void)
+{
+ tree func_type = NULL_TREE;
+ tree new_func = NULL_TREE;
+
On Wed, 20 Mar 2013, Richard Biener wrote:
On Wed, Mar 20, 2013 at 4:29 PM, Marc Glisse wrote:
On Wed, 20 Mar 2013, Richard Henderson wrote:
On 03/20/2013 08:00 AM, Marc Glisse wrote:
Do you at least agree that vector-vector subregs make sense, or is that
part
wrong as well?
You mean a
On Wed, Mar 20, 2013 at 4:29 PM, Marc Glisse wrote:
> On Wed, 20 Mar 2013, Richard Henderson wrote:
>
>> On 03/20/2013 08:00 AM, Marc Glisse wrote:
>>>
>>> Do you at least agree that vector-vector subregs make sense, or is that
>>> part
>>> wrong as well?
>>
>>
>> You mean a V4SImode subreg of a V
The following splits out a core idea out of the patch series
fixing up LIM. For the testcase in PR39326 it get's us from
tree loop invariant motion: 560.00 (78%) usr
TOTAL : 721.06
to
tree loop invariant motion: 109.44 (40%) usr
TOTAL : 274.15
by choosi
On Wed, 20 Mar 2013, Richard Henderson wrote:
On 03/20/2013 08:00 AM, Marc Glisse wrote:
Do you at least agree that vector-vector subregs make sense, or is that part
wrong as well?
You mean a V4SImode subreg of a V8SImode register, not just same-size casting?
I am mostly interested in the r
On Wed, Mar 20, 2013 at 4:13 PM, Richard Henderson wrote:
> On 03/20/2013 08:00 AM, Marc Glisse wrote:
>> Do you at least agree that vector-vector subregs make sense, or is that part
>> wrong as well?
>
> You mean a V4SImode subreg of a V8SImode register, not just same-size casting?
> It makes log
On 03/20/2013 08:00 AM, Marc Glisse wrote:
> Do you at least agree that vector-vector subregs make sense, or is that part
> wrong as well?
You mean a V4SImode subreg of a V8SImode register, not just same-size casting?
It makes logical sense, but I'm fairly sure you'll need a lot more surgery
throu
> Hi,
>
> either it was added very late or I simply missed it in last stage1,
> but currently IPA-CP does not use INLINE_HINT_array_index in any way.
> This patch incorporates it to heuristics computations. I chose the
> bonus value to simply be slightly smaller than the bonuses for known
> strid
On Tue, 19 Mar 2013, Richard Henderson wrote:
On 03/19/2013 08:47 AM, Marc Glisse wrote:
(define_insn_and_split "avx__"
[(set (match_operand:AVX256MODE2P 0 "nonimmediate_operand" "=x,m")
- (unspec:AVX256MODE2P
- [(match_operand: 1 "nonimmediate_operand" "xm,x")]
- UNSP
On Wed, 2013-03-20 at 14:50 +0100, Jakub Jelinek wrote:
> On Wed, Mar 20, 2013 at 08:45:16AM -0500, Bill Schmidt wrote:
> > Eric, thanks -- fixed in trunk. Looks like I've missed the window for
> > 4.8.0. Is this OK for backport once 4.8 opens up again? (Copying
> > Richi/Jakub as well.)
>
> No
On Wed, Mar 20, 2013 at 08:45:16AM -0500, Bill Schmidt wrote:
> Eric, thanks -- fixed in trunk. Looks like I've missed the window for
> 4.8.0. Is this OK for backport once 4.8 opens up again? (Copying
> Richi/Jakub as well.)
Not for 4.8.0 (this isn't a wrong-code, just missed-optimization, righ
Eric, thanks -- fixed in trunk. Looks like I've missed the window for
4.8.0. Is this OK for backport once 4.8 opens up again? (Copying
Richi/Jakub as well.)
Thanks,
Bill
On Mon, 2013-03-18 at 17:31 +0100, Eric Botcazou wrote:
> > 2013-03-13 Bill Schmidt
> > Steven Bosscher
> >
> >
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Next I'll merge the two functions.
Richard.
2013-03-20 Richard Biener
* tree-inline.c (copy_tree_body_r): Sync MEM_REF code with
remap_gimple_op_r.
Index: gcc/tree-inline.c
===
This adds verification and simplifies clear_unused_block_pointer
accordingly (as previously discussed).
Bootstrap and regtest pending on x86_64-unknown-linux-gnu.
Richard.
2013-03-20 Richard Biener
* tree-cfg.c (verify_expr_no_block): New function.
(verify_expr_location_1):
Hi,
either it was added very late or I simply missed it in last stage1,
but currently IPA-CP does not use INLINE_HINT_array_index in any way.
This patch incorporates it to heuristics computations. I chose the
bonus value to simply be slightly smaller than the bonuses for known
strides and sizes,
On Wed, 20 Mar 2013, Jakub Jelinek wrote:
> On Wed, Mar 20, 2013 at 01:57:40PM +0100, Richard Biener wrote:
> > As discussed previously on IRC this patch does the renaming from
> > the confusing DECL_DEBUG_EXPR_IS_FROM to DECL_HAS_DEBUG_EXPR_P
> > which matches DECL_HAS_VALUE_EXPR_P (and it's beha
On Wed, Mar 20, 2013 at 01:57:40PM +0100, Richard Biener wrote:
> As discussed previously on IRC this patch does the renaming from
> the confusing DECL_DEBUG_EXPR_IS_FROM to DECL_HAS_DEBUG_EXPR_P
> which matches DECL_HAS_VALUE_EXPR_P (and it's behavior).
Not sure if we actually guarantee that if D
As discussed previously on IRC this patch does the renaming from
the confusing DECL_DEBUG_EXPR_IS_FROM to DECL_HAS_DEBUG_EXPR_P
which matches DECL_HAS_VALUE_EXPR_P (and it's behavior).
Bootstrap / regtest pending on x86_64-unknown-linux-gnu.
Ok if it passes?
Thanks,
Richard.
2013-03-20 Richar
It looks like this message didn't go through; if you get this multiple
times I apologize. I've been having issues so I don't trust that it
sent correctly :/
On 19-Mar-13 03:04, Maxim Kuvyrkov wrote:
Will commit to trunk once the server is up.
Regarding 4.8, we should've really tried to work
On Fri, Dec 07, 2012 at 11:36:24AM -0800, Cary Coutant wrote:
> > This patch adds DW_AT_const_value or DW_AT_location for unused static vars
> > (thus, not really modified and their DECL_INITIAL can be used for
> > location/constant value info), and optimizes various cases using
> > DW_OP_GNU_impli
On Wed, 20 Mar 2013, Rainer Orth wrote:
> Rainer Orth writes:
>
> > Ian Lance Taylor writes:
> >
> >> On Thu, Mar 14, 2013 at 9:53 AM, Rainer Orth wrote:
> >>
> >>> I found that this patch
> >>>
> >>> 2012-12-04 Ian Lance Taylor
> >>> * godump.c (find_dummy_types): Output a dummy type i
Rainer Orth writes:
> Ian Lance Taylor writes:
>
>> On Thu, Mar 14, 2013 at 9:53 AM, Rainer Orth wrote:
>>
>>> I found that this patch
>>>
>>> 2012-12-04 Ian Lance Taylor
>>> * godump.c (find_dummy_types): Output a dummy type if we couldn't
>>> output the real type.
>>>
>>> fixe
Tobias Burnus writes:
> Rainer Orth wrote:
>> As discussed in PR fortran/54932, the gfortran.dg/do_1.f90 execution
>> tests recently stated to XPASS at all optimization levels, adding lots
>> of testsuite noise. The following patch removes the xfail, allowing all
>> tests to pass.
>>
>> Tested w
On Wed, Mar 20, 2013 at 12:24 PM, Jakub Jelinek wrote:
> On Wed, Mar 20, 2013 at 12:20:27PM +0100, Richard Biener wrote:
>> Walking the SSA def chain would also be possible - preferably from
>> cfgexpand.c when we process the stmt. But you'll eventually lose
>> debug info like for
>>
>> int i =
On Wed, Mar 20, 2013 at 12:20:27PM +0100, Richard Biener wrote:
> Walking the SSA def chain would also be possible - preferably from
> cfgexpand.c when we process the stmt. But you'll eventually lose
> debug info like for
>
> int i = 1;
> __builtin_foo (i);
>
> when we then never expand the
On Wed, Mar 20, 2013 at 11:46 AM, Jakub Jelinek wrote:
> On Wed, Mar 20, 2013 at 11:38:03AM +0100, Richard Biener wrote:
>> Not without using information created by TER which is disabled for this
>> case because of different line information. If TER would not be disabled
>> for this reason it wou
On Wed, Mar 20, 2013 at 11:38:03AM +0100, Richard Biener wrote:
> Not without using information created by TER which is disabled for this
> case because of different line information. If TER would not be disabled
> for this reason it would already work automagically.
Would relaxing that in TER fo
On Tue, Mar 19, 2013 at 6:30 PM, Andi Kleen wrote:
> On Tue, Mar 19, 2013 at 05:10:22PM +0100, Jakub Jelinek wrote:
>> On Tue, Mar 19, 2013 at 08:51:21AM -0700, Andi Kleen wrote:
>> > > Using __always_inline as the name of the macro is a bad idea, glibc
>> > > headers use that macro already. Just
Committed after approval by Jakub.
Tobias
Index: svn.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v
retrieving revision 1.180
diff -u -r1.180 svn.html
--- svn.html 19 Feb 2013 21:21:26 - 1.180
+++ svn.html 20 Mar 2013 10:3
This fixes PR56661 - we were value-numbering two call results
the same even though function attributes tell us that they are
required to return a distinct value (and this property is exploited
by alias analysis). Simply don't do that (as opposed to trying to
fix things up).
Bootstrap and regtest
Arnaud Charlet wrote:
So Tobias: you can go ahead and commit these changes, assuming a clean
build/test for Ada.
I did a successful bootstrap (true all languages (all+ada+go+Obj-c(++)))
and "make check-ada" without any failures on x86-64-gnu-linux.
Committed as Rev. 196814.
Thanks for the r
Hi Tilo,
I have now committed your two patches.
* PR 48618 - Negative unit number in OPEN(...) is sometimes allowed (as
Rev. 196805)
which was approved here:
http://thread.gmane.org/gmane.comp.gcc.fortran/40435/focus=40455 (It's
not in the gcc.gnu.org/ml/fortran as the server didn't record the
60 matches
Mail list logo
