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/103306] [12 Regression] parallel build hangs since r12-5234-g04c5a9 when /usr/include includes broken symbolic links
Date: Thu, 18 Nov 2021 10:39:08 +0000	[thread overview]
Message-ID: <bug-103306-4-QswDtpOejt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103306-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
No matter what, IMO assertions or aborts should be for bugs in the tool
(fixincl in this case), something that shouldn't happen if the tool doesn't
have bugs, while errors or possibly ignored errors should be for the case where
the bug is outside of the tool like in this case.  And, for a tool like
fixincl, the big question is if it should be a fatal error or just warning or
non-fatal error, something the tool can survive and continue with next header.

  parent reply	other threads:[~2021-11-18 10:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 19:14 [Bug bootstrap/103306] New: parallel build hangs since 04c5a91d068c4ca2f09c2bc206fce00db9d1790b zsojka at seznam dot cz
2021-11-17 20:18 ` [Bug bootstrap/103306] parallel build hangs since r12-5234-g04c5a91d068c4ca2f09c2bc206fce00db9d1790b pinskia at gcc dot gnu.org
2021-11-17 20:22 ` pinskia at gcc dot gnu.org
2021-11-17 21:14 ` zsojka at seznam dot cz
2021-11-17 23:06 ` pinskia at gcc dot gnu.org
2021-11-18  6:36 ` zsojka at seznam dot cz
2021-11-18  7:49 ` zsojka at seznam dot cz
2021-11-18  7:53 ` rguenth at gcc dot gnu.org
2021-11-18  7:57 ` jakub at gcc dot gnu.org
2021-11-18  8:01 ` pinskia at gcc dot gnu.org
2021-11-18  8:03 ` zsojka at seznam dot cz
2021-11-18  8:07 ` pinskia at gcc dot gnu.org
2021-11-18  8:07 ` [Bug bootstrap/103306] [12 Regression] parallel build hangs since r12-5234-g04c5a9 when /usr/include includes broken symbolic links pinskia at gcc dot gnu.org
2021-11-18  8:10 ` zsojka at seznam dot cz
2021-11-18 10:22 ` xry111 at mengyan1223 dot wang
2021-11-18 10:23 ` zsojka at seznam dot cz
2021-11-18 10:39 ` jakub at gcc dot gnu.org [this message]
2021-11-18 11:02 ` xry111 at mengyan1223 dot wang
2021-11-19  4:56 ` zsojka at seznam dot cz
2021-11-20 13:18 ` xry111 at mengyan1223 dot wang
2021-11-23 19:20 ` cvs-commit at gcc dot gnu.org
2021-11-23 19:21 ` xry111 at mengyan1223 dot wang
2021-11-28  1:27 ` pinskia at gcc dot gnu.org

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-103306-4-QswDtpOejt@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).