public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/113575] [14 Regression] memory hog building insn-opinit.o (i686-linux-gnu -> riscv64-linux-gnu)
Date: Mon, 04 Mar 2024 04:13:02 +0000	[thread overview]
Message-ID: <bug-113575-4-26yZIAo9tT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113575-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113575

Jeffrey A. Law <law at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |law at gcc dot gnu.org

--- Comment #16 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Fixed on the trunk.

  parent reply	other threads:[~2024-03-04  4:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  7:59 [Bug other/113575] New: " doko at gcc dot gnu.org
2024-01-24  8:05 ` [Bug other/113575] " pinskia at gcc dot gnu.org
2024-01-24  8:06 ` pinskia at gcc dot gnu.org
2024-01-24  8:08 ` sjames at gcc dot gnu.org
2024-01-24  8:25 ` doko at gcc dot gnu.org
2024-01-24  8:53 ` rdapp at gcc dot gnu.org
2024-01-24  9:00 ` rguenth at gcc dot gnu.org
2024-01-24  9:01 ` rdapp at gcc dot gnu.org
2024-01-24  9:09 ` rguenth at gcc dot gnu.org
2024-01-24  9:43 ` rguenth at gcc dot gnu.org
2024-01-24  9:48 ` rguenth at gcc dot gnu.org
2024-01-24 17:21 ` doko at gcc dot gnu.org
2024-01-24 19:30 ` rdapp at gcc dot gnu.org
2024-01-25 13:08 ` rguenth at gcc dot gnu.org
2024-01-25 14:38 ` rdapp at gcc dot gnu.org
2024-01-26 21:44 ` cvs-commit at gcc dot gnu.org
2024-03-04  4:13 ` law at gcc dot gnu.org [this message]
2024-03-04  4:29 ` law 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-113575-4-26yZIAo9tT@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).