Hello Everyone,
Here are seven patches about array notations that were submitted
to GCC patches mailing list for the Cilkplus branch. If anyone finds
any problems or have any objections, please let me know. Otherwise, I
will check them into the Cilkplus branch Monday.
Here are the patch email
Here are the toplevel changes.
2011-12-30 Walter Lee
* MAINTAINERS (tilegx port): Add self.
(tilepro port): Add self.
diff -r -u -p -N /home/packages/gcc-4.7.0-182680/MAINTAINERS ./MAINTAINERS
--- /home/packages/gcc-4.7.0-182680/MAINTAINERS 2011-12-18 01:31:26.0
-0500
++
Here is the libgomp port.
2011-12-30 Walter Lee
* configure.tgt: Handle tilegx and tilepro.
* config/linux/tile/futex.h: New file.
diff -r -u -p -N
/home/packages/gcc-4.7.0-182680/libgomp/config/linux/tile/futex.h
./libgomp/config/linux/tile/futex.h
--- /home/packages/gcc-4.7.
Here is the libgcc port.
2011-12-30 Walter Lee
* config.host: Handle tilegx and tilepro.
* config/tilegx/sfp-machine.h: New file.
* config/tilegx/sfp-machine32.h: New file.
* config/tilegx/sfp-machine64.h: New file.
* config/tilegx/t-crtstuff: New file.
Here is the libcpp port.
2011-12-30 Walter Lee
* configure.ac: Require 64-bit hwint for tilegx and tilepro.
* configure: Regenerate.
diff -r -u -p -N /home/packages/gcc-4.7.0-182680/libcpp/configure
./libcpp/configure
--- /home/packages/gcc-4.7.0-182680/libcpp/configure2011
Here are the contrib changes.
2011-12-30 Walter Lee
* config-list.mk (tilegx-linux-gnu): Add.
(tilepro-linux-gnu): Add.
* gcc_update (gcc/config/tilegx/mul-tables.c): New dependencies.
(gcc/config/tilepro/mul-tables.c): New dependencies.
diff -r -u -p -N /home/pa
I'm resubmitting the gcc ports to TILE-Gx and TILEPro as replies to
this email. The resubmission addresses the feedback made by Richard
Henderson in:
http://gcc.gnu.org/ml/gcc-patches/2011-11/msg01232.html, and
http://gcc.gnu.org/ml/gcc-patches/2011-11/msg01247.html
Feedback by Joseph Myers made
I udpated the powerpc changes in the GCC 4.7 summary:
--- htdocs/gcc-4.7/changes.html.~1~ 2011-12-30 18:43:34.885278709 -0500
+++ htdocs/gcc-4.7/changes.html 2011-12-30 18:55:33.455278920 -0500
@@ -576,19 +576,32 @@ well.
PowerPC/PowerPC64
Vectors of type vector long long or vector l
This is the bootstrap failure of the Ada compiler on MIPS/IRIX, a recent
regression present on mainline and 4.6 branch. The stage 2 compiler
miscompiles the stage 3 compiler (sem_type.adb:Disambiguate) because of an
oversight in the fix for PR tree-opt/50569 which changed build_ref_for_model to
In working on something else, I was using the target pragmas I added in late
November, and I noticed that I had a thinko in setting some of the options like
-mfriz that aren't bitmasks. I committed the patch as obvious:
2011-12-30 Michael Meissner
* config/rs6000/rs6000.c (rs6000_inne
Dear Paul,
Paul Richard Thomas wrote:
Bootstrapped and regtested on i686/Ubuntu 11.1 - OK for trunk?
2011-12-30 Paul Thomas
* trans-array.c (gfc_array_allocate): Null allocated memory of
newly allocted class arrays.
PR fortran/51529
PR fortran/46328
* inter
On Fri, 30 Dec 2011, Steve Kargl wrote:
> I'm sorry, but I find "clang did this, so g++ better follow
> suit" to be a rather uncompelling technical reason for
> defining __cplusplus to be 201103L [1]. The technical question
> is fairly simple: "Does g++ conform to the C++11 standard?"
I think t
On Dec 30, 2011, at 10:18 AM, Fabien Chêne wrote:
> 2011/12/30 Jason Merrill :
>> Why // { dg-warning "" } deprecated on some tests, and
>> // { dg-warning "deprecated" } on others? I would think all of the could
>> use the second form.
>
> I was believing that "// { dg-warning "" } deprecated" w
On Fri, Dec 30, 2011 at 10:38:03AM +0100, Jakub Jelinek wrote:
> On Thu, Dec 29, 2011 at 08:12:51PM -0800, Steve Kargl wrote:
> > The audit trail in the PR pretty much sums up the problem.
> > OK to commit?
>
> Can you tune up the comments a little bit?
> If you look up http://gcc.gnu.org/gcc-4.7/
Dear All,
This patch represents a rather complete fix for this PR. In fact, I
suspect that it also fixes other PRs but I have been out of internet
range for a week and have not been able to check.
The processing of typebound operators has been made more straight
forward here by the addition of a
I've committed this patch to fix and improve coverage reporting:
1) the time stamp local_tick will be -1 if the user overrides the random seed.
In such cases the gcov data file should be deleted, just as it would if the time
cannot be determined.
2) there was a typo in gcov_dump when dumping
2011/12/30 Jason Merrill :
> Why // { dg-warning "" } deprecated on some tests, and
> // { dg-warning "deprecated" } on others? I would think all of the could
> use the second form.
I was believing that "// { dg-warning "" } deprecated" was the way to
test a warning in old-deja. If we can use the
I've committed this patch which does 2 things in libgcov:
1) Robustifies the error recovery if malloc fails during buffering coverage
data. It also generates more informative error messages.
2) Fixes a long standing bug regarding detecting when an object file is used in
multiple programs. C
On 12/30/2011 12:38 PM, Joseph S. Myers wrote:
In the absence of a resolution of a DR against C11 that allows alignof in
this case, I think we should continue to disallow it for C.
Ah, I didn't realize that C11 had alignof as well. OK, then.
Jason
On Fri, 30 Dec 2011, Jason Merrill wrote:
> On 12/28/2011 07:07 PM, Paolo Carlini wrote:
> > I think the resolution of core/930 and C++11 itself are pretty clear:
> > alignof of an array of unknown bound is fine, provided the element type
> > is complete of course.
>
> I think it makes sense for
Hi,
On 12/30/2011 06:27 PM, Jason Merrill wrote:
On 12/28/2011 07:07 PM, Paolo Carlini wrote:
I think the resolution of core/930 and C++11 itself are pretty clear:
alignof of an array of unknown bound is fine, provided the element type
is complete of course.
I think it makes sense for this chan
On 12/28/2011 07:07 PM, Paolo Carlini wrote:
I think the resolution of core/930 and C++11 itself are pretty clear:
alignof of an array of unknown bound is fine, provided the element type
is complete of course.
I think it makes sense for this change to apply to C as well, on the
same principle
After Thumb-2's peephole2 adds flag clobbering on suitable insns in
order to generate 16-bit encoding for them, if-conversion can't
transform these insns into cond_execs. In theory, if the instruction
were converted to conditional form, it would also use 16-bit encoding,
so the flag clobbering
If one of branches has significantly greater probability than the other,
then it may be better to rely on CPU's branch prediction and block
reordering, than putting rarely executed instructions into the pipeline.
In this patch we set 10% frequency ratio as a cutoff.
On SPEC2K INT with -O2 this
This patch adjusts the maximum number of instructions in a basic block
to be converted into conditional form from 5 to 4. The idea is that the
5-th conditional instruction comes at cost of extra IT-instruction,
while 4 insns fit into single IT-block, so this IT-instruction replaces
eliminated b
GCC's scheduler has no idea about Thumb-2 IT blocks, which are generated
from cond_execs at the stage of emitting assembly code. So it treats
conditional instructions independently, and may intermix them with
non-conditional instructions, which will cause generation of extra IT
instructions.
We
This patch adds splits for if_then_else into cond_execs. This helps
generating the minimum number of IT-blocks for two consequent
if_then_elses, e.g. one ITETE insn instead of two ITE insns, if
if_then_else were expanded directly into assembly code.
There are three splitters for the cases when b
Hi,
This series of patches solves few issues we found with Thumb-2
conditional insns. These fixes include:
1) Split if_then_else into cond_execs to generate only required minimum
of IT-blocks;
2) Grouping conditional insns of same INSN_PRIORITY to avoid excessive
splitting of IT-blocks;
3)
Why // { dg-warning "" } deprecated on some tests, and
// { dg-warning "deprecated" } on others? I would think all of the
could use the second form.
+ cp_token *diag_token;
Let's initialize this to NULL to make sure we avoid spurious warnings
about it being used without being set.
OK wi
On Fri, Dec 30, 2011 at 03:20:30PM +0100, Richard Guenther wrote:
> Err - are not _all_ backends using trampolines to represent address-taken
> nested functions? At least I remeber to see them for x86 and plain C
Targets using function descriptors (powerpc64-*linux*,
powerpc*-*aix*, ia64-*) don't
On Wed, Dec 28, 2011 at 8:04 PM, Jakub Jelinek wrote:
> Hi!
>
> For some calls (like memcpy and other builtins that are known to pass
> through the first argument) we know the value of the lhs, but still
> we shouldn't be replacing the call with just a mere assignment of that
> known value to the
On Tue, Dec 27, 2011 at 11:44 AM, Jan Hubicka wrote:
> Hi
> this patch solves problem with negative frequency that is result of overflow
> in profile updating code. The testcase shows quite pathological case where
> profile is misguessed and the mistake is propagated across the CFG by jump
> thre
On Sat, Dec 24, 2011 at 8:00 PM, Steven Bosscher wrote:
> On Tue, Dec 20, 2011 at 9:46 AM, Tristan Gingold wrote:
>> Hi,
>>
>> currently alpha/vms backend emits a trampoline entry point for all nested
>> functions. This is a waste of code space, as although nested functions are
>> very common
Dear all,
first, I want to wish all of you a happy New Year.
Attached you find a patch which calls _gfortran_caf_deregister for
allocatable coarrays - for -fcoarray=lib. In the caf libraray version,
coarrays are allocated/deallocated in the library. The
allocation/deallocation was working bef
* doc/xml/manual/extensions.xml: Improve markup and note that some
extensions are included in C++11.
* doc/xml/manual/concurrency_extensions.xml: Likewise.
Tested with 'make doc-xml-validate-docbook doc-html-docbook'
Committed to trunk
Index: doc/xml/manual/extensions.xml
On 22 December 2011 00:23, Jonathan Wakely wrote:
> The most frequently asked question on gcc-help, and a frequently
> reported "bug" in bugzilla, is
> http://gcc.gnu.org/wiki/FAQ#configure_suffix
>
> It is almost always caused by installing libgmp.so etc. in a
> non-standard location and not using
Hi Ramana,
Please find attached revised LDRD generation patch for A15 ARM mode.
Because of the major rework in ARM RTL epilogue patch, this patch has
undergone some changes.
The patch is tested with check-gcc, bootstrap and check-gdb without
regression.
Ok for trunk?
-- diff --git a/gcc/config
Hi!
Please find attached revised LDRD generation patch for A15 Thumb-2 mode.
Because of the major rework in ARM and Thumb-2 RTL epilogue patches,
this patch has undergone some changes.
The patch is tested with check-gcc, bootstrap and check-gdb without
regression.
Ok for trunk?
-- diff --git a
Hi,
applied mainline and 4_6-branch.
Thanks,
Paolo.
/
2011-12-30 Paolo Carlini
PR libstdc++/51711
* include/bits/regex.h (regex_replace): Fix thinko.
* testsuite/28_regex/algorithms/regex_replace/char/51711.cc: New.
* testsuite/28_rege
On Thu, Dec 29, 2011 at 08:12:51PM -0800, Steve Kargl wrote:
> The audit trail in the PR pretty much sums up the problem.
> OK to commit?
Can you tune up the comments a little bit?
If you look up http://gcc.gnu.org/gcc-4.7/cxx0x_status.html
you'll see that most of the C++11 features are already im
the early inline decisions are still good to dump out. However the
opt-info should check 'if (profile_info)' to decide if count and max
count info need to be dumped.
David
On Fri, Dec 30, 2011 at 12:31 AM, Dehao Chen wrote:
> Hi,
>
> This patch makes the -fopt-info print more concise info:
> 1.
Hi,
This patch makes the -fopt-info print more concise info:
1. only inline decisions after einline are printed
2. print in a more compact format
Bootstrapped with no problem.
Is it okay for google-4_6 and google-main branch?
Thanks,
Dehao
gcc/ChangeLog.google-4_6
2011-12-30 Dehao Chen
42 matches
Mail list logo
