public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/54179] please split insn-emit.c !
Date: Fri, 07 Jul 2023 11:29:03 +0000	[thread overview]
Message-ID: <bug-54179-4-rQDDZqTFGX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54179-4@http.gcc.gnu.org/bugzilla/>

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

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WONTFIX                     |---
             Status|RESOLVED                    |UNCONFIRMED
                 CC|                            |tnfchris at gcc dot gnu.org

--- Comment #32 from Sam James <sjames at gcc dot gnu.org> ---
I'll tentatively reopen as IIRC tamar mentioned they've had some ideas about
this, apologies if I'm misremembering.

  parent reply	other threads:[~2023-07-07 11:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05 11:05 [Bug c/54179] New: " jason.vas.dias at gmail dot com
2012-08-05 11:11 ` [Bug c/54179] " jason.vas.dias at gmail dot com
2012-08-05 11:22 ` wbrana at gmail dot com
2012-08-05 11:36 ` jason.vas.dias at gmail dot com
2012-08-05 11:43 ` jason.vas.dias at gmail dot com
2012-08-05 12:01 ` wbrana at gmail dot com
2012-08-05 12:04 ` steven at gcc dot gnu.org
2012-08-05 12:21 ` jason.vas.dias at gmail dot com
2012-08-05 12:28 ` wbrana at gmail dot com
2012-08-05 12:34 ` steven at gcc dot gnu.org
2012-08-05 12:37 ` steven at gcc dot gnu.org
2012-08-05 13:16 ` jason.vas.dias at gmail dot com
2012-08-05 13:31 ` wbrana at gmail dot com
2012-08-05 13:43 ` jason.vas.dias at gmail dot com
2012-08-05 13:46 ` jason.vas.dias at gmail dot com
2012-08-05 13:51 ` jason.vas.dias at gmail dot com
2012-08-05 13:54 ` steven at gcc dot gnu.org
2012-08-05 13:55 ` steven at gcc dot gnu.org
2012-08-05 14:12 ` wbrana at gmail dot com
2012-08-05 14:13 ` schwab@linux-m68k.org
2012-08-05 18:10 ` jason.vas.dias at gmail dot com
2012-08-05 18:39 ` steven at gcc dot gnu.org
2012-08-05 19:49 ` jason.vas.dias at gmail dot com
2012-08-05 19:52 ` jason.vas.dias at gmail dot com
2012-08-05 20:10 ` jason.vas.dias at gmail dot com
2012-08-05 20:17 ` steven at gcc dot gnu.org
2012-08-05 20:58 ` jason.vas.dias at gmail dot com
2012-08-05 21:05 ` steven at gcc dot gnu.org
2012-08-06  8:43 ` rguenth at gcc dot gnu.org
2012-08-06  9:11 ` steven at gcc dot gnu.org
2012-08-06 10:49 ` steven at gcc dot gnu.org
2023-07-06 10:49 ` mmokrejs at gmail dot com
2023-07-07 11:29 ` sjames at gcc dot gnu.org [this message]
2023-07-07 11:39 ` [Bug bootstrap/54179] " tnfchris at gcc dot gnu.org
2023-07-07 12:47 ` mmokrejs at gmail dot com
2023-10-31 12:48 ` sjames at gcc dot gnu.org
2023-11-13 13:07 ` brjd_epdjq36 at kygur dot com
2023-11-13 15:03 ` xry111 at gcc dot gnu.org
2023-11-13 15:12 ` brjd_epdjq36 at kygur dot com
2024-05-11 12:08 ` brjd_epdjq36 at kygur dot com
2024-05-12  4:29 ` sjames at gcc dot gnu.org
2024-05-12 10:19 ` brjd_epdjq36 at kygur dot com

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-54179-4-rQDDZqTFGX@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).