Jakub Jelinek ja...@redhat.com wrote:
Hi!
evaluate_stmt can be crashed similarly to what you've fixed today.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
Ok.
Thanks,
Richard.
2013-01-07 Jakub Jelinek ja...@redhat.com
PR middle-end/55890
*
Hi,
Please consider this as a reminder to review the patch posted at
following link:-
http://gcc.gnu.org/ml/gcc-patches/2012-12/msg00765.html
Please review the patch and let me know if its okay?
Thanks Regards,
Naveen.H.S
Hi,
AARCH64 back-end defines REGISTER_PREFIX to empty string.
Hence, it can be removed as the default value of REGISTER_PREFIX is .
Please find attached the patch that removes REGISTER_PREFIX and all its
occurrence in aarch64 back-end. Please review the patch and let me know
if there should be
Hi,
max (MAX_CONDITIONAL_EXECUTE) is doubled for IF-THEN-ELSE since there
is one more JUMP for the taken branch to goto the successor of
IF-THEN-ELSE. But when the last JUMP is a RETURN, the additional JUMP
can be optimized.
Here are the two different assemble codes the attached test case (-O2
On 8 January 2013 05:04, Hurugalawadi, Naveen
naveen.hurugalaw...@caviumnetworks.com wrote:
Hi,
ASM_FPRINTF_EXTENSIONS was copied from the arm back-end and is not
needed. Please find attached the patch that replaces %r in asm_fprintf
with reg_names. The definition of ASM_FPRINTF_EXTENSIONS is
On 8 January 2013 05:09, Hurugalawadi, Naveen
naveen.hurugalaw...@caviumnetworks.com wrote:
Hi,
AARCH64 back-end defines REVERSE_CONDITION but not REVERSIBLE_CC_MODE.
REVERSE_CONDITION is used only in case REVERSIBLE_CC_MODE (mode) is
nonzero.
Please find attached the patch that defines
On Mon, Jan 7, 2013 at 7:21 PM, Jagasia, Harsha harsha.jaga...@amd.com wrote:
We would like to propose changing AVX generic mode tuning to generate
128-bit AVX instead of 256-bit AVX.
You indicate a 3% reduction on bulldozer with avx256.
How does avx128 compare to -mno-avx -msse4.2?
Will the
Hi,
a simple ICE on invalid: the problem manifests itself when, during error
recovery, var_defined_without_dynamic_init does
TYPE_HAS_NONTRIVIAL_DESTRUCTOR (TREE_TYPE (var)) for a VAR_DECL which
has error_mark_node as TREE_TYPE.
It seems to me that a good place to avoid this is
On Mon, Jan 7, 2013 at 8:45 PM, Jeff Law l...@redhat.com wrote:
On 01/05/2013 01:10 PM, Steven Bosscher wrote:
Presumably BB7 was created in response to the builtin_unreachable?
Yes. The block only contains the BB_UNREACHABLE call. It is cleaned up
at the end of the GIMPLE passes pipeline,
On Sat, Jan 5, 2013 at 9:10 PM, Steven Bosscher stevenb@gmail.com wrote:
On Thu, Jan 3, 2013 at 9:51 PM, Jeff Law wrote:
On 01/03/2013 12:01 PM, Steven Bosscher wrote:
Hello,
Consider the following test case:
void bar (void);
int foo (int b, int c, int d)
{
int r = 0;
if (b)
Hi Richard,
Hmm? We compile with a C++ compiler where this is perfectly valid ...
I was compiling with GCC 4.7 where it gave me a warning... I don't know
much about C++ anymore, so I didn't know. Oh well!
Ah, for the 4.7 branch yes.
Eric Botcazou asked that we have the same code for
On Tue, Jan 8, 2013 at 12:37 PM, Joel Brobecker brobec...@adacore.com wrote:
Hi Richard,
Hmm? We compile with a C++ compiler where this is perfectly valid ...
I was compiling with GCC 4.7 where it gave me a warning... I don't know
much about C++ anymore, so I didn't know. Oh well!
Ah,
On Fri, Jan 04, 2013 at 02:00:39PM +0100, Martin Jambor wrote:
2013-01-03 Martin Jambor mjam...@suse.cz
PR debug/55579
* tree-sra.c (analyze_access_subtree): Return true also after
potentially creating a debug-only replacement.
testsuite/
*
Hi,
The AArch64 port has support for integer vcond, but did not have
support for floating-point vcond.
This patch adds this support and enables check_effective_target_vect_cond
in the testsuite.
Regression tested on aarch64-none-elf with no regressions.
Is this OK to commit?
Thanks,
James
Status
==
Stage3 has now officially ended after lasting a bit more than two months.
This means that GCC trunk is now in release branch mode, thus only
regression fixes and documentation changes are allowed now.
Upcoming GCC 4.8 has stabilized itself over the holidays and I am
aware of
g++.dg/debug/dwarf2/pr54508.C is FAILing on Solaris 9/x86 (both with as
and gas):
FAIL: g++.dg/debug/dwarf2/pr54508.C -std=gnu++98 scan-assembler c0[
\\t]+[#;/!|@]+
DW_AT_name[\\r\\n]+[^\\r\\n]+[\\r\\n]+[^\\r\\n]+[\\r\\n]+[^#;/!|@]+[#;/!|@]+
DW_AT_decl_line[\\r\\n]+[^#;/!|@]+[#;/!|@]+
On Tue, Jan 08, 2013 at 01:11:24PM +0100, Rainer Orth wrote:
Ok for mainline?
Yes, thanks.
2013-01-08 Rainer Orth r...@cebitec.uni-bielefeld.de
* g++.dg/debug/dwarf2/pr54508.C: Allow for more whitespace after
asm comments.
Jakub
Hello,
I just noticed that part of the proposal we made for...
http://gcc.gnu.org/wiki/DW_AT_GNAT_descriptive_type
... got missed in the patch that got checked in:
http://gcc.gnu.org/ml/gcc-patches/2011-04/msg00099.html
In particular, we're missing the second part, where we are
expected to
Eric Botcazou asked that we have the same code for both 4.7 and HEAD.
Would it be OK to apply it to both? It's not really strictly
necessary for the HEAD, but I don't see it as being harmful either.
Sure.
Thank you! Now checked in.
--
Joel
Hi,
On Mon, Jan 07, 2013 at 01:26:23AM +0100, Jan Hubicka wrote:
Hi,
as discused in the PR log there seems to be ordering issue in
update_indirect_edges_after_inlining that first updates info in call edge to
correspond the situation after inlining and then it tries to devirtualize that
is
On Tue, Jan 8, 2013 at 2:29 PM, Martin Jambor mjam...@suse.cz wrote:
Hi,
On Mon, Jan 07, 2013 at 01:26:23AM +0100, Jan Hubicka wrote:
Hi,
as discused in the PR log there seems to be ordering issue in
update_indirect_edges_after_inlining that first updates info in call edge to
correspond the
Hi,
This patch fixes the support for vectorizing sqrt and sqrtf
function calls on AArch64. While the standard name was implemented
previously, the glue in aarch64_builtin_vectorized_function was not.
We also fix the initialisation of vectors in the
gcc.target/aarch64/vsqrt.c testcase such that
Hello,
Consider the example of the problem report
1 template typename
2 constexpr bool the_truth () { return true; }
3
4 template bool
5struct Takes_bool { };
6
7 templatebool B
8using Alias = Takes_boolB;
9
10 templatetypename T
On Mon, Nov 5, 2012 at 12:23 PM, Jan Hubicka hubi...@ucw.cz wrote:
Hi,
in 4.6 timeframe I limited early inlier growth to apply only for leaf
functions.
This does not work really well, because with less propagation of address
expressions
we are really not 100% succesfull on detecting C++
Hi,
Attached is a patch that fixes the instruction and operand separator for
sumull2 instructions from a space to a tab.
Regressed for aarch64-none-elf on aarch64-4.7-branch. OK to commit?
Thanks,
Tejas Belagod
ARM.
2013-01-08 Tejas Belagod tejas.bela...@arm.com
gcc/
*
Hi,
Attached is a patch that fixes the instruction and operand separator for
sumull2 instructions from a space to a tab.
Regressed for aarch64-none-elf on trunk. OK to commit?
Thanks,
Tejas Belagod
ARM.
2013-01-08 Tejas Belagod tejas.bela...@arm.com
gcc/
*
Hi,
Attached is a patch that makes the test case for sumullq more robust by
looking for {scan-assembler smull v[0-9]+\.type} where type = {8h,
4s, 2d} and smull2 v[0-9]+\.type} where type = {8h, 4s, 2d} instead of
looking for a specific number of occurances of smull v which can vary with the
On 8 January 2013 13:55, James Greenhalgh james.greenha...@arm.com wrote:
Hi,
This patch fixes the support for vectorizing sqrt and sqrtf
function calls on AArch64. While the standard name was implemented
previously, the glue in aarch64_builtin_vectorized_function was not.
We also fix the
On 8 January 2013 12:04, James Greenhalgh james.greenha...@arm.com wrote:
Hi,
The AArch64 port has support for integer vcond, but did not have
support for floating-point vcond.
This patch adds this support and enables check_effective_target_vect_cond
in the testsuite.
Regression tested
OK
/Marcus
On 8 January 2013 14:27, Tejas Belagod tbela...@arm.com wrote:
Hi,
Attached is a patch that makes the test case for sumullq more robust by
looking for {scan-assembler smull v[0-9]+\.type} where type = {8h,
4s, 2d} and smull2 v[0-9]+\.type} where type = {8h, 4s, 2d} instead of
On 8 January 2013 14:25, Tejas Belagod tbela...@arm.com wrote:
2013-01-08 Tejas Belagod tejas.bela...@arm.com
gcc/
* config/aarch64/aarch64-simd.md
(aarch64_simd_vec_sumult_lo_mode,
aarch64_simd_vec_sumult_hi_mode): Separate instruction and
operand
with tab
So this counts all calls in the function we want to inline (!?).
That's completely
backward to me. In fact for forwarder functions you still only allow half
of the early-inlining-insns growth. Previously for non-leafs we didn't allow
any growth (hm, why?).
Well, the idea is that inlining
I'm seeing various failures in the g++.dg/tls/thread_local* tests on
Solaris 9:
With Sun as, I have
XPASS: g++.dg/tls/thread_local-cse.C execution test
XPASS: g++.dg/tls/thread_local2.C execution test
XPASS: g++.dg/tls/thread_local2g.C execution test
XPASS: g++.dg/tls/thread_local6.C execution
On 01/08/2013 04:26 AM, Richard Biener wrote:
The issue is VRP - when you remove unreachable blocks you lose the
conditional statement as it is no longer necessary and thus the predicate
you can derive value-ranges from.
Understood. Perhaps we could eliminate them after the first VRP pass,
Ping?
http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01197.html
Thanks,
Christophe
On 19 December 2012 16:59, Christophe Lyon christophe.l...@linaro.org wrote:
On 17 December 2012 16:12, Richard Earnshaw rearn...@arm.com wrote:
On 29/11/12 17:16, Christophe Lyon wrote:
On trunk I have noticed
On Mon, 2013-01-07 at 12:54 -0800, Steve Ellcey wrote:
On Mon, 2013-01-07 at 20:38 +, Richard Sandiford wrote:
Ah, sorry, this reminded me of a patch I'd written a year ago and never
got around to sanity-checking. Does it fix the problem for you?
Richard
It fixes my small
Hi,
My patch to add bounds that are not dominating loop latch caused problem in
scev_probably_wraps_p that is trying to prove that given IV at given STMT is
not wrapping based on loop bounds. When I was extending loop bounds to contain
not only statements that dominate the loop latch, I verified
Jakub Jelinek ja...@redhat.com writes:
2012-12-19 Jakub Jelinek ja...@redhat.com
PR fortran/55341
* asan.c (asan_clear_shadow): New function.
(asan_emit_stack_protection): Use it.
This looks OK to me. Thanks.
--
Dodji
On Tue, Jan 8, 2013 at 7:58 AM, Dodji Seketeli do...@redhat.com wrote:
Hello,
Consider the example of the problem report
1 template typename
2 constexpr bool the_truth () { return true; }
3
4 template bool
5struct Takes_bool { };
6
7
Hi,
I actually attached not completely final version of the patch. This one has
the extra loop looking for side effect that cures the first testcase.
Sorry for the confussion.
Honza
PR tree-optimize/55875
* gcc.c-torture/execute/pr55875.c: New testcase.
*
On Tue, Jan 08, 2013 at 05:49:28PM +0100, Jan Hubicka wrote:
--- testsuite/gcc.c-torture/execute/pr55875.c (revision 0)
+++ testsuite/gcc.c-torture/execute/pr55875.c (revision 0)
@@ -0,0 +1,17 @@
Please add
/* PR tree-optimization/55875 */
here.
+int a[250];
+__attribute__ ((noinline))
On Tue, 8 Jan 2013, Richard Sandiford wrote:
I disabled 64 bit FPU instructions by -msoft-float. This works, but
using -msingle-float fails. This would be the better
configuration. There are still 64 bit FPU instructions used (e.g. dmfc1
$2,$f0 when using long double multiplication).
On Tue, Jan 8, 2013 at 12:32 PM, Richard Biener wrote:
Does it handle side-effects on the builtin-unreachable path correctly?
int b;
int a;
extern void foo ();
int main()
{
if (!a)
{
if (!b)
foo ();
__builtin_unreachable ();
}
}
---
void foo () {
On 01/07/2013 03:26 PM, Jakub Jelinek wrote:
2012-01-08 Jakub Jelinek ja...@redhat.com
Uros Bizjak ubiz...@gmail.com
PR rtl-optimization/55845
* df-problems.c (can_move_insns_across): Stop scanning at
volatile_insn_p source instruction or give up if
Maciej W. Rozycki ma...@codesourcery.com writes:
On Tue, 8 Jan 2013, Richard Sandiford wrote:
I disabled 64 bit FPU instructions by -msoft-float. This works, but
using -msingle-float fails. This would be the better
configuration. There are still 64 bit FPU instructions used (e.g. dmfc1
On Fri, Dec 21, 2012 at 5:14 AM, Richard Biener rguent...@suse.de wrote:
After the Ada fix including gmp.h from system.h is trivial
(by means of double-int.h it was included from almost everywhere
already)
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Ok for trunk? (Go
On 01/08/2013 08:58 AM, Dodji Seketeli wrote:
There, when we check the argument 'the_truthint()' to see if it
actually is a constant expression, in check_instantiated_arg, we fail
to recognize its constexpr-ness b/c we just look at its TREE_CONSTANT.
The problem is that by the time we get to
Hi!
As discussed in the PR, on the following testcase we've regressed with the
introduction of c_fully_fold, when the C FE normally warns the argument
isn't folded yet. Fixed by also warning in c_fully_fold_internal, if before
that function the shift count wasn't INTEGER_CST and after it it is.
Hi!
This is Steven's patch from the PR plus mine hunk, bootstrapped/regtested on
x86_64-linux and i686-linux, ok for trunk?
2013-01-08 Steven Bosscher ste...@gcc.gnu.org
Jakub Jelinek ja...@redhat.com
PR tree-optimization/48189
* predict.c (predict_loops): If max
On Sun, Jan 6, 2013 at 6:52 PM, Tobias Burnus bur...@net-b.de wrote:
** ping **
Attached is a small variation, which in addition handles the case that a
non-BOOL_C LOGICAL, Bind(C) dummy argument (or result variable) is used in a
procedure call. In that case, the variable is now converted to
I think I'd rather handle this by returning false from
var_needs_tls_wrapper.
Jason
Hi!
No matter whether LRA (if it is a bug in there) is fixed or not,
*vec_concatv2df could handle for !avx sse3 x - x, 1 alternative the same
as it handles x - m, 1 alternative (using movddup).
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2013-01-08 Jakub Jelinek
Here's the patch that Joseph asked for to make mkheaders.in print
a single copyright year. Tested on x86_64-linux-gnu. OK to install?
Richard
fixincludes/
* mkheaders.in: Print 2013 as the copyright year.
Index: fixincludes/mkheaders.in
Here's the result of running the copyright update script on fixincludes/.
Tested on x86_64-linux-gnu. OK to install?
Hope we don't need to list every file in the ChangeLog for this kind
of thing :-)
Richard
fixincludes/
Update copyright.
Index: gcc/fixincludes/fixfixes.c
Hi,
here is even more updated patch, this time really fixing the testcase, I hope ;)
It turns out there is one extra problem in tree-ssa-loop-niter.c triggered by
that code. Some bounds, like one based on inequality test or with wrapping
IVs are bounds only when they are executed every iteration.
After some new suggestions from Uros, I've made a new diff.
Change log:
* config/gthr.m4: Added rdos thread header.
* gcc/config/i386/i386.c: Provided a way to define a default setting for
medium memory model and PIC using TARGET_RDOS define.
* gcc/config/i386/i386.h: Defined TARGET_RDOS macro.
This fixes a 4.8 regression in std::mem_fn.
PR libstdc++/55908
* include/std/functional (_Mem_fn::operator()): Fix constraints to
avoid ambiguity.
* testsuite/20_util/function_objects/mem_fn/55908.cc: New.
* testsuite/20_util/bind/ref_neg.cc: Adjust
Hello,
a small, unexciting bug.
For the case:
subroutine m()
use m
end subroutine m
the USE statement is rejected, but it is not if the subroutine is contained.
In the latter case, the namespace of the symbol of the subroutine is the
parent namespace, which confuses the error
Hello Richard,
cvt.w.s is replaced by trunc.w.s. This seems to work.
Probably showing my ignorance, but I couldn't see this in the patch.
trunc.w.s is enabled by ISA_HAS_TRUNC_W_S. This automatically disables cvt.w.s,
because trunc.w.s is preferred.
I disabled 64 bit FPU instructions by
I was going to fix this missing feature, but as Richard just announced
Stage 3 has ended I'll just update the docs and wait for trunk to
reopen.
* doc/xml/manual/status_cxx2011.xml: Document that N3189 is missing.
Committed to trunk and 4.7
commit d5a292b9ce2ebbe48ab2a9b6823554c86d2bfa06
On Tue, Jan 08, 2013 at 10:06:17PM +0100, Mikael Morin wrote:
a small, unexciting bug.
For the case:
subroutine m()
use m
end subroutine m
the USE statement is rejected, but it is not if the subroutine is contained.
In the latter case, the namespace of the symbol of the
On Tue, 8 Jan 2013, Jakub Jelinek wrote:
Hi!
As discussed in the PR, on the following testcase we've regressed with the
introduction of c_fully_fold, when the C FE normally warns the argument
isn't folded yet. Fixed by also warning in c_fully_fold_internal, if before
that function the
Hello Maciej,
ll, sc, dmult, ddiv, cvt.w.s, 64 bit FPU instructions.
ll and sc is disabled with -mno-llsc and works.
cvt.w.s is replaced by trunc.w.s. This seems to work.
Probably showing my ignorance, but I couldn't see this in the patch.
This has raised my attention -- AFAICS
Janne Blomqvist worte:
On Sun, Jan 6, 2013 at 6:52 PM, Tobias Burnusbur...@net-b.de wrote:
Attached is a small variation, which in addition handles the case that a
non-BOOL_C LOGICAL, Bind(C) dummy argument (or result variable) is used in a
procedure call. In that case, the variable is now
Hi!
I merged this patch from Binutils, which defines a dep on gas for
various other Binutils components:
2013-01-07 Jan-Benedict Glaw jbg...@lug-owl.de
* Makefile.def: Merge from binutils.
* Makefile.in: Dito.
Index: Makefile.in
Hi!
I merged this patch:
2013-01-08 Jan-Benedict Glaw jbg...@lug-owl.de
* config.sub: Merge from config repo.
* config.guess: Dito.
Index: config.sub
===
--- config.sub (revision 195037)
+++ config.sub
IIRC we defined doubles as 32bits wide in our old port. We simply
didn't support 64bit wide doubles. I don't remember what mechanism we
used to make this happen.
Ah, yeah.
I think limiting wide doubles would be good.
I tried to disable dmult and ddiv (see mips.md). Disabling
On 8 January 2013 21:33, Jonathan Wakely wrote:
I was going to fix this missing feature, but as Richard just announced
Stage 3 has ended I'll just update the docs and wait for trunk to
reopen.
* doc/xml/manual/status_cxx2011.xml: Document that N3189 is missing.
Committed to trunk
Ping**2?
This was submitted before the review, so I think it should still be OK.
Ping?
http://gcc.gnu.org/ml/fortran/2013-01/msg0.html
Hello world,
the attached patch replaces ANY(a, b, c) with a .or. b .or c,
leading to reduced execution time. It also handles ALL, PRODUCT
and SUM.
Hi,
On 01/08/2013 09:00 PM, Jason Merrill wrote:
I think I'd rather handle this by returning false from
var_needs_tls_wrapper.
Ah Ok. Then what about the below?
Thanks,
Paolo.
//
/cp
2013-01-09 Paolo Carlini paolo.carl...@oracle.com
PR c++/55801
*
-Original Message-
From: H.J. Lu [mailto:hjl.to...@gmail.com]
Sent: Tuesday, January 08, 2013 1:50 PM
To: Richard Biener; Iyer, Balaji V
Cc: gcc-patches@gcc.gnu.org; Diego Novillo; i...@google.com
Subject: Re: [PATCH] Fix PR54659, include gmp.h from system.h
On Fri, Dec 21, 2012
The attached change updates the extract and insert patterns on HP PA.
It removes the deprecated extzv, extv and insv expanders, replacing them
with SI and DI mode variant. Operand predicates are tightened in these
and related insn patterns. Predicates are also tightened some shift
patterns.
Two
Hi Marcus,
Thanks for reviewing the patch.
Given the comment about SELECT_CC_MODE and the implementation of
aarch64_select_cc_mode this definition of REVERSIBLE_CC_MODE looks
broken to me.
Please find attached the modified patch that does not allow floating
point inequality comparisons in
Hi Maintainers,
Please fine below patch that sets preferred vectorization mode for btver2 as
avx128.
We tested some benchmarks and found that enabling 128-bit AVX instruction
generation by the auto vectorizer performs better than
default 256-bit AVX.
Completed bootstrap and make -k check
On 01/08/2013 03:49 PM, Jürgen Urban wrote:
@Jeff: I think you know the stringent copyright rules for GCC. I want
to use the code from the original patch, but I don't know how many
people were involved. So I can't use it without copyright problems.
Can you please tell me which code can I use
On Wed, Jan 9, 2013 at 6:05 AM, Kumar, Venkataramanan
venkataramanan.ku...@amd.com wrote:
Please fine below patch that sets preferred vectorization mode for btver2 as
avx128.
We tested some benchmarks and found that enabling 128-bit AVX instruction
generation by the auto vectorizer
On Tue, Jan 8, 2013 at 9:32 PM, Leif Ekblad l...@rdos.net wrote:
After some new suggestions from Uros, I've made a new diff.
Change log:
* config/gthr.m4: Added rdos thread header.
* gcc/config/i386/i386.c: Provided a way to define a default setting for
medium memory model and PIC using
77 matches
Mail list logo
