On 2 April 2013 17:55, Ramana Radhakrishnan ramana@googlemail.com wrote:
On Thu, Mar 21, 2013 at 7:03 AM, Zhenqiang Chen
zhenqiang.c...@linaro.org wrote:
Hi,
The patch is to enable shrink-wrap for TARGET_ARM and TARGET_THUMB2.
Bootstrapped and no make check regression.
All previous
Regarding the second point, one should mention that we already have a
warning for alternate return, but this only triggers if there is an
actual RETURN statement (which is not the case for the test code in
the PR). The warning I'm adding triggers on the appearance of an
asterisk argument.
This fixes PR56778 - a fallout of my vectorizer TLC regarding
dataref analysis. The patch restores a check that disallows
runtime alias checks for gather loads (those are not loop
invariant). It also fixes another possible source of issues.
Bootstrapped and tested on x86_64-unknown-linux-gnu,
This fixes PR56812 - the vectorizer TLC got rid of special-casing
interleaving chain members in data dependence analysis. I re-instantiated
that after having a quick look why dependence analysis doesn't
disambiguate them (it should - known issue, on my TODO list).
And added a testcase to make
Hi!
I've backported, bootstrapped/regtested and committed the following two
patches to 4.7 branch.
Jakub
2013-04-03 Jakub Jelinek ja...@redhat.com
Backported from mainline
2013-03-05 Jakub Jelinek ja...@redhat.com
PR debug/56510
* cfgexpand.c
On Tue, Apr 2, 2013 at 7:35 PM, Kenneth Zadeck zad...@naturalbridge.com wrote:
Yes, I agree that you win the challenge that it can be done.What you
have always failed to address is why anyone would want to do this. Or how
this would at all be desirable.But I completely agree that from
On Tue, Apr 2, 2013 at 9:08 PM, Kenneth Zadeck zad...@naturalbridge.com wrote:
this time for sure.
Almost ...
diff --git a/gcc/hwint.c b/gcc/hwint.c
index 330b42c..92d54a3 100644
--- a/gcc/hwint.c
+++ b/gcc/hwint.c
@@ -204,3 +204,35 @@ least_common_multiple (HOST_WIDE_INT a, HOST_WIDE_INT b)
{
On Wed, Apr 3, 2013 at 3:38 AM, Bin Cheng bin.ch...@arm.com wrote:
Hi,
When I look into code of auto-inc-dec.c in GCC, I found this typo in rtl.h,
as
#if (defined (HAVE_PRE_INCREMENT) || defined (HAVE_PRE_DECREMENT) \
|| defined (HAVE_POST_INCREMENT) || defined (HAVE_POST_DECREMENT) \
The following obvious fix fixes the ICE in PR56501.
Boostrap / regtest pending on x86_64-unknown-linux-gnu.
Richard.
2013-04-03 Richard Biener rguent...@suse.de
PR tree-optimization/56501
* tree-switch-conversion.c (check_process_case): Properly
handle !single_succ_p
Thank you for your feedback!
For '}' case, can you simply just add
/* Skip over any character after a percent sign. */
if (*p == '%' *(p + 1))
{
p += 2;
continue;
}
without changing the do-while loop to the while loop?
Loop condition (*p++ != '}') must be moved to loop body for
The testcase no longer fails on the 4.8 branch and trunk,
committed there so we do not regress.
Richard.
2013-04-03 Richard Biener rguent...@suse.de
PR tree-optimization/56407
* gcc.dg/torture/pr56407.c: New testcase.
Index: gcc/testsuite/gcc.dg/torture/pr56407.c
Hi Steven,
From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
ow...@gcc.gnu.org] On Behalf Of Steven Bosscher
Sent: 30 March 2013 13:10
To: Jeff Law
Cc: GCC Patches
Subject: Re: [patch] Stop using JUMP_INSN for jump table data
On Sat, Mar 30, 2013 at 2:02 PM, Jeff Law wrote:
Slightly different and less arcane.
Tested on x86_64-unknown-linux-gnu, applied to trunk and branch.
Richard.
2013-04-03 Richard Biener rguent...@suse.de
PR tree-optimization/55964
* gcc.dg/torture/pr55964-2.c: New testcase.
Index: gcc/testsuite/gcc.dg/torture/pr55964-2.c
On Fri, 15 Mar 2013 18:16:48 +
Julian Brown jul...@codesourcery.com wrote:
Hi,
At present, the libcall helpers implementing atomic operations
(__sync_val_compare_and_swap_X) for char and short types suffer from
a type mismatch. This is leading to test failures, i.e.:
FAIL:
yes, i had caught that when i merged it in with the patches that used
it, is it ok aside from that?
kenny
On 04/03/2013 05:32 AM, Richard Biener wrote:
On Tue, Apr 2, 2013 at 9:08 PM, Kenneth Zadeck zad...@naturalbridge.com wrote:
this time for sure.
Almost ...
diff --git a/gcc/hwint.c
-Original Message-
From: Richard Biener [mailto:richard.guent...@gmail.com]
Sent: Wednesday, April 03, 2013 5:36 PM
To: Bin Cheng
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH GCC]Fix typo in definition of macro AUTO_INC_DEC in
rtl.h
On Wed, Apr 3, 2013 at 3:38 AM, Bin Cheng
On Thu, Mar 28, 2013 at 2:18 PM, Tobias Burnus bur...@net-b.de wrote:
Foone Turing wrote:
This page: http://gcc.gnu.org/gcc-4.8/
under release history says GCC 4.8 was released on March 22, 2012.
This should be 2013, not 2012.
Thanks for the report! I have corrected it now.
Same typo at
On 04/03/2013 02:09 AM, Jonathan Wakely wrote:
This patch implements
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3189.htm
Thanks Jon. I'm seeing abi_check fails which seem related. Could you
please double check?
Thanks again,
Paolo.
On 3 April 2013 12:45, Paolo Carlini wrote:
On 04/03/2013 02:09 AM, Jonathan Wakely wrote:
This patch implements
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3189.htm
Thanks Jon. I'm seeing abi_check fails which seem related. Could you please
double check?
Ah sorry, I didn't
On 04/03/2013 01:53 PM, Jonathan Wakely wrote:
On 3 April 2013 12:45, Paolo Carlini wrote:
On 04/03/2013 02:09 AM, Jonathan Wakely wrote:
This patch implements
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3189.htm
Thanks Jon. I'm seeing abi_check fails which seem related. Could
On 04/03/2013 05:17 AM, Richard Biener wrote:
In the end you will have a variable-size storage in TREE_INT_CST thus
you will have at least to emit _code_ copying over meta-data and data
from the tree representation to the wide-int (similar for RTX CONST_DOUBLE/INT).
I'm objecting to the amount
On Wed, Apr 3, 2013 at 12:47 PM, Kenneth Zadeck
zad...@naturalbridge.com wrote:
yes, i had caught that when i merged it in with the patches that used it, is
it ok aside from that?
Yes.
Thanks,
Richard.
kenny
On 04/03/2013 05:32 AM, Richard Biener wrote:
On Tue, Apr 2, 2013 at 9:08 PM,
Steven Bosscher wrote:
GCC uses fake JUMP_INSNs as placeholders for jump table data. These
JUMP_INSNs have an ADDR_VEC or ADDR_DIFF_VEC as PATTERN, but they are
not real instructions and they are not inside basic blocks. This
results in special-casing JUMP_P insns in various places throughout
This uses dg-additional-options, not dg-options which overrides
target specific flags added by dg-require-effective-target vect_float.
Tested on x86_64-unknown-linux-gnu, applied.
Richard.
2013-04-03 Richard Biener rguent...@suse.de
* g++.dg/vect/slp-pr56812.cc: Use
Hi!
On the following testcase we ICE with -fcompare-debug with
--enable-checking=yes, because strip_typedefs copies args to a new TREE_VEC,
but doesn't copy over NON_DEFAULT_TEMPLATE_ARGS_COUNT. For ENABLE_CHECKING
the code requires that it is set, for !ENABLE_CHECKING it would be needed
only if
Status
==
The GCC 4.7 branch is ready for a release candidate of GCC 4.7.3
which I will do tomorrow if no serious issue shows up until then.
The branch is frozen now, all changes require release manager approval
until the final release of GCC 4.7.3 which should happen roughly
one week after
The RTEMS Community would like to squeeze pr56771 in. It only got a fix in the
past few days. It is a one line arm-rtems specific path to libcpp configure.
Can I commit that?
--joel
RTEMS
Richard Biener rguent...@suse.de wrote:
Status
==
The GCC 4.7 branch is ready for a release
This doesn't seem to have made it to the list.
-Original Message-
From: Moore, Catherine
Sent: Tuesday, April 02, 2013 12:26 PM
To: 'Richard Sandiford'
Cc: gcc-patches@gcc.gnu.org; Rozycki, Maciej; 'c...@codesourcery.com'
Subject: RE: [Patch] Add microMIPS jraddiusp support
Hi Richard,
Hi,
The attached patch fixes duplication in a test case for gcc.target/aarch64/.
Tested on aarch64-none-elf. OK for trunk and branch?
Thanks,
Tejas Belagod
ARM.
2013-04-03 Tejas Belagod tejas.bela...@arm.com
testsuite/
* gcc.target/aarch64/inc/asm-adder-clobber-lr.c: Remove
On Wed, 3 Apr 2013, Joel Sherrill wrote:
The RTEMS Community would like to squeeze pr56771 in. It only got a fix in
the past few days. It is a one line arm-rtems specific path to libcpp
configure.
Can I commit that?
Sure, if it got RTEMS maintainer approval.
Richard.
--joel
RTEMS
On Wed, Apr 3, 2013 at 7:36 AM, Jakub Jelinek ja...@redhat.com wrote:
Hi!
On the following testcase we ICE with -fcompare-debug with
--enable-checking=yes, because strip_typedefs copies args to a new TREE_VEC,
but doesn't copy over NON_DEFAULT_TEMPLATE_ARGS_COUNT. For ENABLE_CHECKING
the
This fixes PR56817 - when unrolling a loop we may not process
to outer loops of that loop without updating SSA form inbetween.
The following patch arranges for that by defering outer loop
processing to the next unrolling iteration.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to
We should be able to just copy NON_DEFAULT_TEMPLATE_ARGS_COUNT over
rather than mess with looking into and building an INTEGER_CST.
Jason
On Wed, Apr 03, 2013 at 08:38:01AM -0500, Gabriel Dos Reis wrote:
2013-04-03 Jakub Jelinek ja...@redhat.com
PR debug/56819
* tree.c (strip_typedefs): SET_NON_DEFAULT_TEMPLATE_ARGS_COUNT
on new_args.
* g++.dg/debug/pr56819.C: New test.
---
Is it okay for this patch to be backported to the 4.8 branch?
Thanks,
Matt
On 25/03/13 18:34, Roland McGrath wrote:
This fixes a gratuitous warning.
Thanks,
Roland
gcc/
2013-03-25 Roland McGrath mcgra...@google.com
* config/arm/arm.c (arm_print_operand: case 'w'): Use fputs
This patch detects and emits an error if the value provided in _Alignas
is negative. The fix was approved pending full regression testing in a
previous discussion (http://gcc.gnu.org/ml/gcc/2013-03/msg00282.html).
To add to that patch, I have added a testcase that explicitly checks for the
error
On Wed, Apr 3, 2013 at 2:05 PM, Kenneth Zadeck zad...@naturalbridge.com wrote:
On 04/03/2013 05:17 AM, Richard Biener wrote:
In the end you will have a variable-size storage in TREE_INT_CST thus
you will have at least to emit _code_ copying over meta-data and data
from the tree
On Wed, Apr 03, 2013 at 09:43:01AM -0400, Jason Merrill wrote:
We should be able to just copy NON_DEFAULT_TEMPLATE_ARGS_COUNT over
rather than mess with looking into and building an INTEGER_CST.
So is this ok instead?
2013-04-03 Jakub Jelinek ja...@redhat.com
PR debug/56819
On Wed, 3 Apr 2013, Matthew Gretton-Dann wrote:
Is it okay for this patch to be backported to the 4.8 branch?
Yes.
Richard.
Thanks,
Matt
On 25/03/13 18:34, Roland McGrath wrote:
This fixes a gratuitous warning.
Thanks,
Roland
gcc/
2013-03-25 Roland McGrath
Hi,
Please find attached a patch that fixes PR56780. Build tested on
x86_64-linux. I've also attached it to the bug.
Regards,
Matt Burgess
2013-04-03 Matt Burgess matt...@linuxfromscratch.org
other/PR56780
* libiberty/configure.ac:
Move test for
Hi Guys,
I am checking in the patch below to make gcc generate the FPU-3.0
multiply-add instructions when targeting the E3V5 V850 architecture.
Cheers
Nick
gcc/ChangeLog
2013-04-03 Nick Clifton ni...@redhat.com
* config/v850/v850e3v5.md (fmasf4): Use fmaf.s on E3V5
Hello,
I am not 100% convinced that it is always better to fold to a MEM_REF, but
that's what the PR asks for.
bootstrap+testsuite on x86_64-linux-gnu.
2013-04-03 Marc Glisse marc.gli...@inria.fr
PR middle-end/52436
gcc/
* fold-const.c (fold_ternary_loc) BIT_FIELD_REF:
OK.
Jason
Associate requirements with declarations. This introduces a new node
(constraint-info) stores requirements and (eventually) decomposed
assumptions for all C++ declaration types. Template constraints are
associated with template declarations (including aliases and template
template parameters) and
On 4/3/2013 8:36 AM, Richard Biener wrote:
On Wed, 3 Apr 2013, Joel Sherrill wrote:
The RTEMS Community would like to squeeze pr56771 in. It only got a fix in the
past few days. It is a one line arm-rtems specific path to libcpp configure.
Can I commit that?
Sure, if it got RTEMS maintainer
In this PR we ICEd because instrument_func_exit checked that
the last stmt of predecessors of EXIT_BLOCK_PTR is GIMPLE_RETURN,
but here we should allow BUILT_IN_RETURN function as well, as
it's basically the same as return.
I'm not sure about the testcase, but we don't have tsan testsuite
yet ...
On Wed, Apr 3, 2013 at 4:15 PM, Marc Glisse marc.gli...@inria.fr wrote:
Hello,
I am not 100% convinced that it is always better to fold to a MEM_REF, but
that's what the PR asks for.
bootstrap+testsuite on x86_64-linux-gnu.
2013-04-03 Marc Glisse marc.gli...@inria.fr
PR
Hi all,
This patch fixes an ICE that we encounter when building gcc on arm targets.
The jump table reorganisation exposed a bug in the backend. This fixes it
by using next_active_insn instead of next_real_insn when looking for the
diff vector in the jump table handling code. (Thanks to Steven
Hi all,
This patch fixes a PR that was exposed in the recent jump table
reorganisation.
We should use next_active_insn instead of next_real_insn in the jump table
handling code.
This fixes the incorrect assembly generation that we get when building
newlib for aarch64.
Tested aarch64-none-elf.
A
Hi,
admittedly, I'm still missing some details of the
--enable-symvers=gnu-versioned-namespace configuration, but this is
straightforweard enough. Applied mainline and 4_8-branch.
Thanks,
Paolo.
///
2013-04-03 Paolo Carlini paolo.carl...@oracle.com
PR
On Wed, Apr 03, 2013 at 04:40:30PM +0200, Marek Polacek wrote:
In this PR we ICEd because instrument_func_exit checked that
the last stmt of predecessors of EXIT_BLOCK_PTR is GIMPLE_RETURN,
but here we should allow BUILT_IN_RETURN function as well, as
it's basically the same as return.
I'm
On 04/03/13 16:07, Kyrylo Tkachov wrote:
Hi all,
This patch fixes an ICE that we encounter when building gcc on arm targets.
The jump table reorganisation exposed a bug in the backend.
This fixes it
by using next_active_insn instead of next_real_insn when looking for the
diff vector in the jump
This patch has been applied to 4.7, 4.8 and 4.9.
PR 56771 closed.
--joel
On 4/2/2013 10:08 AM, Sebastian Huber wrote:
This patch is for GCC 4.8 and 4.9.
v2: Fix ChangeLog.
libcpp/ChangeLog
2013-04-02 Sebastian Huber sebastian.hu...@embedded-brains.de
PR target/56771
*
Though, as INTEGER_CSTs should be shared, perhaps this could be just
NON_DEFAULT_TEMPLATE_ARGS_COUNT (new_args)
= NON_DEFAULT_TEMPLATE_ARGS_COUNT (args);
Yes, thanks!
and strip_typedefs_expr could be changed to do the same thing.
Would it be possible for this patch and the others Kyrylo has recently done
for the new ARMv8 AArch32 instructions to be backported to 4.8?
In particular I'm refering to:
http://gcc.gnu.org/ml/gcc-patches/2013-03/msg00994.html (trunk r197052)
Hi,
thus, as discussed in the audit trail, I'm simply changing the permerror
in the C++ front-end to pedwarn.
Tested x86_64-linux.
Thanks,
Paolo.
PS: there is a couple of issues noticed while working on this -
essentially, tweaks to c.opt and c-common.c - which I prefer to handle
I'm working on my first gcc contribution, but it's a large patch, and I
wanted to sound things out on this list.
I want to eliminate/minimize global state within gcc, since I think
doing so is a key part of making gcc more modular.
Currently there's a lot of global state associated with passes:
OK.
Jason
On 04/03/2013 09:53 AM, Richard Biener wrote:
On Wed, Apr 3, 2013 at 2:05 PM, Kenneth Zadeck zad...@naturalbridge.com wrote:
On 04/03/2013 05:17 AM, Richard Biener wrote:
In the end you will have a variable-size storage in TREE_INT_CST thus
you will have at least to emit _code_ copying over
On Wed, Apr 3, 2013 at 4:07 PM, Kyrylo Tkachov kyrylo.tkac...@arm.com wrote:
Hi all,
This patch fixes a PR that was exposed in the recent jump table
reorganisation.
We should use next_active_insn instead of next_real_insn in the jump table
handling code.
This fixes the incorrect assembly
On Wed, Apr 03, 2013 at 04:07:50PM +0100, Kyrylo Tkachov wrote:
This patch fixes a PR that was exposed in the recent jump table
reorganisation.
We should use next_active_insn instead of next_real_insn in the jump table
handling code.
This fixes the incorrect assembly generation that we get
And here's the demangler patch.
commit 7a39cc5b85f6f100427515c7031f7ec9fe6ac84f
Author: Jason Merrill ja...@redhat.com
Date: Wed Apr 3 12:27:03 2013 -0400
Demangle C++11 ref-qualifier.
include/
* demangle.h (enum demangle_component_type): Add
Hi,
earlier today I noticed that I wasn't able to construct a testcase
tirggering this warning and decided to replace the body with a
gcc_unreachable () and boot test C/OBJC/C++/OBJC++. No regressions.
Its this some sort of legacy case which can go away?
Thanks!
Paolo.
2012-12-14 Teresa Johnson tejohn...@google.com
* lto-cgraph.c (input_symtab): Replace call to compute_working_sets
to get_working_sets.
* gcov-io.c (compute_working_sets): Moved most of body of old
compute_working_sets here from profile.c.
Backport committed to gcc-4_8-branch.
On Thu, Mar 28, 2013 at 04:49:47PM +0100, Uros Bizjak wrote:
2013-03-27 Wei Mi w...@google.com
* config/i386/i386.md: Do shift truncation in define_insn
instead of define_insn_and_split.
Please write ChangeLog as:
* config/i386/i386.md (*ashlmode3_mask): Rewrite as
On Mon, Apr 01, 2013 at 12:36:55PM +0400, Andrey Belevantsev wrote:
Now backported to 4.7 and 4.6 with Jakub's patch for the
sel-sched-ir.c memory leak added.
Test fixed thusly on the 4.6 branch, 4.7 branch has been apparently taken
care by Richi already.
2013-04-03 Jakub Jelinek
Hi!
I've backported 11 patches of mine to 4.6 branch, bootstrapped/regtested
on x86_64-linux and i686-linux, committed.
Jakub
2013-04-03 Jakub Jelinek ja...@redhat.com
Backported from mainline
2012-03-01 Jakub Jelinek ja...@redhat.com
PR
Status
==
The GCC 4.6 branch is ready for a release candidate of GCC 4.6.4
which I will do on Friday if no serious issue shows up until then.
The branch is frozen now, all changes require release manager approval.
The final release should happen roughly one week after the release
candidate,
Per Richi's suggestions I tweaked the recent tree-ssa-dom.c equivalence
code to use int_fits_type_p rather than creating a new integer node and
verifying it had the same value as the old node.
At the time I dropped the TYPE_PRECISION check as I thought it was
redundant with the
Hello,
I would like to add information about the Cilkplus branch into the
svn.html webpage. Here is the patch for it (I generated it using cvs diff -p
svn.html). Is this OK to commit? Am I sending this to the correct
location/mailing list?
Thanks,
Balaji V. Iyer.
Index: svn.html
On Tue, Apr 2, 2013 at 6:56 PM, Steven Bosscher wrote:
The SPARC back
end also calls dbr_schedule() in its machine_reorg pass to work around
errata in Atmel AT697F chips (LEON2-like, i.e. fairly new, see
r179921).
Thinking about this some more: This could be fixed by inserting a
committed as revision 197456
kenny
On 04/03/2013 08:05 AM, Richard Biener wrote:
On Wed, Apr 3, 2013 at 12:47 PM, Kenneth Zadeck
zad...@naturalbridge.com wrote:
yes, i had caught that when i merged it in with the patches that used it, is
it ok aside from that?
Yes.
Thanks,
Richard.
kenny
.. I analyzed a bit what is happening and this is what I see: the only
interesting case is that of C++, where pointer_int_sum is called via
cp_pointer_int_sum. The latter is only called by cp_build_binary_op but
that happens for MINUS_EXPR and PLUS_EXPR as operator. In such cases
however, only
Thanks for helping fixing it. I will take care to verify regression
and bootstrap before checkin to release branches next time.
Regards,
Wei.
On Wed, Apr 3, 2013 at 11:08 AM, Jakub Jelinek ja...@redhat.com wrote:
On Thu, Mar 28, 2013 at 04:49:47PM +0100, Uros Bizjak wrote:
2013-03-27 Wei Mi
On Wed, Apr 3, 2013 at 10:52 AM, Jan Hubicka hubi...@ucw.cz wrote:
2012-12-14 Teresa Johnson tejohn...@google.com
* lto-cgraph.c (input_symtab): Replace call to compute_working_sets
to get_working_sets.
* gcov-io.c (compute_working_sets): Moved most of body of
Ok, here is the follow-up patch, which removes the warning on
(alternate) RETURN statements, in order to avoid double diagnostics.
However, it also adds another warning for alternate-return actual
arguments (in addition to the formal ones), in order to catch
additional cases, which were not
Le 02/04/2013 18:26, Tobias Burnus a écrit :
diff --git a/gcc/fortran/check.c b/gcc/fortran/check.c
index 99174bc..b0c831e 100644
--- a/gcc/fortran/check.c
+++ b/gcc/fortran/check.c
@@ -3649,11 +3649,12 @@ gfc_check_sizeof (gfc_expr *arg)
/* Check whether an expression is interoperable.
Le 02/04/2013 19:19, Tobias Burnus a écrit :
{
snprintf (message, MSGLEN,
Read kind %d %s where kind %d is required for item %d,
- dtp-u.p.saved_length, type_name (dtp-u.p.saved_type), len,
+ type == BT_COMPLEX ? dtp-u.p.saved_length / 2
On 04/01/2013 03:03 PM, Jason Merrill wrote:
(FUNCTION_OR_METHOD_TYPE_CHECK): New.
It turns out that there's already a FUNC_OR_METHOD_CHECK in tree.h, so
I'm removing this duplicate.
commit 4a01f2f261f9f0cb33bd959a80fe47782474ab18
Author: Jason Merrill ja...@redhat.com
Date: Tue
On Wed, Apr 3, 2013 at 10:13 PM, Jason Merrill ja...@redhat.com wrote:
On 04/01/2013 03:03 PM, Jason Merrill wrote:
(FUNCTION_OR_METHOD_TYPE_CHECK): New.
It turns out that there's already a FUNC_OR_METHOD_CHECK in tree.h, so I'm
removing this duplicate.
and maybe rename the old one
lra-constraints.c and lra-eliminations.c include optabs.h, but don't
have a dependency on $(OPTABS_H).
This is obviously bad.
Fixed via the attached patch, which I checked with c/c++ only bootstrap.
Applied to the trunk as obvious.
commit d5bbf015a843c696478a36e3f048c92307e221c6
Author:
82 matches
Mail list logo
