On 01/22/14 09:02, Michael Eager wrote:
On 01/22/14 07:43, Michael Eager wrote:
On 01/22/14 02:55, David Holsgrove wrote:
Hi Michael,
On 26 November 2013 17:48, David Holsgrove wrote:
Hi Michael,
Please find attached same patch based against latest from gcc master.
Can this be applied and
On 16/01/2014 11:44, Jason Merrill wrote:
> My preference would be to turn -Wreturn-type on by default, but not
> create the separate -Wmissing-return flag. As I argued in 2002, there
> should only be one flag.
I don't have any opinion on the subject. The separate option or not is
fine with me. I
Comments added. I create another patch to add the parameter for AVG_LOOP_ITER.
Both patches are attached.
Thanks,
Wei.
On Wed, Jan 22, 2014 at 4:42 PM, Xinliang David Li wrote:
> On Wed, Jan 22, 2014 at 2:23 PM, Wei Mi wrote:
>> This patch handles the mem access builtins in ivopt. The original
Hi Jakub,
Did you get a chance to look at this? Is it OK to install to trunk?
Thanks,
Balaji V. Iyer.
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Iyer, Balaji V
> Sent: Sunday, January 19, 2014 10:37 PM
> To: J
On Tue, Jan 21, 2014 at 3:55 PM, Jan Hubicka wrote:
>> On 01/17/14 14:32, Jan Hubicka wrote:
>> >>* combine-stack-adj.c (combine_stack_adjustments_for_block): Remove
>> >>ARG_SIZE note when adjustment was eliminated.
>> >
>> >Ping... This patch prevents me from switching the accumulate-ar
On 01/22/14 20:46, Alan Modra wrote:
I was hoping for a reply from someone who could OK the previous patches
submitted. Admittedly, I didn't tick all the boxes (no changelog entry),
so here they are again.
It's been in my stack of patches, others may be shying away from the
insanity that is our
On 01/19/14 10:33, Richard Sandiford wrote:
The MIPS %hi and %lo relocation operators act as a pair on REL targets;
you need to see the partnering %lo in order to calculate the addend for
a %hi and detect carries properly. The assembler therefore complains if
%hi is used without a corresponding
I was hoping for a reply from someone who could OK the previous patches
submitted. Admittedly, I didn't tick all the boxes (no changelog entry),
so here they are again.
The Makefile.in BUILD_CPPFLAGS change is for exactly the same reason
as my 2013-12-05 change. When GMPINC points at an installe
> On 19 January 2014 03:12:56 Jan Hubicka wrote:
>
> >Hi,
> >while comparing LTO and non-LTO builds I noticed that with LTO we produce a
> >lot
> >more vtables in datal.rel.ro rather than data.rel.ro.local
> >This is because of partitioning promoting more symbols global. For RTL we
> >make
> >s
During floating point comparison, compiler inserts conditional jumps
to check if the operand is NAN. These type of checks are normally
false. However, compiler sets the probability the same as the original
float-compare conditional jump. This patch sets the probability of
these conditional jumps as
On Wed, Jan 22, 2014 at 2:02 PM, H.J. Lu wrote:
> On Mon, Jan 20, 2014 at 1:11 AM, Uros Bizjak wrote:
>> On Mon, Jan 20, 2014 at 9:38 AM, Jakub Jelinek wrote:
>>
>>> As mentioned in the PR or even in the comment below, ix86_decompose_address
>>> sometimes sets parts.base to some REG and parts.di
On Wed, Jan 22, 2014 at 2:23 PM, Wei Mi wrote:
> This patch handles the mem access builtins in ivopt. The original
> problem described here:
> http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02648.html
>
> Bootstrapped and passed regression test. Performance test ok for
> plain, fdo and lipo. Ok for
Follow-up patch to make the exception specs on the default constructors
conditional, depending on the allocator.
Tested x86_64-linux, committed to trunk.
commit 67b0d66cc6a1af5f697543d24ad7578d81c5eb98
Author: Jonathan Wakely
Date: Wed Jan 22 23:07:23 2014 +
PR libstdc++/58764
ok.
David
On Wed, Jan 22, 2014 at 3:23 PM, Dehao Chen wrote:
> Unfortunately, copy_cfg_body is actually using basic block count
> instead of cgraph edge count. Thus even fixing up the call graph does
> not solve the problem. The 2nd chunk of the patch (cgraphclones.c) is
> actually not necessary
Unfortunately, copy_cfg_body is actually using basic block count
instead of cgraph edge count. Thus even fixing up the call graph does
not solve the problem. The 2nd chunk of the patch (cgraphclones.c) is
actually not necessary. We only need the first part (tree-inline.c).
Thanks,
Dehao
On Fri, J
On Wed, Jan 22, 2014 at 1:51 PM, Pat Haugen wrote:
> Discovered that we blindly set flag_ira_loop_pressure at -O3+, regardless of
> whether command line option was given. Following fixes that.
>
> Bootstrap/regtest with no new regressions, ok for trunk?
>
> -Pat
>
>
> 2014-01-22 Pat Haugen
>
>
On 22 January 2014 19:39, Paolo Carlini wrote:
> On 01/21/2014 04:24 PM, Jason Merrill wrote:
>>
>> OK, thanks.
>
> I don't think Ville has Write After Approval, thus I'm going to commit this
> on his behalf.
Oh, I was expecting Jason would do that. Note that Marek Polacek pointed
out two format
This patch handles the mem access builtins in ivopt. The original
problem described here:
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02648.html
Bootstrapped and passed regression test. Performance test ok for
plain, fdo and lipo. Ok for google 4.8 branch?
Thanks,
Wei.
--- /usr/local/google/hom
Hi Paul,
> This is a straightforward patch that is completely described in the
> ChangeLog entry. I am surprised that this could be a 4.8 regression
> since, as far as I am aware, SELECT_TYPE was not capable of handling
> array selectors before... Nonetheless, it flagged it up for me :-)
well, ac
On Mon, Jan 20, 2014 at 1:11 AM, Uros Bizjak wrote:
> On Mon, Jan 20, 2014 at 9:38 AM, Jakub Jelinek wrote:
>
>> As mentioned in the PR or even in the comment below, ix86_decompose_address
>> sometimes sets parts.base to some REG and parts.disp to const0_rtx, even
>> when the operands aren't of a
On 01/22/2014 10:10 PM, Jason Merrill wrote:
Yep, that's along the lines I was thinking of. But again, prev_scope is
irrelevant here, so the new code shouldn't mention it at all.
Well, in practice I have to mention it in the error_at itself. Otherwise
I'm finishing testing the below.
Paolo.
I had taken this code out as the original cases I'd encountered were
better handled by reorganization the order in which we thread blocks.
However, as seen in 59597, there's still clearly cases where a jump
threading path with a joiner block can have a threaded subpath.
Threading the joiner
On Wed, 22 Jan 2014, Marek Polacek wrote:
> 2014-01-22 Marek Polacek
>
> PR c/59891
> c/
> * c-typeck.c (build_conditional_expr): Call c_fully_fold instead
> of remove_c_maybe_const_expr on op1 and op2.
> testsuite/
> * gcc.dg/torture/pr59891.c: New test.
OK.
--
Jose
Yep, that's along the lines I was thinking of. But again, prev_scope is
irrelevant here, so the new code shouldn't mention it at all.
Original Message
From: Paolo Carlini
Sent: Wed, Jan 22, 2014 03:34 PM
To: Jason Merrill ; gcc-patches@gcc.gnu.org
CC:
Subject: Re: [C++ Pa
As mentioned in the PR, C FE leaked C_MAYBE_CONST_EXPR into GIMPLE.
This happened because remove_c_maybe_const_expr doesn't look for
nested C_MAYBE_CONST_EXPRs. But c_fully_fold will fold these away,
so use that.
Regtested/bootstrapped on x86_64-linux, ok for trunk and 4.8?
Alternatively, we cou
Hi,
On 01/22/2014 06:13 PM, Jason Merrill wrote:
On 01/21/2014 09:55 AM, Jason Merrill wrote:
I think I would prefer to change the "child" assert to be
MAYBE_CLASS_TYPE_P rather than CLASS_TYPE_P.
On second thought, no, I think we do want to specifically handle
TYPENAME_TYPE. But I think we w
This undoes the recent change to make the containers' default
constructors explicit, and makes the Debug Mode and Profile Mode
associative containers consistent with normal mode.
The new C++11 containers (forward_list and unordered_*) still have
explicit default constructors, which is probably wr
On 1/22/2014, 2:41 PM, Jakub Jelinek wrote:
On Wed, Jan 22, 2014 at 02:40:46PM -0500, Vladimir Makarov wrote:
The following patch fixes
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59477
The patch was successfully bootstrapped and tested on x86/x86-64.
Committed as rev. 206938.
2014-
On Wed, Jan 22, 2014 at 02:40:46PM -0500, Vladimir Makarov wrote:
> The following patch fixes
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59477
>
> The patch was successfully bootstrapped and tested on x86/x86-64.
>
> Committed as rev. 206938.
>
> 2014-01-22 Vladimir Makarov
>
>
The following patch fixes
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59477
The patch was successfully bootstrapped and tested on x86/x86-64.
Committed as rev. 206938.
2014-01-22 Vladimir Makarov
PR rtl-optimization/59477
* lra-constraints.c (inherit_in_ebb): Process
On Wed, Jan 22, 2014 at 10:16 AM, Matthias Klose wrote:
>
> Ok, but I cannot do this directly. gcc_cv_ld may already be an absolute path.
> So now I'm checking the very same location as gcc_cv_ld first, then fall back
> to
> AC_PATH_PROG.
When I look at gcc/configure.ac and gcc/exec-tool.in, it
On Wed, Jan 22, 2014 at 10:16 AM, Matthias Klose wrote:
> Am 18.01.2014 03:03, schrieb Ian Lance Taylor:
>> On Fri, Nov 29, 2013 at 5:29 AM, Matthias Klose wrote:
>>> to get full advantage of the -fsplit-stack option, gccgo binaries have to be
>>> linked with gold, not the bfd linker. When the s
Discovered that we blindly set flag_ira_loop_pressure at -O3+,
regardless of whether command line option was given. Following fixes that.
Bootstrap/regtest with no new regressions, ok for trunk?
-Pat
2014-01-22 Pat Haugen
* config/rs6000/rs6000.c (rs6000_option_override_internal):
The current trunk will not bootstrap on a powerpcle64 power8 box if
--with-cpu=power8 is selected. This has been traced down to the fact that we
did not swap the double words when we used the quad memory instructions.
In this patch, I split the ISA 2.07 quad memory support into two parts, one for
Am 18.01.2014 03:03, schrieb Ian Lance Taylor:
> On Fri, Nov 29, 2013 at 5:29 AM, Matthias Klose wrote:
>> to get full advantage of the -fsplit-stack option, gccgo binaries have to be
>> linked with gold, not the bfd linker. When the system linker defaults to the
>> bfd linker, then gccgo should
On 01/21/2014 04:24 PM, Jason Merrill wrote:
OK, thanks.
I don't think Ville has Write After Approval, thus I'm going to commit
this on his behalf.
Thanks,
Paolo.
On 01/21/2014 09:55 AM, Jason Merrill wrote:
I think I would prefer to change the "child" assert to be
MAYBE_CLASS_TYPE_P rather than CLASS_TYPE_P.
On second thought, no, I think we do want to specifically handle
TYPENAME_TYPE. But I think we want a different error message; getting a
TYPENAM
Jan-Benedict Glaw pointed out to me that my recent ansidecl.h change
caused a build failure for CR16. I had missed a couple spots where
PARAMS was still used in the gcc tree.
I'm checking in this patch as obvious.
Tom
2014-01-22 Tom Tromey
* config/i386/i386-interix.h (i386_pe_uniqu
In SPARK 2005, it is not permitted to have a call to a subprogram
in the same unit as the subprogram if the body occurs later on.
This implements that rule if restriction SPARK_05 is active as
shown by the following example:
1. pragma Restrictions (SPARK_05);
2. package SPARKRec2 is
An expression function that is not a completion can appear in a protected body
and requires the same renaming declarations as other protected operations.
The following must compile quietly:
---
with Private_Types;
procedure Main is
package Integer_Buffer is new
Private_Types (Element =>
On 01/22/14 07:43, Michael Eager wrote:
On 01/22/14 02:55, David Holsgrove wrote:
Hi Michael,
On 26 November 2013 17:48, David Holsgrove wrote:
Hi Michael,
Please find attached same patch based against latest from gcc master.
Can this be applied and backported to gcc-4_8-branch when reviewe
This change fixes a compiler crash occurring in some cases of constant
declarations initialized with a call to an instance of a generic function,
when the returned type is an array of dynamically sized elements.
The following compilation must be accepted quietly:
$ gcc -c p.adb
package Q is
fu
Hi Marcus,
After we changed the frame growing direction (downwards) in Aarch64,
the back-end now generates stack smashing set and test based on
generic code available in GCC.
But most of the ports (i386, spu, rs6000, s390, sh, sparc, tilepro and
tilegx) define machine descriptions using standard
This patch fixes a visibility problem in the presence of formal packages that
have themselves formal packages declared with a box. In a generic unit the
formals of such packages are visible, and this visibility must be properly
reflected when compiling an instance.
The following must compile qui
Volatile variables are never considered valid for the purposes
of validity checking, since the assumption is they could change
unexpectedly at any time.
The following program, compiled with -gnatVa -gnatG
1. procedure ValidVolatile is
2.type R is new Integer range 1 .. 10;
3.
On 06/01/14 11:52, Alex Velenko wrote:
Hi,
This patch fixes vector shift by 64 behavior to meet reference
manual expectations. Testcase included to check that expectations
are now met. No regressions found.
Is patch OK?
Thanks,
Alex
2014-01-06 Alex Velenko
gcc/
* config/aarch64/aarc
In SPARK 2005, a subprogram may not contain a direct call to
itself. This patch checks this if SPARK_05 restriction is set
as shown in the following example:
1. pragma Restrictions (SPARK_05);
2. package SPARKRec is
3.procedure p1 (X : Boolean; Y : Integer);
4. end SPARKRec
This patch does two things with respect to the new illegalities in Ada
2012 regarding late declaration of equality for untagged types. First
these errors can be converted to warnings using the -gnatd.E switch.
Second, in earlier versions of Ada, if the -gnatwy switch is set (warn
on Ada incompatibi
On Wed, Jan 22, 2014 at 2:55 PM, Ilya Tocar wrote:
>> > I found out that we forgot to implement some of AVX512 intrinsics.
>> > Here is a patch that adds them. Sorry for huge patch, but changes are
>> > mostly trivial.
>> > Ok for trunk?
>>
>> > +(define_insn "avx512f_2_mask_store"
>> > + [(set
On 01/22/14 02:55, David Holsgrove wrote:
Hi Michael,
On 26 November 2013 17:48, David Holsgrove wrote:
Hi Michael,
Please find attached same patch based against latest from gcc master.
Can this be applied and backported to gcc-4_8-branch when reviewed.
thanks,
David
On 15 July 2013 14:49,
This patch implements fully the rule of 13.11(3) that forbids having both
a Storage_Pool and Storage_Size attribute specified for the same type, as
shown by the following example:
1. with System.Storage_Elements; use System.Storage_Elements;
2. with System.Storage_Pools;use System.St
On 01/22/14 02:50, David Holsgrove wrote:
Hi Michael,
On 22 January 2014 13:43, David Holsgrove wrote:
-Original Message-
From: Michael Eager [mailto:ea...@eagerm.com]
Sent: Friday, 17 January 2014 4:36 am
To: David Holsgrove; gcc-patches@gcc.gnu.org
Cc: Edgar Iglesias; John Williams;
Hi,
This patch improves support for context diffs in mklog and also fixes
tiny bug which caused generation of redundant colons in output.
Verified against several real-world patches.
Ok to commit?
-Y
diff --git a/contrib/mklog b/contrib/mklog
index 16ce191..c6d89a9 100755
--- a/contrib/mklog
Tested x86_64-linux, committed to trunk.
commit ed8eb245c7778ac2ab17a7c29dddc527c3db497e
Author: Jonathan Wakely
Date: Wed Jan 22 14:11:12 2014 +
* include/bits/stl_deque.h (_Deque_impl): Move comment.
diff --git a/libstdc++-v3/include/bits/stl_deque.h
b/libstdc++-v3/include/bits/
Hi,
it is quite late in P3 now, so how about the attached patch?
This would return to the status quo before your patch, where $GMPINC must be !=
sysroot.
Bernd.
> Date: Tue, 7 Jan 2014 16:45:15 +0100
>
> Hi Alan,
>
>
> This issue is not yet resolved, in the moment this cross-compiler issue l
Gerald, are you ok with this version? Jason's approval is conditional to
your opinion ;-)
On Tue, 31 Dec 2013, Marc Glisse wrote:
On Mon, 2 Dec 2013, Gerald Pfeifer wrote:
On Mon, 2 Dec 2013, Marc Glisse wrote:
Index: doc/extend.texi
=
This patch fixes a rare visibility issue that arises when an expanded name in
a proper body has a prefix which is a package that appears in a with_clause of
the proper body, when there is a homonym of the package declared in the parent
of the subunit. Previous to this patch a (spurious) error was r
For practitioners of other languages it is useful to indicate that an access
value is not a legal operand of predefined concatenation.
Compiling foo.adb must yield:
foo.adb:5:33: invalid operand types for operator "&"
foo.adb:5:33: left operand is access type
foo.adb:6:35: invalid operan
This change removes specialized code for insertion of dynamic elaboration
checks (-gnatE) that caused a temporary of a controlled type to be finalized
too early when passed as actual parameter to a subprogram through a
named parameter association.
The following compilation must be accepted and pro
This change avoids issuing the "no entities .." message for a with'ed
package if serious errors have been found. This eliminates some annoying
false positives, as shown by the following example, compiled with -gnatwa
1. with System; use System;
2. package WarnNoEnt is
3.X : Inte
> Ah, OK. In that case, how about this? Tested on mips64-linux-gnu.
Fine with me, thanks!
--
Eric Botcazou
Hi Michael,
On 26 November 2013 17:48, David Holsgrove wrote:
> Hi Michael,
>
> Please find attached same patch based against latest from gcc master.
>
> Can this be applied and backported to gcc-4_8-branch when reviewed.
>
> thanks,
> David
>
> On 15 July 2013 14:49, David Holsgrove wrote:
>> M
Hi Bernd,
We have some testcases, but they require XeonPhi hardware and a
working libgomp plugin. Our current version of the plugin depends on
some libraries, that are not open-sourced yet, so currently we can’t
share it.
However, you could examine what these patches do, making the following step
Hi Michael,
On 22 January 2014 13:43, David Holsgrove wrote:
>> -Original Message-
>> From: Michael Eager [mailto:ea...@eagerm.com]
>> Sent: Friday, 17 January 2014 4:36 am
>> To: David Holsgrove; gcc-patches@gcc.gnu.org
>> Cc: Edgar Iglesias; John Williams; Vidhumouli Hunsigida; Nagaraju
On 01/21/2014 04:16 PM, Paolo Carlini wrote:
+ if (TREE_CODE (child) == TYPENAME_TYPE)
+return false;
+
Maybe we want instead to do
if (WILDCARD_TYPE_P (child))
return false;
(which also passes testing, of course).
Thanks,
Paolo.
On 16/01/14 12:12, Alex Velenko wrote:
[AArch64] VDUP testcases
Hi,
This patch implements test cases for following NEON intrinsics:
vdup_lane_f32
vdup_lane_s[8,16]
vdup_lane_s[32,64]
vdup_n_[p,s,u][8,16]
vdup_n_[s,u][32,64]
vdupb_lane_[s,u]8
vduph_lane_[s,u]16
vdupd_lane_[f,s,u]64
vdups_lane_[
On Wed, Jan 22, 2014 at 12:15:00AM +0100, Jakub Jelinek wrote:
> And for
> (bar (), (bar (), (bar (), (bar (), (bar (), (bar (), (bar (), 7)));
> ?
Argh, for this one we've got COMPOUND_EXPRs even in TREE_OPERAND (r, 1).
Fixed & sorry.
> On the other side, there is warn_if_unused_value, wh
Eric Botcazou writes:
>> It looks like the committed version removed the space after "insn".
>> Was that intentional? It now triggers on MIPS because of the frame-related
>> (insn/f) prologue instruction that stores the link register. The posted
>> version works for me FWIW.
>
> I found out that
Bernd Edlinger writes:
> Hi,
Hello,
> since there was no progress in the last 2 months on that matter,
Sorry, this is my bad. I got sidetracked by something else and forgot
that I had the patch working et al, and all its bits that need approval
got approved. It still can go in right now. It
69 matches
Mail list logo
