Joern Rennecke joern.renne...@embecosm.com writes:
Index: gcc/doc/tm.texi
===
--- gcc/doc/tm.texi (revision 192840)
+++ gcc/doc/tm.texi (working copy)
@@ -11333,3 +11333,11 @@ @deftypefn {Target Hook} {unsigned HOST_
The texinfo manual says that @end should always be put on a line of its
own. Tested with make info dvi pdf html and checked in as obvious.
(None of the converters have a problem with this so the output will be
the same.)
Andreas.
* doc/tm.texi.in (Misc): Add newline before @end.
On Sun, Oct 28, 2012 at 2:37 AM, H.J. Lu hjl.to...@gmail.com wrote:
As suggested by Richard S. [1], after the patch that converts subreg:M
(op:N (...)(...)) to op:M (subreg:M (...) subreg:M (...)), we can
remove several peephole2 patterns that handle subregs of PLUS, MINUS
and MULT operators.
On Sun, Oct 28, 2012 at 9:57 AM, Uros Bizjak ubiz...@gmail.com wrote:
On Sun, Oct 28, 2012 at 2:37 AM, H.J. Lu hjl.to...@gmail.com wrote:
As suggested by Richard S. [1], after the patch that converts subreg:M
(op:N (...)(...)) to op:M (subreg:M (...) subreg:M (...)), we can
remove several
Tested with make info dvi pdf html and checked in as obvious.
Andreas.
* doc/cppopts.texi: Fix use of @item vs. @itemx inside @table.
* doc/extend.texi: Likewise.
* doc/generic.texi: Likewise.
* doc/invoke.texi: Likewise.
* doc/md.texi: Likewise.
*
Hi,
this patch implements simple hints on strongly connected components to inliner.
It increases badness of inlining functions within the same scc component, since
this
non-trivial recursive inlining is not win very often and it may blow up stack
frames a lot.
It also increases the entry points
Andreas Schwab wrote:
Gunther Nikl gn...@users.sourceforge.net writes:
The patch should be installed on trunk and on the 4.7 branch.
Thanks, done. The 4.7 branch required some adjustment, since it's not
compiled as C++.
Right. Maybe a better solution would have been then to only change
On Sun, 28 Oct 2012, Jan Hubicka wrote:
Bootstrapped/regtested x86_64-linux.
Honza
* ipa-inline.c (edge_badness): Reduce precision; use scc hints.
(inline_small_functions): Fix dumps; update all callees after inlining.
* ipa-inline.h (INLINE_HINT_in_scc,
Hi,
as pointed out in the audit trail, my first patch for this C++11 parsing
issue was misguided: I changed cp_parser_template_id but in fact C++11
wants new special *lexing* rules, which must be active outside templates
too, as the additional test (and the old manded one) shows. Thus the
...from sources.redhat.com to sourceware.org.
With that, there are only a few references left in java/ .
Gerald
Index: c99status.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/c99status.html,v
retrieving revision 1.58
diff -u -3 -p
On Sun, 28 Oct 2012, Jan Hubicka wrote:
Bootstrapped/regtested x86_64-linux.
Honza
* ipa-inline.c (edge_badness): Reduce precision; use scc hints.
(inline_small_functions): Fix dumps; update all callees after inlining.
* ipa-inline.h (INLINE_HINT_in_scc,
On Sun, 28 Oct 2012, Jan Hubicka wrote:
Bootstrapped/regtested x86_64-linux.
Honza
* ipa-inline.c (edge_badness): Reduce precision; use scc hints.
(inline_small_functions): Fix dumps; update all callees after inlining.
* ipa-inline.h (INLINE_HINT_in_scc,
This fixes part of PR 55041 by updating the hash table printers to
account for Francois's recent changes.
PR libstdc++/55041
* python/libstdcxx/v6/printers.py (Tr1UnorderedMapPrinter): Update
to handle hashtable as member of unordered_map not base class.
Hello,
this patch lets some predicates on floating point constants answer true
for vectors, so optimizations are applied.
Tested bootstrap + testsuite (default languages).
2012-10-29 Marc Glisse marc.gli...@inria.fr
PR middle-end/55027
gcc/
* tree.c (real_zerop,
Ping. This issue stands in the way of a very simple solution of PR
fortran/51727. I've re-attached the patch for your convenience.
On 15 Oct 2012 at 22:51:05 +0200 Tobias Schlüter wrote:
The attached patch adds out-of-memory diagnostics for code using STL
containers by using
On 10/28/2012 04:14 PM, Marc Glisse wrote:
Hello,
this patch lets some predicates on floating point constants answer
true for vectors, so optimizations are applied.
Great.
I wonder how are we doing lately in terms of function pointer inlining?!
If the current optimizers can already able to
* ping *
On 16.10.2012 23:18, Tobias Burnus wrote:
In the Bessel-function algorithm, there was the useless code:
ret-base_addr = ret-base_addr;
And in all files which included ifunction.m4 is such code:
iall_i4 (gfc_array_i4 * const restrict retarray,
...
if (len = 0)
* ping *
On 19.10.2012 18:54, Tobias Burnus wrote:
gfortran's INTENT(IN) check was too strict for do variables. While a
variable in the normal do-stmt and in an io-implied-do is in the scope
and, hence, the variable may not be modified for a nonpointer
intent(in) variable.
However,
On 10/28/2012 04:46 PM, Paolo Carlini wrote:
On 10/28/2012 04:14 PM, Marc Glisse wrote:
Hello,
this patch lets some predicates on floating point constants answer
true for vectors, so optimizations are applied.
Great.
I wonder how are we doing lately in terms of function pointer
inlining?!
On Sun, 28 Oct 2012, Paolo Carlini wrote:
On 10/28/2012 04:46 PM, Paolo Carlini wrote:
On 10/28/2012 04:14 PM, Marc Glisse wrote:
Hello,
this patch lets some predicates on floating point constants answer true
for vectors, so optimizations are applied.
Great.
I wonder how are we doing
Hi Tobias,
* ping *
On 16.10.2012 23:18, Tobias Burnus wrote:
In the Bessel-function algorithm, there was the useless code:
ret-base_addr = ret-base_addr;
The patch is OK. Thanks a lot!
Thomas
Hi Tobias,
* ping *
This is OK. Thanks for the patch!
Thomas
On Sun, 28 Oct 2012, Marc Glisse wrote:
[there are 4 real_*p that only differ by 1 character]
It is true that we could have a single function in tree.c:
bool real_intcstp (const_tree, int);
The helper function could even take a REAL_VALUE_TYPE as second
argument, so the non-inline part
Hi,
On 10/28/2012 05:51 PM, Marc Glisse wrote:
On Sun, 28 Oct 2012, Marc Glisse wrote:
[there are 4 real_*p that only differ by 1 character]
It is true that we could have a single function in tree.c:
bool real_intcstp (const_tree, int);
The helper function could even take a REAL_VALUE_TYPE
On Sun, 28 Oct 2012, Paolo Carlini wrote:
I was writing something like the below.
I would move the one-liners (real_zerop, etc) to tree.h, but that looks
good, yes.
--
Marc Glisse
Quoting Andreas Schwab sch...@linux-m68k.org:
+These flags are automatically generated; you should not override
them in tm.c:
Typo: s/:$/./, also @file{tm.c}.
Thanks. I have re-bootstrapped the amended patch on i686-pc-linux-gnu.
2012-10-28 Joern Rennecke joern.renne...@embecosm.com
Quoting Richard Biener richard.guent...@gmail.com:
Thus, you can allow the length to vary downwards as well as upwards
across iterations with suitable definitions of the @code{length} attribute
and/or @code{ADJUST_INSN_LENGTH}. Care has to be taken that this does not
lead to infinite loops.
On 10/28/2012 06:06 PM, Marc Glisse wrote:
On Sun, 28 Oct 2012, Paolo Carlini wrote:
I was writing something like the below.
I would move the one-liners (real_zerop, etc) to tree.h, but that
looks good, yes.
Ah great. But please, don't wait on me, I'm in the middle of too many
other
On Mon, Oct 22, 2012 at 11:09 PM, Jakub Jelinek wrote:
On Mon, Oct 22, 2012 at 10:51:43PM +0200, Steven Bosscher wrote:
Wouldn't it be way cheaper to just export dfs_find_deadend from cfganal.c
and call it in calc_dfs_tree on each unconnected bb?
I.e. (untested with the exception of the
Working on a problem where var-tracking started to spend more time
after LRA is switched on, I found that LRA creates significant #
clobbers for x86 code (I saw 20% of all insns). Clobbers are created for
correct live range analysis in LRA in cases when matching pseudos of
*different modes*
On Sun, Oct 28, 2012 at 9:06 PM, Vladimir Makarov wrote:
Unfortunately, it does not solve the problem I mentioned. Now, LRA
generates approximately the same # of insns and debug_insn. Moreover, two
functions (canonicalize_values_star and set_slot_part) in var-tracking
spending most of time
On 12-10-27 6:07 PM, Steven Bosscher wrote:
On Sat, Oct 27, 2012 at 11:49 PM, Steven Bosscher wrote:
So I'm going to revert this patch.
Or actually better, this lighter-weight patch. Will commit after the
usual testing.
I returned to this problem several times and every time I failed to use
On 12-10-27 11:34 AM, Joern Rennecke wrote:
Bootstrapped (c,c++) on i686-pc-linux-gnu.
Committed as obvious.
Thanks, Joern.
Installed.
Gerald
Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.48
diff -u -3 -p -r1.48 changes.html
--- changes.html21 Oct 2012 11:01:37 - 1.48
+++
Hello world,
the attached patch, which is not in its final stage, implements some
warnings for index variables of DO loops. For the following situations,
errors/warnings are issued when an index loop variable is
passed as an actual argument:
- If the dummy argument has INTENT(OUT). I think an
Gerald Pfeifer ger...@pfeifer.com writes:
+ liG++ now supports a code-std=c++1y/code option for experimentation
Fixed the typo.
Andreas.
--- changes.html.~1.49.~2012-10-28 22:11:57.0 +0100
+++ changes.html2012-10-28 22:12:37.0 +0100
@@ -133,7 +133,7 @@ B
While working on the sources-sourceware transition, I noticed
some not directly related items and went ahead and addressed
them. Committed.
2012-10-28 Gerald Pfeifer ger...@pfeifer.com
* build-snapshot.html: Refer to GNU/Linux, simplify link to
installation documentation,
On Sun, 28 Oct 2012, Andreas Schwab wrote:
+ liG++ now supports a code-std=c++1y/code option for experimentation
Fixed the typo.
Thanks, Andreas! The validator did not complain -- which shows
that a pair of human eyes _is_ valuable. :-)
Gerald
On Wed, 24 Oct 2012, Jan Hubicka wrote:
few things I think are worth to be mentioned in changes.html.
Nice!
Index: changes.html
===
+ liLTO partitioning has been rewritten for better reliability
+ and maintanibility.
On Tue, 23 Oct 2012, Richard Earnshaw wrote:
On 23/10/12 23:36, Steven Bosscher wrote:
Will you also add an announcement of this to the news page (home page)
and to gcc-4.8/changes.html?
I'm sure we can... :-)
You have to. :-) Please.
Gerald
Say, what? Anyone know what this is about?
cp ../.././gcc/../fixincludes/README-fixinc include-fixed/README
chmod a+r include-fixed/README
echo timestamp stmp-int-hdrs
TARGET_CPU_DEFAULT= \
HEADERS=auto-host.h ansidecl.h DEFINES=USED_FOR_TARGET \
/bin/sh ../.././gcc/mkconfig.sh tconfig.h
On Sun, 21 Oct 2012, Jonathan Wakely wrote:
I was going to say Ack, since it's a doc patch, but somehow my
own tests on various platforms (FreeBSD, GNU/Linux,...) did not
confirm /usr/include/c++ in the search path.
Or do you mean that it's at the root of some search paths, that
is
Hi,
Workaround now exists for trunk mingw-w64 headers.
Kai approved over IRC, so anybody with commit rights please push.
ChangeLog
2012-10-29 Jonathan Yong jo...@users.sourceforge.net
* config/os/mingw32-w64/os_defines.h: Remove
_GLIBCXX_HAVE_BROKEN_VSWPRINTF
as no longer
Hi,
this patch makes optimizer to predict this-field to be optimized out.
The main motivation for this is to make destructors that only calls destructor
of inner type to be inlined, even in the cold regions.
Bootstrapped/regtested x86_64-linux. Comitted.
2012-10-28 Jan Hubicka j...@suse.cz
On 28 October 2012 22:21, Gerald Pfeifer wrote:
On Sun, 21 Oct 2012, Jonathan Wakely wrote:
I was going to say Ack, since it's a doc patch, but somehow my
own tests on various platforms (FreeBSD, GNU/Linux,...) did not
confirm /usr/include/c++ in the search path.
Or do you mean that it's at
On 29 October 2012 00:08, Jonathan Wakely wrote:
Yes, libdir/gcc/target/version/../../../../include/c++/version would
be more accurate, because libdir is not necessarily /usr
I'll come up with something better ...
I've committed this to the trunk.
commit
The following patch fixes PR55106. A value in GENERAL_REGS is
inherited into a move with destination pseudo of SSE_REGS. It results
into secondary move for which inheritance is tried again an again. It
means cycling LRA passes.
The patch was successfully bootstrapped on x86/x86-64.
On Sun, Oct 28, 2012 at 5:43 PM, Vladimir Makarov vmaka...@redhat.com wrote:
The following patch fixes PR55106. A value in GENERAL_REGS is inherited
into a move with destination pseudo of SSE_REGS. It results into secondary
move for which inheritance is tried again an again. It means
The code changes seem fine, but I don't think a testcase should depend on
the details of what system strings.h declares (or even that it exists)
like that. If you want a system header declaration, add a header to the
testsuite that uses #pragma GCC system_header to be sure it's handled as
Hi Vladimir,
There are many trialling white spaces in LRA codes. This patch removes
them.
H.J.
---
diff --git a/gcc/lra-assigns.c b/gcc/lra-assigns.c
index 1f89338..c558a4d 100644
--- a/gcc/lra-assigns.c
+++ b/gcc/lra-assigns.c
@@ -149,7 +149,7 @@ init_regno_assign_info (void)
{
int i,
50 matches
Mail list logo
