Mike Stump wrote:
> On Apr 10, 2011, at 2:07 PM, Jim Meyering wrote:
>> $ git ls-files .|xargs perl -0777 -n -e 'while (/\b(it)\s+\1\b/gms)'
>> -e '{$n=($` =~ tr/\n/\n/ + 1); ($v=$&)=~s/\n/\\n/g; print
>> "$ARGV:$n:$v\n"}'|grep -v ChangeLog
>> gcc/config/cris/cris.opt:152:it it
>> gcc/gensupport.c:
Hi!
Roger changed fold_convert* back in 2007 to not actually convert to void
GIMPLE_MODIFY_STMT:
http://gcc.gnu.org/ml/gcc-patches/2007-01/msg00279.html
as GIMPLE_MODIFY_STMT didn't have TREE_TYPE and thus converting it to
void has been difficult.
That == GIMPLE_MODIFY_STMT check has been changed
On Apr 10, 2011, at 2:07 PM, Jim Meyering wrote:
> $ git ls-files .|xargs perl -0777 -n -e 'while (/\b(it)\s+\1\b/gms)' -e
> '{$n=($` =~ tr/\n/\n/ + 1); ($v=$&)=~s/\n/\\n/g; print "$ARGV:$n:$v\n"}'|grep
> -v ChangeLog
> gcc/config/cris/cris.opt:152:it it
> gcc/gensupport.c:1066:it\n it
These
Applied an obvious fix to a typo.
* gensupport.c (read_md_rtx): Fix typo in comment.
2011-04-22 Mike Stump
* gensupport.c (read_md_rtx): Fix typo in comment.
Index: gensupport.c
===
--- gensupport.c(revi
On 04/22/2011 02:48 PM, Tobias Burnus wrote:
Another two simple coarray fixes:
(a) when reading a module, the cotype was not set. The consequence was that one
could not use associate alloctable coarray module variables
(b) The coindexed check was overeager and also rejected "alloctate( x%b(3)[*
* config/cris/cris.opt (moverride-best-lib-options): Fix typo in
comment.
2011-04-22 Mike Stump
* config/cris/cris.opt (moverride-best-lib-options): Fix typo in
comment.
Index: config/cris/cris.opt
===
On Sat, 16 Apr 2011, Diego Novillo wrote:
> On Thu, Apr 14, 2011 at 22:01, Lawrence Crowl wrote:
> > +unsigned char too_many_directives_for_bitfield[
> > + N_DIRECTIVES <= (1 << CPP_HASHNODE_INDEX_BITS)
> > + ? 1 : -1];
>
> Heh, I'm not sure what to think of this trick. I think I lik
Rainer Orth writes:
> As described in the PR, fmt FAILs on targets without split-stack support
> (anything but Linux, it seems) since the 32-bit TestScanInts tests
> overflows the default thread stack of 1 MB. To avoid this, I've reduced
> the recursion depth from 1000 to 800 which lets the test
This patch to the Go frontend changes uses of gcc_unreachable to be
go_unreachable instead. The patch is from Evan Shaw. Bootstrapped and
ran Go testsuite on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
diff -r 969c61627ab5 go/README
--- a/go/README Fri Apr 22 11:33:30 2011 -0700
+++ b
On Apr 22, 2011, at 2:05 AM, Richard Guenther wrote:
> I think we shouldn't worry about this kind of testsuite fails.
There are only two testcases in this class. I'd rather have zero. How do you
propose to fix them? For some reason, please just ignore the failures in the
test suite doesn't se
Hi,
the patch also solves inliner compile time problems for mozilla:
garbage collection: 15.88 ( 4%) usr 0.00 ( 0%) sys 15.89 ( 4%) wall
0 kB ( 0%) ggc
callgraph optimization: 3.10 ( 1%) usr 0.00 ( 0%) sys 3.09 ( 1%) wall
15604 kB ( 1%) ggc
varpool construction : 0.69
On Apr 22, 2011, at 8:12 AM, Nicola Pero wrote:
> This patch fixes a building annoyance that I had when building on a new
> machine (an x86_64 gnu/linux box).
>
> The building failed. It was down to two problems:
>
> * due to how I got a copy of the GCC source code on the machine, the timestamp
On 4/21/11, Jason Merrill wrote:
> On 04/21/2011 07:17 PM, Lawrence Crowl wrote:
@@ -1911,7 +1911,7 @@ ggc_collect (void)
- timevar_push (TV_GC);
+ timevar_start (TV_GC);
>>>
>>> Why this change? GC time shouldn't be counted against whatever we
>>> happen to be parsing when it ha
Corporate webmasters, I love them. Installed.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.211
diff -u -r1.211 readings.html
--- readings.html 7 Feb 2011 01:18:01 -000
> We have a --enable-maintainer-mode configure option.
Thanks - I had missed that option. It's an excellent suggestion - here is
a new patch that uses it. :-)
Ok to commit ?
Thanks
PS: Regarding how I detect --enable-maintainer-mode in this new patch,
cp/Make-lang.in
is used at it is, without
On Apr 22, 2011, at 3:28 AM, Eric Botcazou wrote:
>> This patch fixes up hot/cold partitioning on ports that don't have long
>> conditional branches. I'll note that the entire file has lots of other
>> jump optimizations that are suspect.
>
> Do you have a testcase for one of the ports in the tre
Another two simple coarray fixes:
(a) when reading a module, the cotype was not set. The consequence was
that one could not use associate alloctable coarray module variables
(b) The coindexed check was overeager and also rejected "alloctate(
x%b(3)[*])" claiming that the expression is coindex
> Attached one-liner fixes PR target/48723, ICE in
> ix86_expand_prologue() with -fstack-check + function returning struct,
> on corei7-avx. The problem was, that we forgot to update accounting
> info when ix86_adjust_stack_and_probe adjusted stack pointer (in this
> particular case, m->fs.sp_offse
On Fri, Apr 22, 2011 at 1:26 PM, Jakub Jelinek wrote:
> On Fri, Apr 22, 2011 at 01:19:17PM -0700, Easwaran Raman wrote:
>
> The ChangeLog entry has various issues:
>
>> 2011-04-22 Easwaran Raman
>>
>> PR rtl-optimization/44194
>
> This should have tab before PR as well.
>
>> * dse.c (head
This patch ports the implementation of -Wself-assign warning from a
GCC-4.4.3 based tree to google/main branch. The warning checks for
self-assignment and self-initialization. It is intended for detecting
accidental self-assignment due to typos, and therefore does not warn
on a statement that is se
On Fri, Apr 22, 2011 at 01:19:17PM -0700, Easwaran Raman wrote:
The ChangeLog entry has various issues:
> 2011-04-22 Easwaran Raman
>
> PR rtl-optimization/44194
This should have tab before PR as well.
> * dse.c (header files): Include tree-flow.h.
This should be just
* dse.c
Hi,
This patch improves RTL DSE by not assuming that calls read all
memory locations. With this patch, calls are assumed to read any
non-frame memory and any stack variables that can potentially escape.
This patch partly addresses PR rtl-optimization/44194. Bootstraps and
no test regressions. OK f
2011-04-22 Le-Chun Wu
gcc/c-family/ChangeLog:
* c-common.c (check_for_self_assign): New function.
* c-common.h: New function declaration.
* c.opt: New option.
gcc/ChangeLog:
* c-parser.c (c_parser_declaration_or_fndef): Check for self-assign.
(c_parser_e
Hello world,
the attached patch makes block names unique, so that
-fdump-fortran-original dumps are easier to read.
Regression-tested. OK for trunk?
Thomas
2011-04-22 Thomas Koenig
* decl.c (gfc_match_end): Check that the block name starts
with "block@".
*
Attached patch applied.
2011-04-21 François Dumont
* testsuite/lib/libstdc++.exp (check_v3_target_time): Discard
unused compilation result thanks to /dev/null.
* testsuite/lib/libstdc++.exp (check_v3_target_debug_mode
check_v3_target_profile_mode check_v3_target
> Please review the new patch which only implements cfg checksum.
>
> The auto version generation was introduced in 2002 before FDO support
> was added (so the old way never existed), so it might be better to
> make the change independent of this one.
FDO support was there well before 2002, just
On Fri, Apr 22, 2011 at 09:27:50PM +0200, Richard Guenther wrote:
> There is a scary comment before build_int_cst_type why build_int_cst
> can't be sane. Fortunately it is not true. If it were there would
> be other code to be fixed.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, appli
Andreas Tobler writes:
> How does linux/m68k handle this?
It does not support the 68010.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
> Yes, that's very likely. If we'd get around to re-do the LTO option saving
> code
> we might want to forbid -g0 compile and -g link (dropping -g at link
> time as soon
> as we see a single module compiled with -g0). Then we can free some more
> stuff, at least with -g0 - though I'm not sure -g
On 22.04.11 21:05, Andreas Schwab wrote:
Andreas Tobler writes:
Index: config/m68k/netbsd-elf.h
===
--- config/m68k/netbsd-elf.h(revision 172861)
+++ config/m68k/netbsd-elf.h(working copy)
@@ -97,7 +97,11 @@
#undef PTRDI
There is a scary comment before build_int_cst_type why build_int_cst
can't be sane. Fortunately it is not true. If it were there would
be other code to be fixed.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2011-04-22 Richard Guenther
* tree.c (b
On Fri, Apr 22, 2011 at 02:58:31PM -0400, Michael Meissner wrote:
> On Thu, Apr 21, 2011 at 11:04:47AM -0400, Nathan Froyd wrote:
> > - centralizes some infrastructure for defining builtin function types
> > for frontends by providing a common function that
> > DEF_FUNCTION_TYPE_FOO macros can
Andreas Tobler writes:
> Index: config/m68k/netbsd-elf.h
> ===
> --- config/m68k/netbsd-elf.h (revision 172861)
> +++ config/m68k/netbsd-elf.h (working copy)
> @@ -97,7 +97,11 @@
> #undef PTRDIFF_TYPE
> #define PTRDIFF_TYPE "int"
Please review the new patch which only implements cfg checksum.
The auto version generation was introduced in 2002 before FDO support
was added (so the old way never existed), so it might be better to
make the change independent of this one.
Thanks,
David
On Thu, Apr 21, 2011 at 2:15 PM, Xinlia
On Thu, Apr 21, 2011 at 11:04:47AM -0400, Nathan Froyd wrote:
> This patch does two things:
>
> - centralizes some infrastructure for defining builtin function types
> for frontends by providing a common function that
> DEF_FUNCTION_TYPE_FOO macros can call; and
>
> - in order to do that well
On Fri, Apr 22, 2011 at 04:50:26PM +0200, Richard Guenther wrote:
> build_int_cst looks seriously broken, I think we want to make it
> an alias of build_int_cst_type, or rather call that from
> build_int_cst.
The comment above build_int_cst_type talks about it:
"We cannot however make this a defa
Rainer Orth writes:
> 2011-02-13 Rainer Orth
>
> * Makefile.am (CHECK): Remove -Wl,-R from $GC.
> Add LD_LIBRARY_PATH.
> (check): Depend on check-multi, check-tail.
> (check-recursive): Depend on check-head.
> (check-am): Move header, footer generation ...
>
Hello!
Attached one-liner fixes PR target/48723, ICE in
ix86_expand_prologue() with -fstack-check + function returning struct,
on corei7-avx. The problem was, that we forgot to update accounting
info when ix86_adjust_stack_and_probe adjusted stack pointer (in this
particular case, m->fs.sp_offset
This libgo patch brings over a patch to the master Go library to inherit
environment variables in http/cgi. This should fix PR go/48503.
Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu.
Committed to mainline.
Ian
diff -r 9457f9a2e900 libgo/go/http/cgi/host.go
--- a/libgo/go/http/cg
Hi all,
the attached patch fixes the build for m68k-netbsdelf1.6.1. Tested with
a cross build for c,c++ and fortran.
The breakage is alive since r121736.
The patch does the same as m68k linux does.
Ok for trunk?
Thanks,
Andreas
2011-04-22 Andreas Tobler
PR target/48690
*
I'm wondering whether the following patch to add V4SF and V2DF reductions fell
through the cracks?
http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01525.html
--
Michael Meissner, IBM
5 Technology Place Drive, M/S 2757, Westford, MA 01886-3141, USA
meiss...@linux.vnet.ibm.com fax +1 (978) 399-689
This fixes an oversight in the support for parallel types: they are silently
dropped when a type goes through make_packable_type.
Fixed thusly, tested on i586-suse-linux, applied on the mainline.
2011-04-22 Eric Botcazou
* gcc-interface/decl.c (make_packable_type): Copy DECL_PARALLE
This patch prevents the compiler from issuing -Winline warnings for functions
that are compiler-generated. There are a lot of them in Ada and the warnings
are too cryptic to be useful for the average user in this case.
Tested on i586-suse-linux, applied on the mainline.
2011-04-22 Eric Botca
Looks like we won't get consensus (as Jeff mentioned) on the naming
etc. Shall I just commit this one?
Thanks,
David
On Fri, Apr 22, 2011 at 9:23 AM, Gabriel Dos Reis
wrote:
> On Fri, Apr 22, 2011 at 3:52 AM, Richard Guenther
> wrote:
>
>
>>> Maybe-uninitialized matches case 3) -- different fr
On Fri, 22 Apr 2011, Nicola Pero wrote:
> In general, I personally feel that the building system should not depend
> on the relative timestamps of source files unless it's doing something
> in "maintainer mode" where it's being explicitly asked to rebuild one
> source file from the other.
We h
On Thu, 21 Apr 2011, Xinliang David Li wrote:
> Please review the new patch.
The new patch is OK with a suitable ChangeLog entry.
--
Joseph S. Myers
jos...@codesourcery.com
On Apr 22, 2011, at 8:55 AM, Jason Merrill wrote:
> On 04/22/2011 02:13 AM, Mike Stump wrote:
>> http://gcc.gnu.org/ml/gcc/2005-04/msg00161.html
>>
>> has the details of why the code was put in.
>
> Right. At the time, we were sorting the goto queue based on pointer values,
> which caused the
On Fri, Apr 22, 2011 at 3:52 AM, Richard Guenther
wrote:
>> Maybe-uninitialized matches case 3) -- different from case 2 which is
>> actually 'maybe-used-uninitialized'.
>
> Other diagnostics use a level to indicate their noise level. So, why not
> do something like -Wuninitialized=N, with N fr
Sounds like a good idea, but does -Werror=xxx work for this ? I tried
cases with -Wstrict-aliasing, -Werror handling seems broken.
Thanks,
David
On Fri, Apr 22, 2011 at 1:52 AM, Richard Guenther
wrote:
> On Thu, Apr 21, 2011 at 7:43 PM, Xinliang David Li wrote:
>> On Thu, Apr 21, 2011 at 10:2
On Thu, Apr 21, 2011 at 05:36:42PM +0200, Richard Guenther wrote:
> On Thu, Apr 21, 2011 at 5:04 PM, Nathan Froyd
> wrote:
> > This patch does two things:
> >
> > - centralizes some infrastructure for defining builtin function types
> > for frontends by providing a common function that
> > DEF_
On 04/22/2011 02:13 AM, Mike Stump wrote:
http://gcc.gnu.org/ml/gcc/2005-04/msg00161.html
has the details of why the code was put in.
Right. At the time, we were sorting the goto queue based on pointer
values, which caused the problem. We no longer do that, so we shouldn't
need this wor
Hi Richard, this part's for you.
The ARM backend changes needed are very little after the prior patches,
basically just a case in arm_canonicalize_comparison() to detect
(zero_extend:SI (subreg:QI (reg:SI ...) 0)), and swap it into (and:SI
(reg:SI) #255).
Had we not tried the combine modification
This patch is the main bulk of this submission. It modifies the compare
combining part of try_combine(), adding a call of
CANONICALIZE_COMPARISON into the entire logic.
Also, instead of testing for XEXP(SET_SRC(PATTERN(i3)),1) == const0_rtx
at the top, it now allows CONST_INT_P(XEXP(SET_SRC(PATTER
This patch abstracts out a small part of simplify_comparison(), into a
new function simplify_compare_const(). The parts are basically where the
comparison RTX code and a constant operand (op1) can be simplified
towards "compare with zero". Note this part leaves op0 untouched, thus
not passed into s
Hi,
this patch set solves a case seen on ARM when -march= is set to armv6 or
above. ARMv6 has a uxtb (unsigned extend byte) instruction,
corresponding to a ZERO_EXTEND rtx, which is equivalent to 'and reg,
reg, #255'.
The problem with 'uxtb' is that, unlike 'and', it does not have a 's'
condition
This patch fixes a building annoyance that I had when building on a new
machine (an x86_64 gnu/linux box).
The building failed. It was down to two problems:
* due to how I got a copy of the GCC source code on the machine, the timestamp
of each source file was the timestamp of when it was copied
On Fri, Apr 22, 2011 at 3:41 PM, Jakub Jelinek wrote:
> Hi!
>
> On the following testcase associate_plusminus optimizes
> A + ~A into INTEGER_CST { -1, -1 } with type unsigned short, which
> confuses enough following passes on (int) cast of that into
> assuming it is -1 instead of 65535.
Ick.
>
> > Yes, that's very likely. If we'd get around to re-do the LTO option saving
> > code
> > we might want to forbid -g0 compile and -g link (dropping -g at link
> > time as soon
> > as we see a single module compiled with -g0). Then we can free some more
> > stuff, at least with -g0 - though I'm
> Yes, that's very likely. If we'd get around to re-do the LTO option saving
> code
> we might want to forbid -g0 compile and -g link (dropping -g at link
> time as soon
> as we see a single module compiled with -g0). Then we can free some more
> stuff, at least with -g0 - though I'm not sure -g
On Fri, Apr 22, 2011 at 1:58 PM, Jan Hubicka wrote:
> Hi,
> I run the patch on Mozilla. W/o the patch it is:
> Execution times (seconds)
> garbage collection : 20.19 ( 3%) usr 0.02 ( 0%) sys 20.22 ( 3%) wall
> 0 kB ( 0%) ggc
> callgraph optimization: 3.53 ( 1%) usr 0.01 ( 0%)
Hi!
OpenMP 3.0 says that static variables that are declared in a scope inside
the construct are predetermined shared. OpenMP 2.5 was silent about it.
I've asked on OpenMP forum about the local externs, if those should be
predetermined shared too, I'll drop the && !DECL_EXTERNAL (t).
Bootstrapped
Hi!
On the following testcase associate_plusminus optimizes
A + ~A into INTEGER_CST { -1, -1 } with type unsigned short, which
confuses enough following passes on (int) cast of that into
assuming it is -1 instead of 65535.
Fixed by using build_int_cst_type, which is what e.g. fold-const.c
uses whe
On Fri, Apr 22, 2011 at 11:12:01AM +0200, Richard Guenther wrote:
> On Fri, Apr 22, 2011 at 8:13 AM, Mike Stump wrote:
> > Unsurprising... It will never fail during testsuite run, and won't
> > always fail during a bootstrap.
> >
> >> I can't think what the comment would be talking about with poi
Hi,
last year I removed the last use of cp_fold_obj_type_ref (which was a
language hook) but forgot to remove the function itself. So I'm about
to do it now.
I'm currently bootstrapping and testing the following patch. I
consider it obvious enough to commit it myself on Tuesday if it
passes.
T
Hi,
the following one-liner fixes LTO build of SPEC 2006 483.xalancbmk.
The problem is that code that adds new call graph edges for
newly-direct calls is triggered for "zombie clones," clones which
exist only to facilitate materialization of their descendant clones
and will be thrown away afterwar
Hi,
I run the patch on Mozilla. W/o the patch it is:
Execution times (seconds)
garbage collection: 20.19 ( 3%) usr 0.02 ( 0%) sys 20.22 ( 3%) wall
0 kB ( 0%) ggc
callgraph optimization: 3.53 ( 1%) usr 0.01 ( 0%) sys 3.53 ( 1%) wall
15248 kB ( 1%) ggc
varpool construction
> This patch fixes up hot/cold partitioning on ports that don't have long
> conditional branches. I'll note that the entire file has lots of other
> jump optimizations that are suspect.
Do you have a testcase for one of the ports in the tree? Note that parameters
of function must be documented
On Fri, Apr 22, 2011 at 8:13 AM, Mike Stump wrote:
> On Apr 21, 2011, at 9:59 PM, Jason Merrill wrote:
>> On 04/21/2011 10:55 PM, Nathan Froyd wrote:
>>> On Thu, Apr 21, 2011 at 10:49:05PM -0400, Jason Merrill wrote:
Hunh. How does that work? They fill in CASE_LABEL later? Can that be
On Fri, Apr 22, 2011 at 3:40 AM, Mike Stump wrote:
> Ping?
The patch makes the testcase pointless. It also makes the AST differ
more from the source form, so I don't think
it's a particularly good idea.
I think we shouldn't worry about this kind of testsuite fails.
Richard.
> On Apr 12, 2011,
On Thu, Apr 21, 2011 at 5:47 PM, Jeff Law wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> For some dumb reason I thought handling threading through a SWITCH_EXPR
> was hard in VRP; that's definitely not the case, it's no more difficult
> than handling a COND_EXPR.
>
> This patch all
On Thu, Apr 21, 2011 at 7:43 PM, Xinliang David Li wrote:
> On Thu, Apr 21, 2011 at 10:21 AM, Jeff Law wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 04/07/11 18:24, Xinliang David Li wrote:
>>> Hi,
>>>
>>> the following patch implements the option to fine control the emitted
71 matches
Mail list logo
