public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/99496] [11 regression] g++.dg/modules/xtreme-header-3_c.C ICEs after r11-7557 Date: Wed, 10 Mar 2021 18:18:59 +0000 [thread overview] Message-ID: <bug-99496-4-zrtpswRCDz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99496-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99496 Segher Boessenkool <segher at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |segher at gcc dot gnu.org --- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> --- Just FYI: There are four Power Linux systems in the cfarm (as well as some AIX). gcc110 POWER7 BE gcc203 POWER8 BE gcc112 POWER8 LE gcc135 POWER9 LE The last one is by far the most powerful of these.
next prev parent reply other threads:[~2021-03-10 18:19 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-09 22:39 [Bug other/99496] New: " seurer at gcc dot gnu.org 2021-03-10 8:11 ` [Bug other/99496] " rguenth at gcc dot gnu.org 2021-03-10 17:04 ` nathan at gcc dot gnu.org 2021-03-10 18:18 ` segher at gcc dot gnu.org [this message] 2021-03-10 20:13 ` seurer at gcc dot gnu.org 2021-03-10 21:26 ` nathan at gcc dot gnu.org 2021-03-10 21:33 ` seurer at gcc dot gnu.org 2021-03-10 23:47 ` nathan at gcc dot gnu.org 2021-03-11 18:41 ` nathan at gcc dot gnu.org 2021-03-11 22:46 ` seurer at gcc dot gnu.org 2021-03-11 22:48 ` seurer at gcc dot gnu.org 2021-03-12 17:23 ` nathan at gcc dot gnu.org 2021-03-12 19:59 ` nathan at gcc dot gnu.org 2021-03-15 18:31 ` nathan at gcc dot gnu.org 2021-03-16 0:38 ` segher at gcc dot gnu.org 2021-03-16 11:37 ` cvs-commit at gcc dot gnu.org 2021-03-16 11:38 ` nathan at gcc dot gnu.org 2021-03-30 19:44 ` seurer 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-99496-4-zrtpswRCDz@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).