public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/99857] New: [11 Regression] FAIL: libgomp.c/declare-variant-1.c (test for excess errors) by r11-7926 Date: Wed, 31 Mar 2021 20:58:38 +0000 [thread overview] Message-ID: <bug-99857-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99857 Bug ID: 99857 Summary: [11 Regression] FAIL: libgomp.c/declare-variant-1.c (test for excess errors) by r11-7926 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: hjl.tools at gmail dot com CC: jh at suse dot cz Target Milestone: --- r11-7926 caused: lto1: fatal error: bytecode stream: trying to read 0 bytes after the end of the input buffer^M compilation terminated.^M lto-wrapper: fatal error: /export/users/hjl/build/gnu/tools-build/gcc-32bit-gitlab-native/build-i686-linux/./gcc/xgcc returned 1 exit status^M compilation terminated.^M /usr/local32/bin/ld: error: lto-wrapper failed^M collect2: error: ld returned 1 exit status^M See ":er exited with status 1. FAIL: libgomp.c/declare-variant-1.c (test for excess errors)fter the end of the Excess errors:
next reply other threads:[~2021-03-31 20:58 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 20:58 hjl.tools at gmail dot com [this message] 2021-04-01 4:43 ` [Bug middle-end/99857] " marxin at gcc dot gnu.org 2021-04-01 12:22 ` hjl.tools at gmail dot com 2021-04-06 12:19 ` tschwinge at gcc dot gnu.org 2021-04-06 13:33 ` hubicka at ucw dot cz 2021-04-08 3:01 ` asolokha at gmx dot com 2021-04-08 14:25 ` rguenth at gcc dot gnu.org 2021-04-08 14:35 ` jakub at gcc dot gnu.org 2021-04-09 12:45 ` hubicka at gcc dot gnu.org 2021-04-09 13:03 ` jakub at gcc dot gnu.org 2021-04-10 9:18 ` cvs-commit at gcc dot gnu.org 2021-04-10 10:52 ` jakub 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-99857-4@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).