This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'
- From: Chen Gang <gang dot chen dot 5i5j at gmail dot com>
- To: Michael Eager <eager at eagerm dot com>
- Cc: Mike Stump <mikestump at comcast dot net>, Jeff Law <law at redhat dot com>, davem at redhat dot com, gcc-patches List <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 21 Dec 2014 05:45:55 +0800
- Subject: Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'
- Authentication-results: sourceware.org; auth=none
- References: <bekwguasixaphab5pghrhbxp dot 1411603920412 at email dot android dot com> <544673D6 dot 7020607 at gmail dot com> <544709B8 dot 7080707 at gmail dot com> <544CCEC0 dot 50406 at gmail dot com> <544D3C03 dot 4040307 at eagerm dot com> <544DA2FE dot 5080709 at gmail dot com> <54510EB7 dot 1020904 at gmail dot com> <5452457A dot 20109 at gmail dot com> <5453C1DB dot 5010505 at gmail dot com> <545F68F4 dot 1000501 at gmail dot com> <546E09E6 dot 3030909 at gmail dot com> <54799F26 dot 6020308 at gmail dot com> <54954ACD dot 8060707 at gmail dot com> <5495A469 dot 8080808 at eagerm dot com>
On 12/21/2014 12:31 AM, Michael Eager wrote:
> On 12/20/14 02:09, Chen Gang wrote:
>> By the way, if this thread really has negative effect with other members,
>> please warn me, I should not notify it to mailing list again, and try my
>> best to finish it within myself.
>
> I appreciate your enthusiasm and perseverance in pursuing this bug.
>
> If the problem you are working on has changed from the mb-gcc issue,
> change the subject. Otherwise, keep up the good work.
>
Thank you for your encouragement, and I should continue. At present, I
guess my own main issues are:
- Have no enough time resources on open source:
sometimes need work overtime.
need 4 hours per work day on subway between home and work office
(come 2 hours, go 2 hours, so total is 4 hours).
need spend time for my child: check his homework, play with him.
(especially in weekend).
- Really not familiar with gcc:
Sometimes can find real world issues, but can not fix them in time.
Sometimes can find coding issues, but do not know whether it can
cause real world issues or not (may also waste other members time
resources, but get no positive result).
- Not familiar with related environments for each architectures.
So next, I should change myself for solving the issues above, firstly:
- I shall try to spend 1-1.5 hours for reading gcc related documents (
e.g. "gcc info") in work day when I on subway (another time on subway
is for listening Holy Bible, reading news, or sleeping for a while).
- I shall mainly forcus on finding real world issues and try to fix in
time. And stop finding coding issues (which may get negative effect
with others -- at least may waste other members time resources).
- Still contiue for constructing all related enviroments (it is always
necessary) for architectures.
Welcome any ideas, suggestions or completions by any members.
Thanks.
--
Chen Gang
Open share and attitude like air water and life which God blessed