public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107155] ppc_intrinsics is missing
Date: Wed, 05 Oct 2022 10:22:00 +0000	[thread overview]
Message-ID: <bug-107155-4-OA8n1zLqEV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107155-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
The discussion in the duplicate issue revolves around whether the header in the
sources was suitable (i.e. for something != cell).

The Apple header (which presumably does not have these contraints, since it was
deployed with Apple GCC-4.x) was committed to the Apple branch on the FSF
server.

my understanding of the rules (we have used this policy before) is that any
sources actually committed to an FSF server are considered to be contributed -
so that we could forward-port that header.

It's a question of finding some time to fish it out and adjust the install to
add it and test .. (I have other GCC items much higher on the TODO).

      parent reply	other threads:[~2022-10-05 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 22:26 [Bug target/107155] New: " vital.had at gmail dot com
2022-10-04 22:34 ` [Bug target/107155] " pinskia at gcc dot gnu.org
2022-10-04 22:35 ` pinskia at gcc dot gnu.org
2022-10-05 10:22 ` iains at gcc dot gnu.org [this message]

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-107155-4-OA8n1zLqEV@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).