public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/98590] [11 regression] Bootstrap failure with Ada on Cygwin since switch to C++11
Date: Fri, 08 Jan 2021 10:47:01 +0000	[thread overview]
Message-ID: <bug-98590-4-88qGpsVfGa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98590-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98590

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It is not really a penalization, the -std= is (supposed to be) added only
during bootstraps for stage1, so if one builds a cross-compiler or
non-bootstrapped compiler, it isn't added and nobody is penalized, if one
bootstraps the compiler, the only penalization will be that stage1 could be
slightly slower (it will be slow anyway, as it is built with -O0, isn't it).

  parent reply	other threads:[~2021-01-08 10:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 20:07 [Bug bootstrap/98590] New: " mikpelinux at gmail dot com
2021-01-07 20:10 ` [Bug bootstrap/98590] " mikpelinux at gmail dot com
2021-01-07 20:12 ` mikpelinux at gmail dot com
2021-01-07 20:25 ` ebotcazou at gcc dot gnu.org
2021-01-08  8:32 ` rguenth at gcc dot gnu.org
2021-01-08 10:03 ` ebotcazou at gcc dot gnu.org
2021-01-08 10:23 ` jakub at gcc dot gnu.org
2021-01-08 10:42 ` ebotcazou at gcc dot gnu.org
2021-01-08 10:47 ` jakub at gcc dot gnu.org [this message]
2021-01-09 14:05 ` mikpelinux at gmail dot com
2021-02-01 11:32 ` ebotcazou at gcc dot gnu.org
2021-02-03 16:45 ` mikpelinux at gmail dot com
2021-02-26 12:30 ` rguenth at gcc dot gnu.org
2021-03-02 22:20 ` cvs-commit at gcc dot gnu.org
2021-03-07 17:02 ` mikpelinux at gmail dot com

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=bug-98590-4-88qGpsVfGa@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).