It's a regression (albeit an old one):
http://gcc.gnu.org/ml/gcc-patches/2013-01/msg01044.html
Thanks in advance.
--
Eric Botcazou
This reduces compile-time of the testcase in PR56113 (with n = 4)
from 575s to 353s. It does so by reducing the quadratic algorithm
to impose an order on visiting dominator sons during a domwalk.
Steven raises the issue that there exist domwalk users that modify
the CFG during the walk and
On Mon, Jan 21, 2013 at 9:41 AM, Eric Botcazou ebotca...@adacore.com wrote:
Hi,
this is a regression present in the Ada compiler since 4.5: the issue had been
latent for ages, but an unrelated streamlining of the IR made it appear.
When make_range_step is invoked on:
(integer)!b 0
On Fri, Feb 01, 2013 at 10:00:00AM +0100, Richard Biener wrote:
This reduces compile-time of the testcase in PR56113 (with n = 4)
from 575s to 353s. It does so by reducing the quadratic algorithm
to impose an order on visiting dominator sons during a domwalk.
Steven raises the issue
This reduces the work done for single predecessor nodes for
assigning pointer equivalence classes in label_visit. For
the PR56113 testcase with n = 4 this reduces PTA time from
tree PTA: 119.59 (34%) usr
to
tree PTA: 51.62 (18%) usr
(the percentages are
On Fri, 1 Feb 2013, Jakub Jelinek wrote:
On Fri, Feb 01, 2013 at 10:00:00AM +0100, Richard Biener wrote:
This reduces compile-time of the testcase in PR56113 (with n = 4)
from 575s to 353s. It does so by reducing the quadratic algorithm
to impose an order on visiting dominator sons
The mode for AND should really be CC_NZ, so I fixed that up and in the TST
patterns that (erroneously) expected it to be CC mode.
It has been tested on linux and bare-metal.
OK to commit to trunk (as bug fix)?
Thanks.
Ian
13-02-01 Ian Bolton ian.bol...@arm.com
*
On 01/02/13 11:05, Ian Bolton wrote:
The mode for AND should really be CC_NZ, so I fixed that up and in the TST
patterns that (erroneously) expected it to be CC mode.
It has been tested on linux and bare-metal.
OK to commit to trunk (as bug fix)?
Thanks.
Ian
13-02-01 Ian Bolton
Hi All,
This is simple fix that is aimed to help users in porting their
applications to x86 platforms which rely on an order of function
argument evaluation. To preserve direct order of argument evaluation
they need to be added additional option '-mno-push-args' to compile
that looks reasonable
So - back to PR55848 - this testcase shows that we still handle
builtins vs. non-builtins in a wrong way. If at compile-time
we chose to use a non-builtin variant we have to preserve that
(-fno-builtin) - easy to do at WPA stage by adjusting symbol
merging. Now, at LTRANS stage somebody clever
On 27/01/13 08:46, Venkataramanan Kumar wrote:
Hi Maintainers,
The attached patch backports the gcc trunk patch
http://gcc.gnu.org/ml/gcc-patches/2013-01/msg00143.html to
ARM/aarch64-4.7-branch branch.
ChangeLog.aarch64
2013-01-27 Venkataramanan Kumar venkataramanan.ku...@linaro.org
AIX 6.1 added an alignment argument to the .lcomm pseudo-op. This
fixes many of the remaining Altivec failures on AIX where GCC was
generating a zero vector in BSS, but the block was not appropriately
aligned.
I also took the opportunity to change ASM_OUTPUT_ALIGNED_COMMON use of
exact_log2 to
Hi!
I've committed following backports from trunk to 4.7 branch, after
bootstrapping/regtesting it on x86_64-linux and i686-linux.
Jakub
2013-02-01 Jakub Jelinek ja...@redhat.com
Backported from mainline
2012-11-13 Jakub Jelinek ja...@redhat.com
PR
On Fri, Feb 1, 2013 at 5:10 AM, Yuri Rumyantsev ysrum...@gmail.com wrote:
This is simple fix that is aimed to help users in porting their
applications to x86 platforms which rely on an order of function
argument evaluation. To preserve direct order of argument evaluation
they need to be added
Richard Stallman has given permission to include code derived from GNU
C Library in libgcc for AIX using the GCC Runtime Exception license.
The updated patch is appended. The GNU C Library code (cxa_atexit.c,
cxa_finalize.c, exit.h) is modified, so I am not exactly certain if my
reference to the
On 01/31/2013 02:02 AM, Jakub Jelinek wrote:
2013-01-31 Jakub Jelinekja...@redhat.com
PR debug/54793
* final.c (need_profile_function): New variable.
(final_start_function): Drop ATTRIBUTE_UNUSED from first argument.
If first of NOTE_INSN_BASIC_BLOCK or
On 01/31/2013 07:24 PM, Caroline Tice wrote:
On Wed, Jan 30, 2013 at 9:26 AM, Jason Merrill ja...@redhat.com wrote:
@@ -17954,6 +17954,10 @@ mark_class_instantiated (tree t, int ext
+ if (flag_vtable_verify)
+vtv_save_class_info (t);
Why do you need this here as well as in
Hi all,
This patch adds the tests for the ARMv8 AArch32 implementation of atomics.
It refactors some aarch64 tests and reuses them.
Ok for trunk or for the next stage 1 (together with part 1 at
http://gcc.gnu.org/ml/gcc-patches/2013-01/msg01441.html)?
Thanks,
Kyrill
gcc/testsuite/ChangeLog
Ummm... forgot the patch, sorry!
-Original Message-
From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
ow...@gcc.gnu.org] On Behalf Of Kyrylo Tkachov
Sent: 01 February 2013 17:37
To: gcc-patches@gcc.gnu.org
Cc: Ramana Radhakrishnan; Richard Earnshaw; Marcus Shawcroft
Subject:
Hi,
This patch moves the various tuning parameter data structures
further up config/aarch64/aarch64.c and then uses them to
initialise the generic_tunings variable. This mirrors their
position on trunk.
This fixes the warning:
config/aarch64/aarch64.c:129:33: warning: uninitialised const
Hi,
This patch series fixes a number of warnings in the AArch64 port on
the aarch64-4.7-branch.
The warnings fixed are:
---
[AArch64-4.7] Fix warning - Initialise generic_tunings.
config/aarch64/aarch64.c:129:33: warning: uninitialised const
‘generic_tunings’ is invalid in C++
Hi,
In config/aarch64/aarch64.c::aarch64_add_constant `shift' was
declared after we started writing code. C90 doesn't like this,
so split the declaration and the assignment.
This fixes the warning:
config/aarch64/aarch64.c: In function ‘aarch64_add_constant’:
config/aarch64/aarch64.c:2249:4:
Hi,
push_reload takes an `enum reload_type' as its final argument.
On trunk we just cast the int we have to the correct type,
so we do that here to mirror trunk and correct the warning.
We can't fix this by changing the type of the argument we take
as we would then need to forward declare the
Here is a new version of my patch, with the cleanup you requested.
2012-12-18 Christophe Lyon christophe.l...@linaro.org
gcc/
* config/arm/arm-protos.h (tune_params): Add
prefer_neon_for_64bits field.
* config/arm/arm.c (prefer_neon_for_64bits): New
Hi,
aarch64_simd_const_bounds declares `lane' after an assert. This
patch moves the declaration above the assert.
This patch fixes the warning:
config/aarch64/aarch64.c: In function ‘aarch64_simd_const_bounds’:
config/aarch64/aarch64.c:6412:3: warning: ISO C90 forbids mixed declarations
and
Hi,
emit_library_call takes an `enum library_type` as its second argument.
Currently aarch64-4.7-branch passes it an int 0.
This patch fixes this, mirroring trunk, by passing LCT_NORMAL instead.
This patch fixes the warning:
config/aarch64/aarch64.c: In function ‘aarch64_trampoline_init’:
Hi,
This patch is a backport of one approved here:
http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01135.html
The patch fixes the warning:
config/aarch64/aarch64.md:840: warning: source missing a mode?
Regression tested with no regressions on aarch64-none-elf.
OK for aarch64-4.7-branch?
LGTM
On Thu, Jan 31, 2013 at 8:54 PM, VandeVondele Joost
joost.vandevond...@mat.ethz.ch wrote:
The updated changelog entry is below, but somebody with write access should
do the commit, please.
2013-01-31 Dmitry Vyukov dvyu...@gcc.gnu.org
Joost VandeVondele
When I did the initial power7 port, I punted on allowing TImode in the VSX
registers because I couldn't get it to work. I am now revisiting it, and these
patches are my current effort, and I was wondering if people had comments on
them. In terms of performance, there are two benchmarks in the
Test successful so attached patch applied.
2013-02-01 François Dumont fdum...@gcc.gnu.org
* include/bits/hashtable_policy.h
(_Prime_rehash_policy::_M_next_bkt)
(_Prime_rehash_policy::_M_need_rehash): Move definition...
* src/c++11/hashtable_c++0x.cc: ... here.
*
The branch was merged with trunk @ 195676.
The branch was successfully bootstrapped on x86/x86-64.
Committed as rev. 195679.
On 13-01-31 6:36 PM, Steven Bosscher wrote:
On Wed, Jan 30, 2013 at 6:24 PM, Vladimir Makarov wrote:
The following patch fixes
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56144
The patch was successfully bootstrapped and tested on x86/x86-64.
Hello Vlad,
Can you please put this patch on the
The enclosed patch for Google 4.7 is an optimization for debug strings
under -gsplit-dwarf. Currently under -gsplit-dwarf, all strings with
DW_FORM_strp end up in the .debug_str.dwo section, which requires any
string not destined for the .dwo to use DW_FORM_string, disallowing any
duplication
33 matches
Mail list logo
