public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Vaish, Mayank" <Mayank.Vaish@amd.com>
To: Sam James <sam@gentoo.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: GCC 13 release date
Date: Wed, 19 Apr 2023 06:13:27 +0000	[thread overview]
Message-ID: <PH7PR12MB714047BEF843B67EE944D89D87629@PH7PR12MB7140.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87ilds769h.fsf@gentoo.org>

[AMD Official Use Only - General]

Thanks Sam. This is clear and helpful. 

Regards, 
Mayank

-----Original Message-----
From: Sam James <sam@gentoo.org> 
Sent: Wednesday, April 19, 2023 11:38 AM
To: Vaish, Mayank <Mayank.Vaish@amd.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 13 release date


"Vaish, Mayank" <Mayank.Vaish@amd.com> writes:

> [AMD Official Use Only - General]
>

Hi Mayank,

> Thanks Sam for your prompt response. 
>
> The status message https://gcc.gnu.org/pipermail/gcc/2023-April/241140.html. mentions GCC 13.0.1 report. Is there any stable GCC 13.0.0 tag/branch available for general use. 

It means that GCC 13.1 will be tagged in a week from the
releases/gcc-13 branch. No GCC 13.0 release will exist.

(It's a 13.0.1 status report because releases/gcc-13 is 13.0.1 (for development) until it officially becomes 13.1 and is released. 13.0.x would never be released.)

I hope that helps.

TL;DR: GCC 13 is coming out in a week, if everything goes OK. And it will be called '13.1' officially.

>
> Regards,
> Mayank
>
> -----Original Message-----
> From: Sam James <sam@gentoo.org>
> Sent: Wednesday, April 19, 2023 11:02 AM
> To: Vaish, Mayank <Mayank.Vaish@amd.com>
> Cc: gcc@gcc.gnu.org
> Subject: Re: GCC 13 release date
>
>
> "Vaish, Mayank via Gcc" <gcc@gcc.gnu.org> writes:
>
>> [AMD Official Use Only - General]
>>
>> Hi,
>>
>> Looking out for GCC 13 release date. GCC Development plan<https://gcc.gnu.org/develop.html#timeline> only mention about GCC 13 Stage 4 development.
>>
>> Please comment on the formal GCC 13 release date.
>
> I'm just an observer, but RC1 is likely to be today and if nothing goes badly, GCC 13 will follow a week after that.
>
> This was covered on this mailing list in the last status report a few days ago: https://gcc.gnu.org/pipermail/gcc/2023-April/241140.html.
>
>>
>> Thanks.
>> Mayank
>
> thanks,
> sam

      reply	other threads:[~2023-04-19  6:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19  4:55 Vaish, Mayank
2023-04-19  5:32 ` Sam James
2023-04-19  5:52   ` Vaish, Mayank
2023-04-19  6:07     ` Sam James
2023-04-19  6:13       ` Vaish, Mayank [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH7PR12MB714047BEF843B67EE944D89D87629@PH7PR12MB7140.namprd12.prod.outlook.com \
    --to=mayank.vaish@amd.com \
    --cc=gcc@gcc.gnu.org \
    --cc=sam@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).