On Fri, Apr 05, 2013 at 10:54:48AM +0400, Andrey Belevantsev wrote:
> I am testing the revert of this backport for 4.6 and will commit it
> in about an hour or so. However, I am surprised we don't hit this
Ok, thanks.
> either on 4.7, 4.8 or trunk. Some flush_pending_lists calls are
> protected
Jakub Jelinek wrote:
>On Thu, Apr 04, 2013 at 08:37:47PM +0200, Richard Biener wrote:
>> Can you factor out a function that returns
>> A proper qimode value if possible or null and
>> Use it in both places?
>
>Like this?
You should be able to remove zero, minus one and constructor special casing
On Fri, Apr 05, 2013 at 09:21:16AM +0200, Richard Biener wrote:
> Jakub Jelinek wrote:
>
> >On Thu, Apr 04, 2013 at 08:37:47PM +0200, Richard Biener wrote:
> >> Can you factor out a function that returns
> >> A proper qimode value if possible or null and
> >> Use it in both places?
> >
> >Like th
On Fri, 5 Apr 2013, Jakub Jelinek wrote:
On Fri, Apr 05, 2013 at 09:21:16AM +0200, Richard Biener wrote:
Jakub Jelinek wrote:
On Thu, Apr 04, 2013 at 08:37:47PM +0200, Richard Biener wrote:
Can you factor out a function that returns
A proper qimode value if possible or null and
Use it in bo
> Jakub, you don't happen to remember any changes in this area that could
> hide the problem for 4.7 and later?
We do have regressions on the 4.7 branch in the scheduler (CCed Olivier who
has more information).
--
Eric Botcazou
> Thinking about this some more: This could be fixed by inserting a
> machine-specific pass just after delayed-branch scheduling, like in
> the attached patch. I think the same is possible with the dbr_schedule
> call in the MIPS backend.
>
> Eric, what do you think of this approach?
No objection
Hello,
while debugging I made the finding that in find_func_aliases rhsop
might be used as NULL for gimple_assign_single_p items. It should be
using for the gimple_assign_single_p instead directly the rhs1-item as
argument to pass to get_constraint_for_rhs function.
ChangeLog
2013-04-05 Kai Ti
> Hmm, what do you have in mind for such a situation?
>
> If extract_asm_operands returns NULL then asm_noperands will return -1.
>
> If extract_asm_operands returns non-NULL then asm_noperands deep-dives
> the PATTERN of the insn (just like extract_asm_operands) and returns
> >= 0 unless the ins
Gabriel Dos Reis writes:
>> diff --git a/libstdc++-v3/include/c_global/cstdio
>> b/libstdc++-v3/include/c_global/cstdio
>> index fcbec0c..037a668 100644
>> --- a/libstdc++-v3/include/c_global/cstdio
>> +++ b/libstdc++-v3/include/c_global/cstdio
>> @@ -131,7 +131,9 @@ namespace std
>>using ::
On Fri, Apr 5, 2013 at 4:01 AM, Rainer Orth
wrote:
> Gabriel Dos Reis writes:
>
>>> diff --git a/libstdc++-v3/include/c_global/cstdio
>>> b/libstdc++-v3/include/c_global/cstdio
>>> index fcbec0c..037a668 100644
>>> --- a/libstdc++-v3/include/c_global/cstdio
>>> +++ b/libstdc++-v3/include/c_glob
From: Zhouyi Zhou
Sender: Zhouyi Zhou
To:
Subject: [PATCH v2] inline fail reporting: reporting inline fail caused by
overwritable function
When inline failed because of callee is overwritable, gcc will not report it
in dump file as other inline failing cases do. This patch correct this.
Gabriel Dos Reis writes:
> On Fri, Apr 5, 2013 at 4:01 AM, Rainer Orth
> wrote:
>> Gabriel Dos Reis writes:
>>
diff --git a/libstdc++-v3/include/c_global/cstdio
b/libstdc++-v3/include/c_global/cstdio
index fcbec0c..037a668 100644
--- a/libstdc++-v3/include/c_global/cstdio
>
On Fri, Apr 5, 2013 at 4:13 AM, Rainer Orth
wrote:
> Gabriel Dos Reis writes:
>
>> On Fri, Apr 5, 2013 at 4:01 AM, Rainer Orth
>> wrote:
>>> Gabriel Dos Reis writes:
>>>
> diff --git a/libstdc++-v3/include/c_global/cstdio
> b/libstdc++-v3/include/c_global/cstdio
> index fcbec0c..0
On 5 April 2013 08:42, Konstantin Serebryany
wrote:
>
> On Fri, Apr 5, 2013 at 10:37 AM, Jakub Jelinek wrote:
> > On Thu, Apr 04, 2013 at 09:53:30PM +0200, Bernhard Reutner-Fischer wrote:
> >> uClibc can be built without Largefile support, add the corresponding
> >> guards. uClibc does not have _
On 5 April 2013 11:23, Gabriel Dos Reis wrote:
> On Fri, Apr 5, 2013 at 4:13 AM, Rainer Orth
> wrote:
>> Gabriel Dos Reis writes:
>>
>>> On Fri, Apr 5, 2013 at 4:01 AM, Rainer Orth
>>> wrote:
Gabriel Dos Reis writes:
>> diff --git a/libstdc++-v3/include/c_global/cstdio
>> b
On Fri, Apr 05, 2013 at 11:46:44AM +0200, Bernhard Reutner-Fischer wrote:
> > >> --- a/libsanitizer/sanitizer_common/sanitizer_allocator.cc
> > >> +++ b/libsanitizer/sanitizer_common/sanitizer_allocator.cc
> > >> @@ -9,11 +9,13 @@
> > >> // run-time libraries.
> > >> // This allocator that is use
This should fix the handlers for platforms without __atomic_exchange
for pointers by using a mutex. I used the old __mutex type not
std::mutex because it's available on more platforms and works for the
'single' thread model too. I didn't try to optimise away the atomic
ops for accessing the handle
Hi!
I've noticed another place where distdir: goal was present, in
boehm-gc/include/Makefile.in on 4.6 branch. Fixed thusly, committed to 4.6.
2013-04-05 Jakub Jelinek
PR other/43620
* Makefile.am (AUTOMAKE_OPTIONS): Add no-dist.
* include/Makefile.am (AUTOMAKE_OPTIO
> I don't know whether backporting this would be better than reverting
> the offending change as just done on 4.7.
I presume that you meant on the 4.6 branch.
--
Eric Botcazou
On Apr 5, 2013, at 12:21 , Eric Botcazou wrote:
>> I don't know whether backporting this would be better than reverting
>> the offending change as just done on 4.7.
>
> I presume that you meant on the 4.6 branch.
Arf, indeed, thanks for correcting :)
Joseph pointed out the cortex-a53 wasn't documented in invoke.texi.
Fixed thusly.
Ramana
2013-04-05 Ramana Radhakrishnan
* doc/invoke.texi (ARM Options): Document cortex-a53 support.Index: gcc/doc/invoke.texi
===
--- gc
Jakub Jelinek wrote:
>On Fri, Apr 05, 2013 at 09:21:16AM +0200, Richard Biener wrote:
>> Jakub Jelinek wrote:
>>
>> >On Thu, Apr 04, 2013 at 08:37:47PM +0200, Richard Biener wrote:
>> >> Can you factor out a function that returns
>> >> A proper qimode value if possible or null and
>> >> Use it
On 05.04.2013 14:10, Olivier Hainque wrote:
On Apr 5, 2013, at 10:13 , Eric Botcazou wrote:
We do have regressions on the 4.7 branch in the scheduler (CCed Olivier who
has more information).
Right: we do see a SEGV while compiling the attached monitor.i (preprocessed
output from a qemu tr
On 5 April 2013 11:13, Jonathan Wakely wrote:
> This should fix the handlers for platforms without __atomic_exchange
> for pointers by using a mutex. I used the old __mutex type not
> std::mutex because it's available on more platforms and works for the
> 'single' thread model too. I didn't try to
Richard,
There has been something that has bothered me about you proposal for the
storage manager and i think i can now characterize that problem. Say i
want to compute the expression
(a + b) / c
converting from tree values, using wide-int as the engine and then
storing the result in a tre
Hi all,
With r197491 I added testsuite support for vectorisation of rounding
functions on ARMv8 NEON, but the options set up
for vect.exp results in the testsuite trying to test all the vect tests with
ARMv8 NEON which does not work on
ARMv7 targets and simulators that don't support ARMv8 (like qe
Hi!
I've missed that OpenMP 4.0 rc2 in 2.6's last restriction mentions:
"For C++, in the simd construct the only random access iterator type that are
for var are pointer types."
The following patch implements that restriction (no testcase yet until simd
is fully supported), committed to branch.
On Apr 5, 2013, at 13:22 , Andrey Belevantsev wrote:
>> http://gcc.gnu.org/ml/gcc-patches/2012-08/msg01625.html
>>
>> I don't know whether backporting this would be better than reverting
>> the offending change as just done on 4.7.
>
> I'd say for 4.6 the best way is to revert. PR 56077 is
On Fri, Apr 05, 2013 at 12:46:48PM +0200, Richard Biener wrote:
> >BTW, the integer_all_onesp stuff is broken for this from what I can
> >see, for complex
> >numbers it returns true for -1 + 0i where all bytes aren't 0xff, so we
> >need
> >to rule out COMPLEX_CSTs (or do integer_all_onesp on each p
On Fri, Apr 05, 2013 at 03:28:11PM +0200, Olivier Hainque wrote:
>
> On Apr 5, 2013, at 13:22 , Andrey Belevantsev wrote:
> >> http://gcc.gnu.org/ml/gcc-patches/2012-08/msg01625.html
> >>
> >> I don't know whether backporting this would be better than reverting
> >> the offending change as ju
On Apr 5, 2013, at 15:40 , Jakub Jelinek wrote:
> As written in PR56848, the patch should be reverted for 4.7.3
> and reapplied together with the additional fix after 4.7.3 is released
> (before 4.7.3 release there is just too short time to do anything else,
> while before 4.7.4 there will be ple
On 04/05/13 14:06, Kyrylo Tkachov wrote:
Hi all,
With r197491 I added testsuite support for vectorisation of rounding
functions on ARMv8 NEON, but the options set up
for vect.exp results in the testsuite trying to test all the vect tests with
ARMv8 NEON which does not work on
ARMv7 targets and s
On Thu, Mar 28, 2013 at 2:27 AM, Richard Biener
wrote:
> On Wed, Mar 27, 2013 at 6:22 PM, Teresa Johnson wrote:
>> I found that the node weight updates on cloned nodes during ipa-cp were
>> leading to incorrect/insane weights. Both the original and new node weight
>> computations used truncating
- -Original Message-
> From: Ramana Radhakrishnan
> Sent: 05 April 2013 15:06
> To: Kyrylo Tkachov
> Cc: gcc-patches@gcc.gnu.org; mikest...@comcast.net
> Subject: Re: [PATCH][ARM][testsuite] Fix testsuite options for testing
> rounding vectorisation on ARMv8
>
> On 04/05/13 14:06, Kyrylo T
On 04/05/13 15:55, Kyrylo Tkachov wrote:
Hi all
This patch fixes a warning in arm.c about a comparison between signed and
unsigned integers.
This is usually harmless, but during bootstrap we compile with -Werror and
this turns
into an error. The fix is a one-liner.
Tested to make sure warning g
Hi all
This patch fixes a warning in arm.c about a comparison between signed and
unsigned integers.
This is usually harmless, but during bootstrap we compile with -Werror and
this turns
into an error. The fix is a one-liner.
Tested to make sure warning goes away and did a regtest run for
arm-none
Hi all,
This patch is a backport of the fix for PR 56720 where we would ICE on
arm-*-* when trying to
expand vcond with a floating point unorderd comparison cases. The patch is
almost identical
to the trunk patch at:
http://gcc.gnu.org/ml/gcc-patches/2013-03/msg00652.html
except that it adds expli
On 04/05/13 16:26, Greta Yorsh wrote:
-Original Message-
From: Richard Earnshaw
Sent: 22 February 2013 16:30
To: Greta Yorsh
Cc: GCC Patches; Ramana Radhakrishnan; ni...@redhat.com;
p...@codesourcery.com
Subject: Re: [PATCH,ARM][1/n] New patterns for subtract with carry
On 18/02/13 18:
This patch prevents segfault when using --param min-crossjump-insns=0.
What can happen in that case is that flow_find_cross_jump returns 0,
thus nmatch is 0, then
nmatch < PARAM_VALUE (PARAM_MIN_CROSSJUMP_INSNS)
doesn't hold, thus we continue, but we segfault later on when
doing split_block. I thi
On 03/15/13 18:16, Julian Brown wrote:
Hi,
At present, the libcall helpers implementing atomic operations
(__sync_val_compare_and_swap_X) for char and short types suffer from
a type mismatch. This is leading to test failures, i.e.:
FAIL: gcc.dg/atomic-compare-exchange-1.c execution test
FAIL: g
On 04/05/13 15:44, Kyrylo Tkachov wrote:
- -Original Message-
From: Ramana Radhakrishnan
Sent: 05 April 2013 15:06
To: Kyrylo Tkachov
Cc: gcc-patches@gcc.gnu.org; mikest...@comcast.net
Subject: Re: [PATCH][ARM][testsuite] Fix testsuite options for testing
rounding vectorisation on ARMv8
On Fri, Apr 5, 2013 at 10:22 AM, Eric Botcazou wrote:
>> Thinking about this some more: This could be fixed by inserting a
>> machine-specific pass just after delayed-branch scheduling, like in
>> the attached patch. I think the same is possible with the dbr_schedule
>> call in the MIPS backend.
>>
On 2013-04-04 19:32 , Jing Yu wrote:
OK for google/gcc-4_8?
OK.
Diego.
Joerg Wunsch wrote:
The attached patch adds the new ATmega*RFR* devices to AVR-GCC.
[...]
Supply the auto generated files, too. Cf. t-avr, avr-mcus.def etc.
Johann
This patch improves code generation for Newton-Raphson reciprocal
estimates for divide and square root on PowerPC
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56843).
For the divide case, we formerly had specialized routines for two- and
three-pass estimates. Rather than add new routines for one-
Jakub Jelinek wrote:
>On Fri, Apr 05, 2013 at 12:46:48PM +0200, Richard Biener wrote:
>> >BTW, the integer_all_onesp stuff is broken for this from what I can
>> >see, for complex
>> >numbers it returns true for -1 + 0i where all bytes aren't 0xff, so
>we
>> >need
>> >to rule out COMPLEX_CSTs (or
On Fri, Apr 5, 2013 at 1:49 PM, Bill Schmidt
wrote:
> This patch improves code generation for Newton-Raphson reciprocal
> estimates for divide and square root on PowerPC
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56843).
>
> For the divide case, we formerly had specialized routines for two- an
On Fri, 5 Apr 2013, Marc Glisse wrote:
Shouldn't we change integer_all_onesp to do what its name says and create a
separate integer_minus_onep for the single place I could find where it would
break, the folding of x * -1 ?
2013-04-05 Marc Glisse
* tree.c (integer_all_onesp) : Test
On 04/05/2013 02:29 AM, Kai Tietz wrote:
Hello,
while debugging I made the finding that in find_func_aliases rhsop
might be used as NULL for gimple_assign_single_p items. It should be
using for the gimple_assign_single_p instead directly the rhs1-item as
argument to pass to get_constraint_for_r
On Apr 5, 2013, at 7:05 AM, Ramana Radhakrishnan wrote:
> Ok by me but I'd like Mike to have another look.
Ok by me.
On 04/05/2013 12:20 AM, Jonathan Wakely wrote:
On 4 April 2013 21:16, François Dumont wrote:
I think this is mostly very good, thanks for cleaning it up. The
indentiation of the closing brace for __is_assignable_helper looks
wrong. Is there a reason that __is_assignable_helper::__test uses a
d
The following patch adds a new functionality to IRA to improve RA in
presence of hard registers in RTL. IRA already had some mechanism
dealing with hard regs but it affected only pseudos in *the same insn*
containing hard register. This technique was not good enough to
remove regmove pass code
On 04/05/2013 09:22 AM, Marek Polacek wrote:
This patch prevents segfault when using --param min-crossjump-insns=0.
What can happen in that case is that flow_find_cross_jump returns 0,
thus nmatch is 0, then
nmatch < PARAM_VALUE (PARAM_MIN_CROSSJUMP_INSNS)
doesn't hold, thus we continue, but we s
On Fri, Apr 05, 2013 at 02:21:57PM -0600, Jeff Law wrote:
> On 04/05/2013 09:22 AM, Marek Polacek wrote:
> >This patch prevents segfault when using --param min-crossjump-insns=0.
> >What can happen in that case is that flow_find_cross_jump returns 0,
> >thus nmatch is 0, then
> >nmatch < PARAM_VALU
On 04/05/2013 02:33 PM, Jakub Jelinek wrote:
On Fri, Apr 05, 2013 at 02:21:57PM -0600, Jeff Law wrote:
On 04/05/2013 09:22 AM, Marek Polacek wrote:
This patch prevents segfault when using --param min-crossjump-insns=0.
What can happen in that case is that flow_find_cross_jump returns 0,
thus nm
So, I was debugging why the nightly run of this script did not actually
every update anything. As part of that I manually ran the script on
gcc.gnu.org.
Let's say the output was not particularly helpful. ;-)
This patch addresses that and does not simply ignore _all_ output any
more, plus it exp
On 04/05/2013 02:14 PM, Vladimir Makarov wrote:
The following patch adds a new functionality to IRA to improve RA in
presence of hard registers in RTL. IRA already had some mechanism
dealing with hard regs but it affected only pseudos in *the same insn*
containing hard register. This techniq
On Fri, Apr 05, 2013 at 02:42:19PM -0600, Jeff Law wrote:
> ? I must be missing something, the change causes an early bail out
> from try_crossjump_to_edge.
>
> We don't want to raise the min to > 0 as that doesn't allow the user
> to turn on this specific transformation.
The condition is
if (
On 04/05/2013 02:50 PM, Jakub Jelinek wrote:
On Fri, Apr 05, 2013 at 02:42:19PM -0600, Jeff Law wrote:
? I must be missing something, the change causes an early bail out
from try_crossjump_to_edge.
We don't want to raise the min to > 0 as that doesn't allow the user
to turn on this specific tr
> Andrey, could you please take care of this ?
I've reverted the patch after bootstrapping/regtesting on x86-64/Linux.
--
Eric Botcazou
On 2 April 2013 11:14, Jakub Jelinek wrote:
>
> Yeah, IMHO we definitely want to support GCC_COLORS env var or similar, with
> same syntax as e.g. GREP_COLORS, but with different names of the (two
> letter?) color names.
The attached patch adds support for customization via GCC_COLORS
following g
Hello,
Almost trivial, but it makes the dumps look so much better if UNSPEC
names are printed instead of just numbers.
OK for trunk?
Ciao!
Steven
* config/sparc/sparc.md: Use define_c_enum for "unspec" and "unspecv".
* config/sparc/sparc.md: Use define_c_enum for "unspec" and "
On 13-04-05 4:48 PM, Jeff Law wrote:
On 04/05/2013 02:14 PM, Vladimir Makarov wrote:
The following patch adds a new functionality to IRA to improve RA in
presence of hard registers in RTL. IRA already had some mechanism
dealing with hard regs but it affected only pseudos in *the same insn*
c
On Fri, 5 Apr 2013, Thomas Schwinge wrote:
> As I understand it (and I may add that this is the first time ever I'm
> looking at soft-fp internals), that appears to be a bug in soft-fp, in
> this very code added ten years ago ;-), which is invoked by means of
> _df_to_tf.o:__extenddftf2 for this c
On Apr 5, 2013, at 11:18 PM, Eric Botcazou wrote:
>> Andrey, could you please take care of this ?
>
> I've reverted the patch after bootstrapping/regtesting on x86-64/Linux.
Thanks Eric.
65 matches
Mail list logo
