This patch fixes the stride setting for cshift1; hence, it fixes
gfortran.dg/optional_dim_3.f90.
Build and regtested on x86-64-linux - 13 failing tests remain.
OK?
Tobias
2012-07-15 Tobias Burnus
* m4/cshift1.m4 (cshift1): Correctly set stride multiplier.
* generated/cshift1_16.c: Regener
On Sun, Jul 15, 2012 at 1:56 AM, H.J. Lu wrote:
> On Wed, Apr 25, 2012 at 12:14 PM, Jakub Jelinek wrote:
>
>> We have a splitter for reg1 = reg2 & 0x, but only if regnums
>> are different. But movl %edi, %edi is a cheaper variant of
>> andq $0x, %rdi even with the same register a
The following patch compares the stride multiplier rather than the
stride; that's not only faster as it avoids an useless division, but it
also fixes gfortran.dg/associated_2.f90 by not dividing by zero.
Build and regtested on x86-64-gnu-linux, and committed as Rev. 189492.
Remaining 12 (branc
Hi Tobias,
This patch fixes the stride setting for cshift1; hence, it fixes
gfortran.dg/optional_dim_3.f90.
Build and regtested on x86-64-linux - 13 failing tests remain.
OK?
OK. Thanks for the patch!
Thomas
Installed.
Andreas.
* g++.dg/debug/dwarf2/pubnames-2.C: Support all known comment
characters.
diff --git a/gcc/testsuite/g++.dg/debug/dwarf2/pubnames-2.C
b/gcc/testsuite/g++.dg/debug/dwarf2/pubnames-2.C
index 375b856..3b7f95e 100644
--- a/gcc/testsuite/g++.dg/debug/dwarf2/pubnam
This patch cleans up the source code and generated code ("dump") by
changing (ubound-lbound+1) calculations to directly taking the "extent".
Except for a faster -O0 performance and saving some cycles during code
generation, the code should be the same.
The only real code change I did was to g
Hello world,
this fixes an ICE with allocation of coarrays. Regression-tested.
OK for trunk? What about 4.7?
Thomas
2012-07-15 Thomas König
PR fortran/53824
* resolve.c (resolve_allocate_deallocate): If both
start indices are NULL, skip the test for equal
On Tue, 10 Jul 2012, Jonathan Wakely wrote:
>> Yes, but people should use inline namespaces instead; we should deprecate
>> this form and then remove it in 4.9.
>
> * doc/extend.texi (Namespace Association): Alter cautionary text.
I think this also should go into the GCC 4.8 release notes
On 15/07/2012 13:24, Tobias Burnus wrote:
> This patch cleans up the source code and generated code ("dump") by
> changing (ubound-lbound+1) calculations to directly taking the "extent".
> Except for a faster -O0 performance and saving some cycles during code
> generation, the code should be the sa
Added a caveat to the gcc-4.7/changes.html page about C++11 ABI
incompatibilities.
Committed to wwwdocs.
Index: htdocs/gcc-4.7/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.120
diff -u
On 15 July 2012 12:26, Gerald Pfeifer wrote:
> On Tue, 10 Jul 2012, Jonathan Wakely wrote:
>>> Yes, but people should use inline namespaces instead; we should deprecate
>>> this form and then remove it in 4.9.
>>
>> * doc/extend.texi (Namespace Association): Alter cautionary text.
>
> I thi
Chung-Lin Tang writes:
> This patch adds scheduling support for the NetLogic XLP, including a new
> pipeline description, and associated changes.
>
> Asides from the new xlp.md description file, there are also some sync
> primitive attribute modifications, for better scheduling of sync loops
> (Ma
Hello,
The attached patch removes old peephole patterns that seem to be unused.
Tested with 'make all'. CSiBE result-size (-m4-single -ml -O2
-mpretend-cmove) does not show any changes.
OK?
Cheers,
Oleg
ChangeLog:
* config/sh/sh.md: Delete mov related define_peephole patterns.
Index:
Hello,
This patch replaces usages of CONST_OK_FOR_I06 with
satisfies_constraint_I06 and moves the CONST_OK_FOR_I10 macro to sh.c.
Tested with 'make all-gcc'.
OK?
Cheers,
Oleg
ChangeLog:
* config/sh/sh.h (CONST_OK_FOR_I06): Delete.
(CONST_OK_FOR_I10): Move macro to ...
*
Thomas Koenig wrote:
this fixes an ICE with allocation of coarrays. Regression-tested.
OK for trunk? What about 4.7?
OK. Thanks for the patch. Regarding 4.7, I don't have a strong opinion.
Given that it is a simple patch and given that (single-image) coarrays
work rather well in 4.7, maybe
On Fri, 22 Jun 2012, H.J. Lu wrote:
> I am not sure if news.html is the best place for this.
news.html definitely is not a good place for this, cf. the comment
in that file. ;-)
> How about putting it in gcc-4.8/changes.html?
Yes, that fits.
> Does it look OK?
Index: ./gcc-4.8/changes.html
The auto-vectorizer is overly aggressive when not constrained by the
vectorizer cost model. Although the cost model is by no means perfect,
it does a reasonable job of avoiding many poor vectorization decisions.
Since the auto-vectorizer is enabled by default at -O3 and above, we
should also enabl
Hello,
If I'm not mistaken, the SH target does not use the '"* ..."' notation
for output template code. The patch below updates the table in
backends.html to reflect the current status.
Cheers,
Oleg
Index: htdocs/backends.html
===
On Sun, 15 Jul 2012, Jonathan Wakely wrote:
>> I think this also should go into the GCC 4.8 release notes
>> (gcc-4.8/changes.html)?
> I can do that too. There's no gcc-4.8 dir yet, do I need to copy over
> the various other files from the gcc-4.7 dir or can I just create
> changes.html and leave
On Sun, 1 Jul 2012, Tom G. Christensen wrote:
> Latest results for 4.7.x
Thanks, Tom!
Gerald
Hi Terry,
On Mon, 9 Jul 2012, Terry Guo wrote:
> As it becomes our long term goal to deliver arm-none-eabi tool chain
> based on GCC 4.6/4.7/4.8 and future branches, I am going to use the
> following pattern to document this branch family. Is it ok to commit?
yep, this looks good (and sorry for
Hi Jonathan,
On Sat, 14 Jul 2012, Jonathan Wakely wrote:
> Attached this time, here's the original mail again:
>
> PR c++/53919
> * doc/install.texi (Installing GCC): Refer to instructions for
> released versions. Fix hyphenation.
>
> Whether or not we want the release-sp
Oleg Endo wrote:
> This patch replaces usages of CONST_OK_FOR_I06 with
> satisfies_constraint_I06 and moves the CONST_OK_FOR_I10 macro to sh.c.
> Tested with 'make all-gcc'.
>
> OK?
OK.
Regards,
kaz
Oleg Endo wrote:
> The attached patch removes old peephole patterns that seem to be unused.
> Tested with 'make all'. CSiBE result-size (-m4-single -ml -O2
> -mpretend-cmove) does not show any changes.
>
> OK?
OK.
Regards,
kaz
Oleg Endo wrote:
> If I'm not mistaken, the SH target does not use the '"* ..."' notation
> for output template code. The patch below updates the table in
> backends.html to reflect the current status.
Looks obvious and OK to me.
Regards,
kaz
On 5 July 2012 21:13, Matthew Gretton-Dann wrote:
> On 26/06/12 14:44, Richard Earnshaw wrote:
>>
>> On 25/06/12 15:59, Matthew Gretton-Dann wrote:
>>>
>>> All,
>>>
>>> This patch adds support to the ARM backend for generating floating-point
>>> fused multiply-accumulate.
>>>
>>> OK?
>>>
>>> gcc/C
These were spotted while debugging usage of atomics within
glibc. The kind of changes are microoptimizations,
nanooptimizations, a buglet and a major issue. Micro: the
load-store-conditional sequence for compare-and-swap I
originally committed was an earlier version improved later.
Nanooptimizati
Use the new need_atomic_barrier_p.
gcc:
* config/cris/sync.md ("atomic_fetch_")
("atomic_compare_and_swap"): Gate expand_mem_thread_fence
calls on result of call to need_atomic_barrier_p.
Index: config/cris/sync.md
==
Buglet in "atomic_compare_and_swap", allowing (in theory)
a volatile or post-increment memory operand. Simplest and
safest fixed by excluding all memory operands.
gcc:
* config/cris/sync.md ("atomic_compare_and_swap"): Change
predicate to nonmemory_operand for operand 3. Add FIXM
Microoptimizations for the atomic patterns themselves. Constant
operands are so common that it seems wasteful not to handle the
most common cases and avoid wasting a register.
gcc/testsuite:
* gcc.target/cris/20011127-1.c: Adjust to %P being a
valid register operand output modifie
Well, give up by default that is, and fix it up in a helper
function in glibc to hold a global byte-sized atomic lock for
the duration. (Sorry!) Yes, this means that
fold_builtin_atomic_always_lock_free is wrong. It knows about
alignment in general but doesn't handle the case where the
default a
Buglet in cris_preferred_reload_class, incidental, apparently
without effect at least regarding failing test-cases. A class
disjunct from the input was returned as "preferred". It could
arguably be gcc_asserted as a sanity-check by the caller that
the returned class is a subset of the original cl
I think CONSTANT_ADDRESS_P can and should be eliminated,
replaced by something like
CONSTANT_P (x) && targetm.legitimate_address_p (QImode, x, false)
(or QImode replaced by the known used mode) in the code
currently calling it.
It should, because the default definition is redundant and evil;
easy
Hi
The following patches implemented the optimizations suggested by
PR53189, optimizations of 64bit logic operation with constant. Could
any maintainer help to review it?
http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00087.html
http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00169.html
http://gcc.gnu
> From: Hans-Peter Nilsson
> Date: Mon, 16 Jul 2012 05:49:00 +0200
> gcc:
> * config/cris/sync.md ("atomic_fetch_")
> ("cris_atomic_fetch__1")
> ("atomic_compare_and_swap")
> ("cris_atomic_compare_and_swap_1"): Make
> conditional on TARGET_ATOMICS_MAY_CALL_LIBFUNCS
On 2012/7/16 12:28 AM, Richard Sandiford wrote:
> Chung-Lin Tang writes:
>> This patch adds scheduling support for the NetLogic XLP, including a new
>> pipeline description, and associated changes.
>>
>> Asides from the new xlp.md description file, there are also some sync
>> primitive attribute m
On 16/07/2012, at 6:37 PM, Chung-Lin Tang wrote:
> On 2012/7/16 12:28 AM, Richard Sandiford wrote:
>> Chung-Lin Tang writes:
>>> This patch adds scheduling support for the NetLogic XLP, including a new
>>> pipeline description, and associated changes.
>>>
>>> Asides from the new xlp.md descripti
37 matches
Mail list logo
