From: Segher Boessenkool <segher@kernel.crashing.org>
To: Richard Biener <rguenther@suse.de>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: GCC 8.0.0 Status Report (2018-01-15), Trunk in Regression and Documentation fixes only mode
Date: Tue, 16 Jan 2018 12:50:00 -0000 [thread overview]
Message-ID: <20180116125007.GR21977@gate.crashing.org> (raw)
In-Reply-To: <alpine.LSU.2.20.1801150920260.32271@zhemvz.fhfr.qr>
On Mon, Jan 15, 2018 at 09:21:07AM +0100, Richard Biener wrote:
> We're still in pretty bad shape regression-wise. Please also take
> the opportunity to check the state of your favorite host/target
> combination to make sure building and testing works appropriately.
I tested building Linux (the kernel) for all supported architectures.
Everything builds (with my usual tweaks, link with libgcc etc.);
except x86_64 and sh have more problems in the kernel, and mips has
an ICE. I'll open a PR for that one.
Segher
next prev parent reply other threads:[~2018-01-16 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 8:21 Richard Biener
2018-01-16 12:50 ` Segher Boessenkool [this message]
2018-01-16 17:11 ` Joseph Myers
2018-01-17 17:56 ` Segher Boessenkool
2018-01-16 19:20 ` Andrew Roberts
2018-01-17 8:20 ` Richard Biener
2018-01-26 14:22 ` Rainer Orth
2018-01-26 18:56 ` Andrew Roberts
2018-01-27 14:38 ` Rainer Orth
2018-02-06 9:22 ` Rainer Orth
2018-02-06 9:49 ` Matthias Klose
2018-02-06 16:14 ` Vincent Lefevre
2018-02-06 16:28 ` Vincent Lefevre
2018-02-06 17:34 ` Joseph Myers
2018-02-06 21:59 ` Vincent Lefevre
2018-02-06 17:32 ` Joseph Myers
2018-02-06 21:48 ` Vincent Lefevre
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=20180116125007.GR21977@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).