On Thu, Jun 12, 2014 at 6:33 AM, Jan Hubicka hubi...@ucw.cz wrote:
Hi,
this lenghtly patch makes the legwork to put section names out of tree
representation.
Originally they were STRING_CST. I ended up implementing on-side reference
counted
string voclabulary that is done in bit baroque
On Wed, Jun 11, 2014 at 6:08 PM, Ilya Enkovich enkovich@gmail.com wrote:
Hi,
This patch fixes problem with size emitted for static structures with
flexible array. I found a couple of trackers in guzilla for this problem but
all of them are marked as fixed and problem still exists.
On Wed, Jun 11, 2014 at 11:35 PM, DJ Delorie d...@redhat.com wrote:
If the combined bitfields are exactly the size of the mode, the logic
for detecting range overflow is flawed - it calculates an ending
position that's the position of the first bit in the next field.
In the case of short for
This patch tries to get safe lower and upper bounds where accesses
are always guaranteed to work. The goal is not to penalize
reasonable written code: When boot-strapping the whole GCC
only a few places were found, where this new check triggers.
Boot-strapped and regression-tested on
On Thu, Jun 12, 2014 at 10:03 AM, Eric Botcazou ebotca...@adacore.com wrote:
This patch tries to get safe lower and upper bounds where accesses
are always guaranteed to work. The goal is not to penalize
reasonable written code: When boot-strapping the whole GCC
only a few places were found,
On Thu, Jun 12, 2014 at 6:33 AM, Jan Hubicka hubi...@ucw.cz wrote:
Hi,
this lenghtly patch makes the legwork to put section names out of tree
representation.
Originally they were STRING_CST. I ended up implementing on-side reference
counted
string voclabulary that is done in bit
On Thu, Jun 12, 2014 at 6:04 AM, Evgeny Stupachenko evstu...@gmail.com wrote:
Testing finished. No new regressions.
Is the following patch ok?
+ if (targetm.sched.reassociation_width (VEC_PERM_EXPR, mode) 1 ||
+ !vect_shift_permute_load_chain (dr_chain, size, stmt, gsi,
result_chain))
If we want to give frontends a way to pass information that address of a
given global object is not taken (apparently useful for Ada and its alias
attribute), then I do not think we are looking for middle-end only
solution.
I don't feel very confortable with doing that in Ada, since everybody
On Thu, 12 Jun 2014, Eric Botcazou wrote:
If we want to give frontends a way to pass information that address of a
given global object is not taken (apparently useful for Ada and its alias
attribute), then I do not think we are looking for middle-end only
solution.
I don't feel very
Btw, I wonder if we can simply mark the MEMs generated from spill code
with MEM_NOTRAP_P so we can remove the special casing of
frame-pointer-based addresses from add while properly initializing
MEM_NOTRAP_p from rtx_addr_can_trap_p?
Spill code generated by the compiler itself? That's quite
On Thu, 12 Jun 2014 10:36:25, Eric Botcazou wrote:
Btw, I wonder if we can simply mark the MEMs generated from spill code
with MEM_NOTRAP_P so we can remove the special casing of
frame-pointer-based addresses from add while properly initializing
MEM_NOTRAP_p from rtx_addr_can_trap_p?
Spill
Richard,
as briefly discussed before, I would like to teach LTO type merging to not merge
types that was declared in anonymous namespaces and use C++ ODR type names
(stored in DECL_ASSEMBLER_NAME of the TYPE_DECL) to break down canonical types
by their names.
First thing I need to arrange IMO is
On Thu, 12 Jun 2014, Eric Botcazou wrote:
If we want to give frontends a way to pass information that address of a
given global object is not taken (apparently useful for Ada and its alias
attribute), then I do not think we are looking for middle-end only
solution.
I don't feel
Btw I am not sure at all, why argp-references can never be dangerous?
For instance in a struct with an array inside, passed as function argument?
IMO there cannot be any definitive solution to this issue until after we move
all the affected optimizations from RTL to GIMPLE. In the meantime,
Btw, may_be_aliased already does that.
Indeed, and we could make use of that in Ada, at least in some cases.
Of course one issue is that it's impossible to write a verifier that
checks whether DECL_NONALIASED and TREE_ADDRESSABLE are out-of-sync
(because by design they can be). So it's a
On Thu, 12 Jun 2014, Jan Hubicka wrote:
On Thu, 12 Jun 2014, Eric Botcazou wrote:
If we want to give frontends a way to pass information that address of a
given global object is not taken (apparently useful for Ada and its
alias
attribute), then I do not think we are looking
There was apparently a last-minute name change for DECL_NONALIASED.
Tested on x86_64-suse-linux, applied on mainline and 4.9 branch as obvious.
2014-06-12 Eric Botcazou ebotca...@adacore.com
* tree-core.h (DECL_NONALIASED): Use proper spelling in comment.
--
Eric BotcazouIndex:
On Thu, 12 Jun 2014 10:50:29, Eric Botcazou wrote:
Btw I am not sure at all, why argp-references can never be dangerous?
For instance in a struct with an array inside, passed as function argument?
IMO there cannot be any definitive solution to this issue until after we move
all the affected
This implements the requested inlining of memmove for possibly
overlapping arguments by doing first all loads and then all stores.
The easiest place is to do this in memory op folding where we already
perform inlining of some memcpy cases (but fail to do the equivalent
memcpy optimization -
Hi DJ,
Have you checked the other alignment macros to see if they need to be
fixed too?
Thank you for review this patch.
Yes, I have checked other alignment macros and it seems fine.
This should be :
I have corrected this review comment.
Is this patch now ok to commit?
Best Regards,
On Thu, Jun 12, 2014 at 10:47 AM, Jan Hubicka hubi...@ucw.cz wrote:
Richard,
as briefly discussed before, I would like to teach LTO type merging to not
merge
types that was declared in anonymous namespaces and use C++ ODR type names
(stored in DECL_ASSEMBLER_NAME of the TYPE_DECL) to break
On Thu, Jun 12, 2014 at 12:29 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Thu, Jun 12, 2014 at 10:47 AM, Jan Hubicka hubi...@ucw.cz wrote:
Richard,
as briefly discussed before, I would like to teach LTO type merging to not
merge
types that was declared in anonymous namespaces and
Hi Honza,
Unfortunately, AIX isn't the only target massively affected by your
recent patches. This all started with r210597
2014-05-17 Jan Hubicka hubi...@ucw.cz
* tree-pass.h (make_pass_ipa_comdats): New pass.
* timevar.def (TV_IPA_COMDATS): New timevar.
*
On Thu, Jun 12, 2014 at 12:34 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Thu, Jun 12, 2014 at 12:29 PM, Richard Biener
richard.guent...@gmail.com wrote:
On Thu, Jun 12, 2014 at 10:47 AM, Jan Hubicka hubi...@ucw.cz wrote:
Richard,
as briefly discussed before, I would like to teach
On Thu, Jun 12, 2014 at 10:36 AM, Eric Botcazou ebotca...@adacore.com wrote:
Btw, I wonder if we can simply mark the MEMs generated from spill code
with MEM_NOTRAP_P so we can remove the special casing of
frame-pointer-based addresses from add while properly initializing
MEM_NOTRAP_p from
From: tschwinge tschwinge@138bc75d-0d04-0410-961f-82ee72b054a4
gcc/c/
* c-parser.c (c_parser_oacc_all_clauses): Handle
PRAGMA_OMP_CLAUSE_IF.
(OACC_DATA_CLAUSE_MASK, OACC_KERNELS_CLAUSE_MASK)
(OACC_PARALLEL_CLAUSE_MASK, OACC_UPDATE_CLAUSE_MASK): Add it.
From: tschwinge tschwinge@138bc75d-0d04-0410-961f-82ee72b054a4
--enable-target-gcc-configure-flags, EXTRA_TARGET_GCC_FLAGS vs.
--enable-accelerator-gcc-configure-flags, EXTRA_ACCELERATOR_GCC_FLAGS.
* configure.ac (--enable-target-gcc-configure-flags)
It seems the https transition broke refering to permanently moved
URL gcc-3.0/gcc-3.0.html (I get a certificate error or some such),
breaking gennews and thus gcc_release. Fixed like below which
makes gennews succeed.
Committed to the 4.7 branch.
Richard.
2014-06-12 Richard Biener
The GCC 4.7 branch is now closed, please refrain from committing anything
there now.
Richard.
Hi all,
we have merged the gcc-4_9-branch into linaro/gcc-4_9-branch up to
revision 211054 as r211495. We have also backported this set of revisions:
r209419 as r211497 : PR rtl-optimization/60663
r209457 as r211496 : TRY_EMPTY_VM_SPACE Change aarch64 ilp32
r209559 as r211498 : [AArch64]
Rainer Orth r...@cebitec.uni-bielefeld.de writes:
Hi Honza,
Unfortunately, AIX isn't the only target massively affected by your
recent patches. This all started with r210597
2014-05-17 Jan Hubicka hubi...@ucw.cz
* tree-pass.h (make_pass_ipa_comdats): New pass.
*
Adds additional checks and tests for ill-formed programs.
2014-06-12 Andrew Sutton andrew.n.sut...@gmail.com
* gcc/cp/parser.c (cp_check_type_concept): New.
(cp_check_concept_name): Remove redundant condition from check.
Diagnose misuse of non-type concepts in
This patch add predicate for storewb_pair/loadwb_pair, because aarch64
register pair push and pop instructions only accept constant offset
within certain range.
OK for trunk?
Thanks.
gcc/ChangeLog:
2014-06-12 Renlin Li renlin...@arm.com
* config/aarch64/aarch64.c
On 12 June 2014 04:31, Mike Stump mikest...@comcast.net wrote:
On Jun 10, 2014, at 3:03 PM, Ramana Radhakrishnan ramana@googlemail.com
wrote:
I am a bit ambivalent between getting folks to add scan-assembler
tests here and worrying between this and getting the behaviour
correct.
On 06/11/2014 02:00 PM, Christian Bruel wrote:
On 06/11/2014 06:17 AM, Joern Rennecke wrote:
Joern, is this new target macro interface OK with you ?
Yes, this interface should allow me to do switches between rounding
and truncating
floating-point modes with an add/subtract immediate.
On 12 June 2014 01:23, Peter Bergner berg...@vnet.ibm.com wrote:
On Wed, 2014-06-11 at 23:07 +, Joseph S. Myers wrote:
On Wed, 11 Jun 2014, Peter Bergner wrote:
I'd like to ping the following patch that fixes PR57653. This did
bootstrap and regtest with no regressions on
On 05/25/2014 11:35 AM, Richard Sandiford wrote:
Bernd Schmidt bernds_...@t-online.de writes:
On 02/13/2014 10:18 AM, Richard Sandiford wrote:
contrib/
* dg-extract-results.py: New file.
* dg-extract-results.sh: Use it if the environment seems suitable.
I'm now seeing the
That is, have a tree_may_be_mergeable_p (), call it during the DFS
walk storing it alongside the visited edges and thus obtain a result
for each SCC, stream that as a flag (a special hash value is ugly,
but well ... I guess it works). The important part is to make an SCC
Hi,
in this old bug Ian complained that the diagnostic we provide for:
typedef void v;
typedef v (*pf)(v);
is rather unfriendly, especially for people coming from C:
33101.C:2:17: error: ‘anonymous’ has incomplete type
33101.C:2:18: error: invalid use of ‘v’
thus Gaby (and Ian) suggested
Hello,
I updated i386.md part of the patch. Initial patch included handling
of blockage, which is obviously superflous. Additionally I merged
32-bit and 64-bit peephole2 versions by using mode-specifier W.
ChangeLog
2014-06-12 Kai Tietz kti...@redhat.com
* config/i386/i386.md
On Thu, Jun 12, 2014 at 10:47 AM, Jan Hubicka hubi...@ucw.cz wrote:
Richard,
as briefly discussed before, I would like to teach LTO type merging to not
merge
types that was declared in anonymous namespaces and use C++ ODR type names
(stored in DECL_ASSEMBLER_NAME of the TYPE_DECL) to
On Jun 12, 2014, at 8:53 AM, Bernd Schmidt ber...@codesourcery.com wrote:
I've recently been trying to add ada to my set of tested languages, and I now
encounter the following:
File ../../git/gcc/../contrib/dg-extract-results.py, line 242, in parse_run
line = file.readline()
File
On Jun 12, 2014, at 7:26 AM, Christophe Lyon christophe.l...@linaro.org wrote:
On 12 June 2014 04:31, Mike Stump mikest...@comcast.net wrote:
On Jun 10, 2014, at 3:03 PM, Ramana Radhakrishnan
ramana@googlemail.com wrote:
At this point I'm going to wait to see if any of the testsuite
Hi,
The patch fixes a bug in the AArch64 backend in calculating the
beginning address of the unnamed incoming arguments on the stack, i.e.
the initial value of __va_list-__stack. aarch64_layout_arg incorrectly
calculates the size of named arguments on stack using the number of
registers
It was reported that mysql was failing its testsuite due to a regex
routine being mis-compiled on the ppc and s390 platforms. Upon
investigation it was found that the fix for PR61009 was incomplete.
The fix for 61009 changed thread_through_normal_block to return a
tri-state with negative
Hi!
Seems http://gcc.gnu.org/r197156 effectively reverted
the PR45078 fix for arm*-linux* (where unfortunately tm_file
is always overridden).
Was the removal of vxworks-dummy.h from that line intentional
or just some mistake?
Seems one can't build gcc plugins on arm because of this,
because
These two patches fix multiple ICE that occurred due to DFE being
recently enabled after AutoFDO LIPO linking.
Passes regression and internal testing. Ok for Google/4_8?
Teresa
2014-06-12 Teresa Johnson tejohn...@google.com
Dehao Chen de...@google.com
Google ref
A bit belated, I have now committed the patch as Rev. 211587.
Thanks for confirming that it now works!
Tobias
Bernd Schmidt wrote:
On 06/04/2014 10:36 PM, Tobias Burnus wrote:
Bernd Schmidt wrote:
Even with this applied, I'm still seeing similar failures.
I didn't claim that the patch
On Thu, Jun 12, 2014 at 06:21:32PM +0200, Kai Tietz wrote:
with addition of adding a second peephole2 pass after sched2 pass, I
was able to get some improvement for PR target/39284. I think by this
addition we can close bug as fixed.
Additionally additional peephole2 pass shows better results
On 06/10/14 01:42, Ilya Enkovich wrote:
Hi,
This patch fixes PR61446. The problem appears when we insert value copies
after transformations. We use the widest extension mode met in a chain, but it
may be wider than original destination register size. This patch checks it and
use smaller
On 06/09/2014 04:46 PM, Jason Merrill wrote:
I'm updating -Wabi to allow for warnings about changes between a
previous ABI version and the currently selected one, and rather than
adjust all the warnings for -fabi-version=1 I'd like to tear it out.
Here's a revised patch that I'm checking in.
... in terms of code proper, the below is much better, IMHO. Assuming,
as I understand, we have no reason to call the rather heavy same_type_p
when we already know that VOID_TYPE_P (type) is true...
Thanks,
Paolo.
//
Index: cp/decl.c
I talked about doing this in 4.9
(https://gcc.gnu.org/ml/gcc/2013-03/msg8.html), but decided to put
it off along with the libstdc++ ABI transition. I think it's time now.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit a2aa0efcd1f27e85a4c652f5177c66686f530a96
Author: Jason Merrill
On Thu, Jun 05, 2014 at 10:43:25PM +0100, Richard Sandiford wrote:
This final patch uses a common .md file to define all standard
constraints except 'g'.
I had a look at what targets still use g. Note: there can be
errors in this, it's all based on \g[,] :-)
* frv and mcore use g in
On Jun 12, 2014, at 12:17 PM, Jason Merrill ja...@redhat.com wrote:
I talked about doing this in 4.9
(https://gcc.gnu.org/ml/gcc/2013-03/msg8.html), but decided to put it off
along with the libstdc++ ABI transition. I think it's time now.
Is a doc change needed?
@opindex fabi-version
On Jun 12, 2014, at 3:24 PM, Segher Boessenkool seg...@kernel.crashing.org
wrote:
On Thu, Jun 05, 2014 at 10:43:25PM +0100, Richard Sandiford wrote:
This final patch uses a common .md file to define all standard
constraints except 'g'.
I had a look at what targets still use g. Note:
How does this affect pr60732?
Dominique
On 06/10/14 01:42, Ilya Enkovich wrote:
Hi,
This patch fixes PR61446. The problem appears when we insert value copies
after transformations. We use the widest extension mode met in a chain, but it
may be wider than original destination register size. This patch checks it and
use smaller
On 06/12/14 04:12, Richard Biener wrote:
This implements the requested inlining of memmove for possibly
overlapping arguments by doing first all loads and then all stores.
The easiest place is to do this in memory op folding where we already
perform inlining of some memcpy cases (but fail to do
2014-06-12 20:52 GMT+02:00 Segher Boessenkool seg...@kernel.crashing.org:
On Thu, Jun 12, 2014 at 06:21:32PM +0200, Kai Tietz wrote:
with addition of adding a second peephole2 pass after sched2 pass, I
was able to get some improvement for PR target/39284. I think by this
addition we can close
Add support for partial concept ids. Mostly this just refactors the
basic support for concept names to also allow a template and extra
arguments.
Also added the missing .exp file for the test suite.
2014-06-12 Andrew Sutton andrew.n.sut...@gmail.com
* gcc/cp/constraint.cc
Now that -fabi-version defaults to 0, -Wabi isn't very useful. But for
people interested in compatibility with earlier versions, this patch
allows you to say -Wabi=2 to get any relevant warnings. This patch also
adjusts the compatibility aliases to default to backward compatibility
with
On 06/12/2014 03:36 PM, Mike Stump wrote:
On Jun 12, 2014, at 12:17 PM, Jason Merrill ja...@redhat.com wrote:
I talked about doing this in 4.9
(https://gcc.gnu.org/ml/gcc/2013-03/msg8.html), but decided to put it off
along with the libstdc++ ABI transition. I think it's time now.
Is a
On 06/12/2014 03:44 PM, Dominique Dhumieres wrote:
How does this affect pr60732?
It should fix that failure.
Jason
Will that work on other targets?
Well, this is the only point I am a bit concerned too. In general I
wouldn't expect here any issues to run peephole after scheduling, as
peephole doesn't do anything a new run of ira/lra would require.
My concern is that peepholes are rather fragile, so
Hi!
This patch fixes 3 issues:
1) distribute doesn't support lastprivate clause, so gimplification
shouldn't add it, it causes ICEs
2) for shared clauses on teams construct we need to at least
record something in decl_map, otherwise lookup_decl ICEs
3) c_omp_split_clauses ICEd on a couple
* cris, m68k, pdp11, and vax actually use g.
So it won't be all that much work to completely get rid of g.
Do we want that?
Is it simply a matter of replacing “g” by “mri”? That’s what the doc
suggests. Or is there more to the story than that?
As far as I know g and rmi are
On 06/12/2014 03:14 PM, Paolo Carlini wrote:
... in terms of code proper, the below is much better, IMHO. Assuming,
as I understand, we have no reason to call the rather heavy same_type_p
when we already know that VOID_TYPE_P (type) is true...
same_type_p is not so heavy since it just compares
On 6/12/2014 9:21 AM, Kai Tietz wrote:
with addition of adding a second peephole2 pass after sched2 pass, I
was able to get some improvement for PR target/39284. I think by this
addition we can close bug as fixed.
Additionally additional peephole2 pass shows better results for PR
target/51840
I think the patch looks good. David and Rong, any comments?
Dehao
On Thu, Jun 12, 2014 at 11:23 AM, Teresa Johnson tejohn...@google.com wrote:
These two patches fix multiple ICE that occurred due to DFE being
recently enabled after AutoFDO LIPO linking.
Passes regression and internal
Hi,
while updating vect_can_force_dr_alignment_p for section API I noticed the
predicate is bit confused about when it can update the alignment.
We need to check that decl_binds_to_current_def_p and in case we compile
a partition also that the symbol is not homed in other partition.
Previous code
DR1206 allows explicit specializations of member enumerations
of class templates, so just remove the pedwarn about it.
Tested on Linux-x64. Not bootstrapped.
diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
index d267a5c..97eadeb 100644
--- a/gcc/cp/pt.c
+++ b/gcc/cp/pt.c
@@ -967,11 +967,8 @@
On 13 June 2014 01:37, Ville Voutilainen ville.voutilai...@gmail.com wrote:
DR1206 allows explicit specializations of member enumerations
of class templates, so just remove the pedwarn about it.
Tested on Linux-x64. Not bootstrapped.
Argh, also remove the old comment, new patch attached.
diff
This looks fine to me.
-Rong
On Thu, Jun 12, 2014 at 11:23 AM, Teresa Johnson tejohn...@google.com wrote:
These two patches fix multiple ICE that occurred due to DFE being
recently enabled after AutoFDO LIPO linking.
Passes regression and internal testing. Ok for Google/4_8?
Teresa
2014-06-12 11:55 GMT+04:00 Richard Biener richard.guent...@gmail.com:
On Wed, Jun 11, 2014 at 6:08 PM, Ilya Enkovich enkovich@gmail.com wrote:
Hi,
This patch fixes problem with size emitted for static structures with
flexible array. I found a couple of trackers in guzilla for this
Comdat locals are now used by ipa-comdats, for thunks and for decloned
ctors.
We probably need to figure out bit more precise limitation of Solaris and
either
fix or add way for target to say what kind of comdat locals are not
supported.
Right. I'll start reghunting for the
When you extract the address and use it. For example when you
do auto-parallelization and outline a part of your function it
passes arrays as addresses.
Or if you start to introduce address induction variables like
the vectorizer or IVOPTs does.
I see, nothing really done by current
On Mon, 12 May 2014, Tobias Burnus wrote:
The patch changes the URL shown in the release message to HTTPS. (Cf.
https://gcc.gnu.org/viewcvs/gcc/hooks/svnmailer.conf and gcc-cvs mailing
list.)
Yes, please. Thanks!
Gerald
78 matches
Mail list logo
