Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Romain Naour <romain.naour@gmail.com>,
	Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] toolchain/Config.in: update gcc version for gcc bug 68485
Date: Fri, 29 Jul 2022 14:12:05 +0200	[thread overview]
Message-ID: <20220729141205.2bde03b3@windsurf> (raw)
In-Reply-To: <20220729121055.168510-1-giulio.benetti@benettiengineering.com>

On Fri, 29 Jul 2022 14:10:54 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

>  # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68485. This bug still
> -# exists in gcc 9.x
> +# exists in gcc 11.x

What about the recently introduced gcc 12.x ? :-)

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-07-29 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 12:10 [Buildroot] [PATCH 1/2] toolchain/Config.in: update gcc version for gcc bug 68485 Giulio Benetti
2022-07-29 12:10 ` [Buildroot] [PATCH 2/2] package/mariadb: work around " Giulio Benetti
2022-09-13 14:15   ` Peter Korsgaard
2022-07-29 12:12 ` Thomas Petazzoni via buildroot [this message]
2022-07-29 12:29   ` [Buildroot] [PATCH 1/2] toolchain/Config.in: update gcc version for " Giulio Benetti
2022-07-29 12:33     ` Thomas Petazzoni via buildroot
2022-07-29 12:47       ` Giulio Benetti
2022-07-29 19:58 ` Thomas Petazzoni via buildroot

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=20220729141205.2bde03b3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.de_schampheleire@nokia.com \
    --cc=thomas.petazzoni@bootlin.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