public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <idsandoe@googlemail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: GCC 14.1 Release Candidate available from gcc.gnu.org
Date: Thu, 2 May 2024 10:26:40 +0100	[thread overview]
Message-ID: <18DDA8CC-B226-45BE-98E3-B734255A4E07@googlemail.com> (raw)
In-Reply-To: <ZjDJEldLGYqfoIkT@tucnak>



> On 30 Apr 2024, at 11:33, Jakub Jelinek via Gcc <gcc@gcc.gnu.org> wrote:
> 
> The first release candidate for GCC 14.1 is available from
> 
> https://gcc.gnu.org/pub/gcc/snapshots/14.1.0-RC-20240430/
> ftp://gcc.gnu.org/pub/gcc/snapshots/14.1.0-RC-20240430/
> 
> and shortly its mirrors.  It has been generated from git commit
> r14-10154-g7a00c459cbb913a.
> 
> I have so far bootstrapped and tested the release candidate on
> x86_64-linux.
> Please test it and report any issues to bugzilla.
> 
> If all goes well, we'd like to release 14.1 on Tuesday, May 7th.
> 

I have bootstrapped and tested this on powerpc, i686 darwin9
x86_64 darwin10 - 21 and darwin23, also on i686-darwin17.
most of the results have been pushed to sourceware bunsen.

In doing this I have found a wrong-code regression in
Objective-C that is confined to Darwin (NeXT v2 runtime) and I
will be applying a patch to trunk later (and then to affected
branches) hopefully, it will be considered suitable for 14.1 too.

thanks
Iain


      parent reply	other threads:[~2024-05-02  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 10:33 Jakub Jelinek
2024-04-30 19:34 ` William Seurer
2024-05-01 12:50 ` Frank Scheiner
2024-05-02  9:26 ` Iain Sandoe [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=18DDA8CC-B226-45BE-98E3-B734255A4E07@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).