public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/43613] Some architecture-dependent codes
Date: Sun, 18 Feb 2024 07:51:00 +0000	[thread overview]
Message-ID: <bug-43613-4-umNPC0D2aD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43613-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from nightstrike <nightstrike at gmail dot com> ---
Patch thread started here:

https://gcc.gnu.org/pipermail/gcc-patches/2024-February/644674.html
https://inbox.sourceware.org/gcc-patches/4700e066-1b50-4e7b-92f7-d8c33a330bbf@gmail.com/

and ended with this solution:

https://gcc.gnu.org/pipermail/gcc-patches/2024-February/644701.html
https://inbox.sourceware.org/gcc-patches/Zbu34FTR73081bMb@tucnak/


which was committed in r14-8898-g2bb4556220285e.

I believe based on comment 7, this can now be closed.

  parent reply	other threads:[~2024-02-18  7:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-43613-4@http.gcc.gnu.org/bugzilla/>
2021-09-19 10:42 ` pinskia at gcc dot gnu.org
2024-01-16  4:53 ` nightstrike at gmail dot com
2024-01-16  5:06 ` xry111 at gcc dot gnu.org
2024-02-18  7:51 ` nightstrike at gmail dot com [this message]
2024-02-20  4:57 ` aflyhorse at foxmail dot com
2010-04-01  1:02 [Bug target/43613] New: " aflyhorse at foxmail dot com
2010-04-01  1:15 ` [Bug target/43613] " pinskia at gcc dot gnu dot org
2010-04-01  8:23 ` aflyhorse at foxmail dot com
2010-04-01  8:26 ` aflyhorse at foxmail dot com
2010-04-12 10:44 ` aflyhorse at foxmail dot com
2010-04-12 14:12 ` pinskia at gcc dot gnu dot org
2010-04-13 10:58 ` aflyhorse at foxmail 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-43613-4-umNPC0D2aD@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).