public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alexander.lelyakin at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99227] [meta] [modules] Bugs relating to header-units of STL header files Date: Tue, 30 Mar 2021 07:33:56 +0000 [thread overview] Message-ID: <bug-99227-4-RhqSkS2Uw3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99227-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99227 --- Comment #2 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> --- I have started some script that continuously do following: git pull configure make make install do 5000 attempts to compile system headers in random order upload the results of the attempts to http://lelyakin.de/modules They are sorted by error message and by count of successfully compiled headers. Results are updated approximately every 7-8 hours. Currently reproducible are the following errors: 99737 - Aborted 99479 - Aborted signal terminated program cc1plus 99722 - Segmentation fault 99426 - failed to read compiled module cluster 99283 - in assert_definition 99241 - in install_entity 99284 - in key_mergeable 99242 - in lookup_mark 99243 - in set_filename 99244 - in tsubst_copy 99246 - in write_location 99427 - non-constant condition for static assertion 99760 - qsort checking failed 99274 - wrong number of template arguments (1, should be 2
next prev parent reply other threads:[~2021-03-30 7:33 UTC|newest] Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-23 18:34 [Bug c++/99227] New: " nathan at gcc dot gnu.org 2021-02-26 12:49 ` [Bug c++/99227] " nathan at gcc dot gnu.org 2021-02-26 12:49 ` nathan at gcc dot gnu.org 2021-03-05 18:19 ` nathan at gcc dot gnu.org 2021-03-05 20:54 ` nathan at gcc dot gnu.org 2021-03-06 10:08 ` alexander.lelyakin at googlemail dot com 2021-03-08 18:09 ` nathan at gcc dot gnu.org 2021-03-10 20:12 ` nathan at gcc dot gnu.org 2021-03-11 21:13 ` nathan at gcc dot gnu.org 2021-03-12 13:10 ` nathan at gcc dot gnu.org 2021-03-12 18:23 ` nathan at gcc dot gnu.org 2021-03-13 7:02 ` alexander.lelyakin at googlemail dot com 2021-03-15 12:42 ` nathan at gcc dot gnu.org 2021-03-15 12:43 ` nathan at gcc dot gnu.org 2021-03-22 15:27 ` nathan at gcc dot gnu.org 2021-03-22 19:42 ` nathan at gcc dot gnu.org 2021-03-23 11:37 ` nathan at gcc dot gnu.org 2021-03-23 12:22 ` nathan at gcc dot gnu.org 2021-03-30 1:22 ` mpolacek at gcc dot gnu.org 2021-03-30 1:26 ` mpolacek at gcc dot gnu.org 2021-03-30 1:27 ` mpolacek at gcc dot gnu.org 2021-03-30 1:35 ` mpolacek at gcc dot gnu.org 2021-03-30 7:33 ` alexander.lelyakin at googlemail dot com [this message] 2021-03-30 20:36 ` mpolacek at gcc dot gnu.org 2021-03-31 13:35 ` mpolacek at gcc dot gnu.org 2021-03-31 13:36 ` mpolacek at gcc dot gnu.org 2021-04-02 16:09 ` nathan at gcc dot gnu.org 2021-04-07 6:27 ` alexander.lelyakin at googlemail dot com 2021-04-07 6:27 ` alexander.lelyakin at googlemail dot com 2021-04-07 6:29 ` alexander.lelyakin at googlemail dot com 2021-04-17 13:59 ` alexander.lelyakin at googlemail dot com 2021-09-28 14:37 ` johelegp at gmail dot com 2021-12-29 23:04 ` pinskia at gcc dot gnu.org 2021-12-30 16:09 ` pinskia at gcc dot gnu.org 2021-12-30 16:10 ` pinskia at gcc dot gnu.org 2021-12-30 16:12 ` pinskia at gcc dot gnu.org 2021-12-30 16:12 ` pinskia at gcc dot gnu.org 2022-01-01 4:17 ` pinskia at gcc dot gnu.org 2022-02-13 14:03 ` johelegp at gmail dot com 2022-02-17 15:08 ` dominiq at lps dot ens.fr 2022-09-29 20:28 ` ppalka at gcc dot gnu.org 2022-09-29 21:07 ` ppalka at gcc dot gnu.org 2022-10-12 11:32 ` redi at gcc dot gnu.org 2022-10-12 19:13 ` ppalka at gcc dot gnu.org 2022-10-25 17:48 ` ppalka at gcc dot gnu.org 2024-03-06 16:47 ` ppalka at gcc dot gnu.org 2024-03-06 16:49 ` ppalka at gcc dot gnu.org 2024-03-07 19:56 ` ppalka at gcc dot gnu.org 2024-04-12 19:53 ` ppalka 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-99227-4-RhqSkS2Uw3@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: linkBe 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).