public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96899] New: [10.2 Regression] [SH] Bootstrap fails when building libgomp
Date: Wed, 02 Sep 2020 12:55:12 +0000 [thread overview]
Message-ID: <bug-96899-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96899
Bug ID: 96899
Summary: [10.2 Regression] [SH] Bootstrap fails when building
libgomp
Product: gcc
Version: 10.2.0
URL: https://buildd.debian.org/status/fetch.php?pkg=gcc-10&
arch=sh4&ver=10.2.0-6&stamp=1598935952&raw=0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: glaubitz at physik dot fu-berlin.de
CC: jrtc27 at jrtc27 dot com, kkojima at rr dot iij4u.or.jp,
oleg.endo@t-online.de
Target Milestone: ---
Target: sh*-*-*
With gcc-10.2, the bootstrap has started to fail on Debian/sh4, please see:
> https://buildd.debian.org/status/fetch.php?pkg=gcc-10&arch=sh4&ver=10.2.0-6&stamp=1598935952&raw=0
It's failing when building libgomp, not sure exactly what the problem is.
I have not yet bisected which commit broke the build. Might do that later.
I cannot copy and paste the partial build log because that triggers the spam
filter and locks my bugzilla account :(.
next reply other threads:[~2020-09-02 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 12:55 glaubitz at physik dot fu-berlin.de [this message]
2020-09-02 14:16 ` [Bug target/96899] " rguenth at gcc dot gnu.org
2020-09-02 14:17 ` [Bug target/96899] [10 " rguenth at gcc dot gnu.org
2020-09-02 14:18 ` glaubitz at physik dot fu-berlin.de
2020-09-03 7:58 ` glaubitz at physik dot fu-berlin.de
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-07-07 9:04 ` rguenth 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-96899-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: 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).