I found typo in the testcase header, fixed. Ok to apply to trunk?
thanks, Dinar.
On Fri, Apr 18, 2014 at 1:13 PM, Dinar Temirbulatov
wrote:
> Hello,
> Here is another version of fix. This time, I added
> complete_type_or_else call just before aggregate_value_p. Bootstra
wrote:
> On 04/07/2014 03:46 PM, Jason Merrill wrote:
>>
>> I guess we need to call complete_type before aggregate_value_p.
>
>
> complete_type_or_else, actually.
>
> Jason
>
>
2014-04-18 Dinar Temirbulatov
PR c++/57958
* semantics.c (appl
Hi,
I revised the patch from
http://gcc.gnu.org/ml/gcc-patches/2014-04/msg00083.html.
This change fixes PR57958 (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57958)
For this code:
auto fn = [] (const Foo& x) {
return (x);
};
{
Foo a;
fn(a);
}
Current version of trunk generates fol
Hi,
Following change fixes gimple production for lambda function, in the
patch I assumed that constructing COMPOUND_EXPR for the return value
of "auto" type function resoluted to CLASS_TYPE_P is wrong. Tested
x86_64-pc-linux-gnu by applying to trunk with no new regressions.
Thanks, Dinar.
fix
Ping?
Hi,
Here is the patch, Tested by profiledbootstrap. Ok for google gcc-4.8?
thanks, Dinar.
profiledbootstrap-fix1.patch
Description: Binary data
t;
>>>>
>>>> On Tue, Jul 30, 2013 at 11:56 AM, Teresa Johnson
>>>> wrote:
>>>>> cc'ing Rong and David since this came from LIPO support.
>>>>>
>>>>> The patch as-is removes the one use of PARAM_GCOV_DEBUG (whi
IPO support.
>>
>> The patch as-is removes the one use of PARAM_GCOV_DEBUG (which is on
>> by default) without removing the parameter itself. What is the failure
>> mode you see from this code?
>>
>> Thanks,
>> Teresa
>>
>> On Tue, Jul 30, 2013 a
Hello
This change allows to complete profiledbootstrap on the google gcc-4.8
branch, tested with make bootstrap with no new regressions. OK for
google 4.8?
thanks, Dinar.
profiledbootstrap-fix.patch
Description: Binary data
ge on
x86_64-linux with no errors.
thanks, Dinar.
On Sat, Jun 1, 2013 at 4:55 PM, Jakub Jelinek wrote:
> On Sat, Jun 01, 2013 at 10:11:24AM +0200, Jakub Jelinek wrote:
>> On Sat, Jun 01, 2013 at 08:39:58AM +0400, Dinar Temirbulatov wrote:
>> > I am in
Hi,
oh, This is my mistake I should have bootstrap the compiler. I am
investigating the problem.
thanks, Dinar.
On Sat, Jun 1, 2013 at 7:50 AM, H.J. Lu wrote:
> On Wed, May 29, 2013 at 9:36 AM, Dinar Temirbulatov
> wrote:
>> Here is the corrected version of change. Also
Hi,
I updated MAINTAINERS list with following change(patch attached).
thanks, Dinar.
MAINTAINERS.patch
Description: Binary data
MAX_PENDING_LIST_LENGTH.
On Wed, May 29, 2013 at 6:49 PM, Jeff Law wrote:
> On 05/29/2013 06:52 AM, Steven Bosscher wrote:
>>
>> Hello,
>>
>> On Wed, May 29, 2013 at 2:01 PM, Dinar Temirbulatov wrote:
>>>
>>> Hi,
>>> I noticed that
is longer than
>>> MAX_PENDING_LIST_LENGTH. Tested with gcc testsite on x86_64-linux-gnu
>>> with c and c++ enabled. Ok for trunk?
>>> thanks, Dinar.
>>>
>>> 2013-05-28 Dinar Temirbulatov
>>>
>>> PR rtl-optimiz
++ enabled. Ok for trunk?
thanks, Dinar.
2013-05-28 Dinar Temirbulatov
PR rtl-optimization/57268
* sched-deps.c (sched_analyze_2): Flush dependence list
then it is longer than MAX_PENDING_LIST_LENGTH.
fix.patch
Description: Binary data
Hi,
During investigation of some defect, I found that for HImode reload
pass generated three instruction with QImode but for modern arm
machines that could be done with just one instruction. Attached patch
adds that capability.
thanks, Dinar.
reload_o
Hi Ramana,
Here is obvious fix for PR49423, I just added pool range for
arm_zero_extendqisi2, arm_zero_extendqisi2_v6, arm_zero_extendhisi2,
arm_zero_extendhisi2_v6 patterns.
thanks, Dinar.
PR49423.patch
Description: Binary data
than "-O3"?
thanks, Dinar.
On Fri, Jun 15, 2012 at 12:12 PM, Richard Earnshaw wrote:
> On 14/06/12 19:46, Dinar Temirbulatov wrote:
>> Hi,
>> OK for trunk?
>> thanks, Dinar.
>>
>
> I'm still not comfortable about th
Hi,
OK for trunk?
thanks, Dinar.
On Tue, Jun 12, 2012 at 11:00 AM, Paolo Bonzini wrote:
> Il 12/06/2012 08:52, Dinar Temirbulatov ha scritto:
>>> is safe? That is, that the underflows cannot produce a wrong result?
>
> [snip]
>
> Thanks very much!
>
Hi, Paolo.
Here is the new version of patch. I have tested this version with gcc
testsuite only on i686 without new regressions, for now. Mips and arm
tests are in progress.
One strange thing I noticed:
>
> No need for this gen_reg_rtx, either, by passing a NULL_RTX target below.
>
>> + carry
oh, I found typo in comment in the end of patch. fixed.
thanks, Dinar.
On Thu, Jun 7, 2012 at 2:14 PM, Dinar Temirbulatov
wrote:
> Hi,
> Here is new version of patch based up on Paolo review, again tested on
> arm-7l, mips-32r2 (74k), i686 without new re
, mode, 1, 1);
>>> > + emit_store_flag_force (c1, GT, u1, tmp, mode, 1, 1);
>>> > + result = expand_binop (mode, ior_optab, c, c1, cres, 1,
>>> > OPTAB_LIB_WIDEN);
>>> > + if (!result)
>>> > + return 0;
>>>
hink it is ready now?
thanks, Dinar.
On Tue, May 22, 2012 at 7:45 PM, Richard Henderson wrote:
> On 05/22/12 07:05, Dinar Temirbulatov wrote:
>> + if ((size - 1 > BITS_PER_WORD
>> + && BITS_PER_WORD == 32 && mode == DImode)
>
> Do note that t
Earnshaw wrote:
> On 03/05/12 11:27, Dinar Temirbulatov wrote:
>
>
> This clearly needs more work.
>
> Comments: Need to end with a period and two spaces.
> Binary Operators: Need to be surrounded with white space.
sorry for this, hope I resolved such issues with the new v
Hi,
Here is updated version of patch. I added comments describing the algorithm.
> Hi Dinar. I'm afraid it gives the wrong results for some dividends
> * 82625484914982912 / 2023346444509052928: gives 4096, should be zero
> * 18317463604061229328 / 2023346444509052928: gives 4109, should be 9
>
Hi,
Here is the patch that adds support for divide 64-bit by constant for
32-bit target machines, this patch was tested on arm-7a with no new
regressions, also I am not sure on how to avoid for example i686
targets since div operation there is fast compared to over targets and
it showed better perf
hi, Richard
On Mon, Sep 26, 2011 at 11:50 AM, Richard Sandiford
wrote:
> Dinar Temirbulatov writes:
>> I found typo in the patch instead of checking *set_after != 0 it was
>> set_after != 0, here is corrected version of patch. I retested the
>> patch without typo on mip
PM, Dinar Temirbulatov
wrote:
> hi, Richard,
> This version of patch showed no regressions on mipsel-unknown-linux-gnu.
> Thanks, Dinar.
>
>
> On Wed, Sep 21, 2011 at 4:59 PM, Richard Sandiford
> wrote:
>> Dinar Temirbulatov writes
hi, Richard,
This version of patch showed no regressions on mipsel-unknown-linux-gnu.
Thanks, Dinar.
On Wed, Sep 21, 2011 at 4:59 PM, Richard Sandiford
wrote:
> Dinar Temirbulatov writes:
>> @@ -14696,7 +14696,11 @@ mips_avoid_hazard (rtx after,
28 matches
Mail list logo
