public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/108682] libffi needs to merge upstream to get LoongArch support
Date: Fri, 03 Mar 2023 04:16:03 +0000	[thread overview]
Message-ID: <bug-108682-4-D4EUesZ7jv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108682-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Merging libffi is a big change and not suitable for stage 3 IMO.

Can we can apply the LoongArch patch locally instead?  It will not affect other
targets and even if does not work perfectly on LoongArch we don't lose
anything.

  parent reply	other threads:[~2023-03-03  4:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 10:08 [Bug libffi/108682] New: " robinlee.sysu at gmail dot com
2023-03-03  4:14 ` [Bug libffi/108682] " xry111 at gcc dot gnu.org
2023-03-03  4:16 ` xry111 at gcc dot gnu.org [this message]
2023-03-03  7:54 ` xry111 at gcc dot gnu.org
2023-03-03  8:33 ` schwab@linux-m68k.org
2023-03-03  8:45 ` xry111 at gcc dot gnu.org
2023-05-22  6:28 ` xry111 at gcc dot gnu.org
2023-05-22 16:34 ` ian at airs dot com
2023-05-22 16:34 ` ian at airs dot com
2023-05-23  8:17 ` xry111 at gcc dot gnu.org
2023-05-23 16:22 ` ian at airs dot com
2023-05-24  7:40 ` xry111 at gcc dot gnu.org
2023-08-23  6:16 ` cvs-commit at gcc dot gnu.org
2023-08-23 14:12 ` xry111 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-108682-4-D4EUesZ7jv@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).