This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
- From: Chen Gang S <gang dot chen at sunrus dot com dot cn>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: Jeff Law <law at redhat dot com>, Mike Stump <mikestump at comcast dot net>, gcc-patches List <gcc-patches at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Mon, 26 Jan 2015 06:01:13 +0800
- Subject: Re: [PATCH] toplev.c: Process the failure when read fails for random_seed
- Authentication-results: sourceware.org; auth=none
- References: <54A0D2CA dot 3010806 at sunrus dot com dot cn> <54AAEF0E dot 6040706 at redhat dot com> <54BF776C dot 1090504 at sunrus dot com dot cn> <8808FAA9-0A81-47E4-8456-33F0F506AE25 at comcast dot net> <54C0E54F dot 4060702 at sunrus dot com dot cn> <54C1281F dot 1070000 at redhat dot com> <54C152BA dot 6010503 at sunrus dot com dot cn> <54C15520 dot 80703 at redhat dot com> <54C1628C dot 7070006 at sunrus dot com dot cn> <alpine dot LSU dot 2 dot 11 dot 1501252046300 dot 2527 at tuna dot site>
On 1/26/15 03:50, Gerald Pfeifer wrote:
> On Friday 2015-01-23 04:50, Chen Gang S wrote:
>> And I want to consult: for passing assignment working flow, must I
>> make a patch which contents much code lines? (At present, my patches
>> are all trivial patch).
>
> No, the assignment process does not have any requirements on
> past or current patches. You even can complete the assignment
> process without a single patch at that point.
>
> So, do not worry.
>
> And we are happy to see improvements and fixes of all kinds,
> so please continue.
>
Thank you very much for your encourage. :-)
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed