This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 4.7.3 plans?
- From: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: xunxun <xunxun1982 at gmail dot com>, Kenny Simpson <theonetruekenny at yahoo dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sun, 24 Mar 2013 22:33:34 -0500
- Subject: Re: gcc 4.7.3 plans?
- References: <1359428956 dot 84169 dot YahooMailClassic at web142405 dot mail dot bf1 dot yahoo dot com> <CAFiYyc2rzSO3JDjUfTwJyPdQLUm0BCSPSieEyPomXChOk=baPg at mail dot gmail dot com> <51443A35 dot 4030308 at gmail dot com> <CAFiYyc2heOkwLi0dvLKPO3P-gcH3H5EOawoadfKhiXhKqC_oUg at mail dot gmail dot com>
On 3/18/2013 4:03 AM, Richard Biener wrote:
> On Sat, Mar 16, 2013 at 10:24 AM, xunxun <xunxun1982@gmail.com> wrote:
>> 于 2013/1/29 星期二 19:24, Richard Biener 写道:
>>
>>> On Tue, Jan 29, 2013 at 4:09 AM, Kenny Simpson
>>> <theonetruekenny@yahoo.com> wrote:
>>>> There have been quite a few fixes on the 4.7 branch since 4.7.2 was
>>>> released 4 months ago and several of the remaining regression bugs have
>>>> fixes in trunk.
>>>>
>>>> What are the plans for 4.7.3?
>>> There will be a 4.7.3 release (shortly) before 4.8.0 releases. There
>>> is quite a number
>>> of regression fixes that are suitable for backporting to the 4.7 branch
>>> still.
>>>
>>> Richard.
>>>
>>>> thanks,
>>>> -Kenny
>>>>
>> The GCC 4.8 branch has been created and a first release candidate
>> is being prepared right now.
>>
>> When will 4.7.3 be released?
> When it's released.
>
> Why are you so interested in a date?
In general, knowing that the GCC Community has committed to a release
in days/weeks/months as one of the responses put it, lets folks plan.
If one's goal is to use official, unpatched releases, then those releases
have importance.
If you are a typical GNU/Linux distribution, this is not a concern
as most distributions ship with patches. But the "unwashed masses"
would really like to stick to something the GCC Community has put
a seal of goodness on.
Speaking for the RTEMS Community, we strive to be able to use
unpatched FSF releases and try to push patches upstream in a timely
manner to accomplish this. We don't always get things merged
in time and there are always bugs discovered after releases but
these are small.
So yes, knowing one will happen is important. Putting days/weeks/months
on it, helps people schedule. Even if that is nothing but a goal.
A statement like "within X of the 4.8.0 release date which is
expected in about Y timeframe" would help.
One response offered to help. Take them up on it. Give them something
to do. Volunteers are good. :)
> Richard.
>
>> --
>> Best Regards,
>> xunxun
>>
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985