Hi!
As reported by Uros, the new testcase now fails with -mno-sse4.
The problem is that can_vec_perm_p tests different permutation from what
is actually expanded in the even/odd case (hi/lo is correct).
The permutation is always done after VCE to the narrower type.
Fixed thusly, committed as obvi
For some reasons, result variables are walked twice. With
-finit-local-zero their value gets set to 0, either via an inserted
assignment or by adding a initialization (sym->value).
With -fno-automatic sym->value is also set for result variables, which
later leads to an error. With the patch, t
Hi DJ,
We have this at the top of the loop, so I don't think it matters:
next = NEXT_INSN (insn);
if (GET_CODE (insn) != INSN)
continue;
Good point.
However, I think an insn will be skipped if we use NEXT. Perhaps we
want PREV? Or the loop might need to be
The GCC 4.5.4 release has been tagged and is being created right now.
The 4.5 branch is thus now closed.
We have now two actively maintained releases as planned, 4.6.x and 4.7.x.
Richard.
On Jun 29, 2012, Mike Stump wrote:
> First, let get to the heart of the matter. That is the behavior of
> compiler.
That's a distraction in the context of a patch to improve a feature
that's already present in the testsuite machinery, isn't it? I have no
objection to discussing this other topi
On Mon, Jul 2, 2012 at 1:06 PM, Alexandre Oliva wrote:
> On Jun 29, 2012, Mike Stump wrote:
>
>> First, let get to the heart of the matter. That is the behavior of
>> compiler.
>
> That's a distraction in the context of a patch to improve a feature
> that's already present in the testsuite machi
Hi Tobi,
On Fri, 29 Jun 2012, Tobias Grosser wrote:
> > +static isl_constraint *
> > +build_linearized_memory_access (isl_map *map, poly_dr_p pdr)
> > +{
> > +}
>
> The function itself looks correct. However, I would personally have returned
> an isl_map instead of an isl_constraint.
As you not
On Wed, 27 Jun 2012, Diego Novillo wrote:
> On Fri, Jun 22, 2012 at 9:16 AM, Richard Guenther wrote:
> >
> > This bumps the requirement to enable Graphite to using cloog 0.17.0
> > which is the last release from upstream. The patch removes the
> > support for the legacy cloog versions, too.
> >
On Thu, 28 Jun 2012, Diego Novillo wrote:
> On 12-06-27 11:06 , Richard Guenther wrote:
>
> > 2012-06-27 Richard Guenther
> > Michael Matz
> > Tobias Grosser
> > Sebastian Pop
> >
> > config/
> > * cloog.m4: Set up to work against ISL only.
> > * isl.m4: New file.
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Russian team of translators. The file is available at:
http://translationproject.org/latest/gcc/ru.po
(This file, 'gcc-4.7.1.ru.po', has just
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Russian team of translators. The file is available at:
http://translationproject.org/latest/gcc/ru.po
(This file, 'gcc-4.7.1.ru.po', has just
On Jun 13, 2012, Alexandre Oliva wrote:
> On May 3, 2012, Alexandre Oliva wrote:
>> Here are the 3 patches that, together, are equivalent to the one posted
>> before, except for the visibility of cleanup_auto_inc_dec.
> Ping?
> http://gcc.gnu.org/ml/gcc-patches/2012-05/msg00300.html
Ping²?
On Jun 30, 2012, David Edelsohn wrote:
> IBM's policy specifies a comma:
> ,
> and not a dash range.
But this notation already means something else in our source tree.
--
Alexandre Oliva, freedom fighterhttp://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- G
ewise.
> > >
> > > libgomp/
> > > * testsuite/libgomp.graphite/force-parallel-4.c: Adjust.
> > > * testsuite/libgomp.graphite/force-parallel-5.c: Likewise.
> > > * testsuite/libgomp.graphite/force-parallel-7.c: Likewise.
> > > * testsuite
On 7/2/2012 8:35 AM, Alexandre Oliva wrote:
On Jun 30, 2012, David Edelsohn wrote:
IBM's policy specifies a comma:
,
and not a dash range.
But this notation already means something else in our source tree.
I think using the dash is preferable, and is a VERY widely used
notation, us
til.c: Remove.
> > > > * graphite-cloog-util.h: Likewise.
> > > > * graphite-ppl.h: Likewise.
> > > > * graphite-ppl.c: Likewise.
> > > > * graphite-dependences.h: Likewise.
> > > >
> > > >
> > * graphite-ppl.h: Likewise.
> > > > > * graphite-ppl.c: Likewise.
> > > > > * graphite-dependences.h: Likewise.
> > > > >
> > > > > libgomp/
> > > > > * testsuite/libgomp.graphite/force-
t; > * graphite-scop-detection.c: Re-arrange includes.
> > > > > > * graphite-cloog-util.c: Remove.
> > > > > > * graphite-cloog-util.h: Likewise.
> > > > > > * graphite-ppl.h: Likewise.
> > > > > > * graphit
Robert Dewar writes:
> On 7/2/2012 8:35 AM, Alexandre Oliva wrote:
>> On Jun 30, 2012, David Edelsohn wrote:
>>> IBM's policy specifies a comma:
>>
>>> ,
>>
>>> and not a dash range.
>>
>> But this notation already means something else in our source tree.
>
> I think using the dash is preferable
On Mon, 2 Jul 2012, Robert Dewar wrote:
> On 7/2/2012 8:35 AM, Alexandre Oliva wrote:
> > On Jun 30, 2012, David Edelsohn wrote:
> >
> > > IBM's policy specifies a comma:
> >
> > > ,
> >
> > > and not a dash range.
> >
> > But this notation already means something else in our source tree.
>
On Sun, Jul 1, 2012 at 11:58 AM, Richard Guenther
wrote:
> On Sat, Jun 30, 2012 at 12:29 PM, Steven Bosscher
> wrote:
>> Hello,
>>
>> This patch moves the emit_case_bit_tests method of switch lowering
>> from 'expand' to a GIMPLE pass.
>>
>> Initially, I planned to move all switch lowering to so
On 07/02/2012 01:32 PM, Michael Matz wrote:
Hi Tobi,
On Fri, 29 Jun 2012, Tobias Grosser wrote:
+static isl_constraint *
+build_linearized_memory_access (isl_map *map, poly_dr_p pdr)
+{
+}
The function itself looks correct. However, I would personally have returned
an isl_map instead of an i
On 07/02/2012 01:32 PM, Michael Matz wrote:
+++ b/gcc/graphite.c
@@ -253,6 +253,8 @@ graphite_finalize (bool need_cfg_cleanup_p)
print_loops (dump_file, 3);
}
+isl_ctx *the_isl_ctx;
Why are you creating a global ctx here?
For the printer, before I was aware of the fact that of cour
On Mon, Jul 2, 2012 at 10:17 AM, Joseph S. Myers
wrote:
> On Mon, 2 Jul 2012, Robert Dewar wrote:
>
>> On 7/2/2012 8:35 AM, Alexandre Oliva wrote:
>> > On Jun 30, 2012, David Edelsohn wrote:
>> >
>> > > IBM's policy specifies a comma:
>> >
>> > > ,
>> >
>> > > and not a dash range.
>> >
>> > But
On Mon, 2 Jul 2012, David Edelsohn wrote:
> There was a similar discussion many years ago. The dash format is
> widely used, but the comma format has better legal clarity and
> definition in worldwide copyright litigation, at least many years ago.
Maybe questions about the meanings of the dash fo
Mike Stump says he got word that I am reinstated as a testsuite
maintainer so I added myself to the MAINTAINERS file (with, I now
see, a typo in the ChangeLog).
2012-07-02 Janis Johnson
* MAINTAINERS (Various Mainterers): Add myself as testsuite
maintainer.
Index: MAINTAINERS
Hi,
this patch uses the aggregate jump functions created by a previous
patch to determine benefits of inlining a particular call graph edge.
It does so by fairly straightforward way. It a flag to struct
condition to specify it is actually an aggregate value at an offset,
also newly stored in the
My concern is more about calling NEXT_INSN on a deleted insn. If
that's guaranteed to be "reliable", I'm OK with it.
Alternately, call NEXT_INSN at the top of the loop, but save the value
until the *next* iteration of the loop, so we can delete the insn and
not have to call NEXT_INSN on it after
On Jul 2, 2012, at 4:06 AM, Alexandre Oliva wrote:
> On Jun 29, 2012, Mike Stump wrote:
>> First, let get to the heart of the matter. That is the behavior of
>> compiler.
>
> That's a distraction in the context of a patch to improve a feature
> that's already present in the testsuite machinery,
On 6/27/2012 8:06 AM, Richard Guenther wrote:
This merges from the graphite branch the move of PPL to ISL,
and completes it where it was lacking - thanks to Micha.
It leaves unmerged the addition of a pluto-like ISL optimizer
as well as a bugfix for stride > 1 which did not come with
a testcase.
After the move to CLooG 0.17.0/ISL 0.10, mainline fails to configure
with a static libisl:
configure:5697: checking for version 0.10 of ISL
configure:5722: gcc -o conftest -g -O2 -I/vol/gcc/include -I/vol/gcc/include -I/
vol/gcc/include -I/vol/gcc/include-L/vol/gcc/lib -lisl -lisl conftest.c
On Sun, Jul 1, 2012 at 1:08 AM, Uros Bizjak wrote:
> Based on the observation above, the patch is OK for mainline, but
> please also handle "rep nop" case.
Here's the new version of the patch that does that. Note that someone
needs to commit this for me, since I am not empowered to do it myself.
While a C++ enumeration is being defined, the enumerators have the types
of their initializers, rather than the enumeration type itself. As a
result, if two enumerators are initialized from two other enumerations,
and then the two are used in a ?: to initialize a third, we end up with
mismatch
It seems that since my change to avoid push_to_top_level for
instantiating lambdas, the code in maybe_add_lambda_conv_op for handling
function context activates and does the wrong thing. I don't remember
why I added the code that sets DECL_INTERFACE_KNOWN, but it doesn't seem
to be needed.
T
On 06/15/2012 10:27 AM, Paolo Carlini wrote:
The problem is that with the patch applied we get errors of the "no
matching function" type, instead of access control errors.
I suppose this is expected, right?!?
Yes, but when we're printing the candidates we need to give an access
control error
Hello,
The attached patch adds a few bswap32 test cases for SH.
Tested against rev 189175 with
make -k check RUNTESTFLAGS="sh.exp=pr53568-1.c --target_board=sh-sim
\{-m2/-ml,-m2/-mb,-m2a/-mb,-m2a-single/-mb,-m4/-ml,-m4/-mb,
-m4-single/-ml,-m4-single/-mb,-m4a-single/-ml,-m4a-single/-mb}"
to make
On May 26, 2012, at 8:03 PM, Michael Matz wrote:
> ---
> PR middle-end/38474
> * cfgexpand.c (struct stack_var): Add slot_type member.
> (add_stack_var): Initialize it.
> (add_alias_set_conflicts): Remove.
> (merge_stack_vars_p, more_specific_type):
Hi,
this third patch is basically a proof-of-concept aiming at alleviating
the following code found in Fortran functions when they look at the
contents of array descriptors:
:
stride.156_7 = strain_tensor_6(D)->dim[0].stride;
if (stride.156_7 != 0)
goto ;
else
goto ;
Oleg Endo wrote:
> The attached patch adds a few bswap32 test cases for SH.
> Tested against rev 189175 with
> make -k check RUNTESTFLAGS="sh.exp=pr53568-1.c --target_board=sh-sim
> \{-m2/-ml,-m2/-mb,-m2a/-mb,-m2a-single/-mb,-m4/-ml,-m4/-mb,
> -m4-single/-ml,-m4-single/-mb,-m4a-single/-ml,-m4a-si
Hello,
The test case g++.dg/other/packed1.C does not fail on SH.
Is it OK to remove SH from the xfail list there?
Tested with
make -k check RUNTESTFLAGS="dg.exp=packed1.C --target_board=sh-sim
\{-m2/-ml,-m2/-mb,-m2a/-mb,-m2a-single/-mb,-m4/-ml,-m4/-mb,
-m4-single/-ml,-m4-single/-mb,-m4a-single/-
I extended the patch a little so that the option can be used to set
multiple stack reuse levels: -fstack-reuse=[all|name_vars|none]
all: enable stack reuse for all local vars (named vars and compiler
generated temporaries) which live in memory;
name_vars: enable stack reuse only for user declared
Oleg Endo wrote:
> The test case g++.dg/other/packed1.C does not fail on SH.
> Is it OK to remove SH from the xfail list there?
OK.
Regards,
kaz
resolves_to_fixed_type_p has caused a lot of ICEs in templates over the
years because it wants to look inside the DECL_INITIAL of variables with
non-constant initializers which are still in pre-tsubst form. Checking
processing_template_decl to prevent this isn't strong enough, because
fold_non
The diagnostic for calling a non-static member function without an
associated object depends on the form of the dummy object built by
build_dummy_object. If we wrap it in a NON_DEPENDENT_EXPR, then
is_dummy_object doesn't recognize it any more. So don't wrap it.
Tested x86_64-pc-linux-gnu, a
This patch fixes a selector fault in the new g++.dg/cpp0x/nullptr28.C test
by changing the c++-11 target selector to the equivalent options. The
test itself was backported from trunk in r188953 to fix PR52988.
Tested on x86_64-linux. The ERROR changes to a PASS.
OK for 4.6?
-- Michael
gcc/te
On Tue, Jul 03, 2012 at 04:09:18PM +1200, Michael Hope wrote:
> This patch fixes a selector fault in the new g++.dg/cpp0x/nullptr28.C test
> by changing the c++-11 target selector to the equivalent options. The
> test itself was backported from trunk in r188953 to fix PR52988.
>
> Tested on x86_6
My change in 4.8 to use 'auto' for the return type of a lambda caused
uses_template_parms (current_function_decl) to return true, causing us
to skip the real adjustment to the base address. Fixed by looking at
DECL_TI_ARGS instead.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 7b39813
A nested lambda in a template was complaining about use of an 'auto'
function before its return type was deduced; this was because we were
using tsubst_copy to instantiate LAMBDA_EXPR_EXTRA_SCOPE, i.e. treating
it as an expression, which results in calling mark_used. Fixed by using
tsubst inst
48 matches
Mail list logo
