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 target/99401] Rebuilding the compiler with itself fails at -O2
Date: Fri, 05 Mar 2021 12:51:22 +0000	[thread overview]
Message-ID: <bug-99401-4-5xSMn3ATAB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99401-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Anyway, in that case you want to attach here the preprocessed source on which
some undefined references to LC* appear and state exact gcc options that were
used to compile that, so that others can try to reproduce it e.g. with
cross-compilers.

  parent reply	other threads:[~2021-03-05 12:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  8:53 [Bug c++/99401] New: GCC11 MinGW-w64 32-bit build fails with undefined reference to `LC0' brechtsanders at users dot sourceforge.net
2021-03-05  9:19 ` [Bug c++/99401] " ebotcazou at gcc dot gnu.org
2021-03-05 10:33 ` [Bug target/99401] " brechtsanders at users dot sourceforge.net
2021-03-05 11:23 ` ebotcazou at gcc dot gnu.org
2021-03-05 12:39 ` [Bug target/99401] Rebuilding the compiler with itself fails at -O2 ebotcazou at gcc dot gnu.org
2021-03-05 12:44 ` brechtsanders at users dot sourceforge.net
2021-03-05 12:51 ` jakub at gcc dot gnu.org [this message]
2021-04-29 13:49 ` jakub at gcc dot gnu.org
2021-04-29 17:21 ` brechtsanders at users dot sourceforge.net

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-99401-4-5xSMn3ATAB@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).