public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93177] PPC: Missing many useful platform intrinsics
Date: Wed, 26 Oct 2022 16:30:00 +0000	[thread overview]
Message-ID: <bug-93177-4-gsdePrgPUg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93177-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Sergey Fedorov from comment #16)
> For Darwin, PPC intrinsics already is there in Apple headers. Can it be
> added into current GCC?

If it is in the Apple headers already, why would you need a separate copy
in GCC?

Also please note that as said many of those things do not work with current
GCC, and arguably didn't work with older GCC either, the user just got lucky
that the random translation he got did what he wanted :-/  Things like "sync"
or "dcbst" need proper dependencies, things like lwarx are *impossible* to
do, etc.

But thought-out patches are welcome :-)

  parent reply	other threads:[~2022-10-26 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93177-4@http.gcc.gnu.org/bugzilla/>
2022-10-04 22:34 ` pinskia at gcc dot gnu.org
2022-10-26 15:05 ` vital.had at gmail dot com
2022-10-26 15:15 ` iains at gcc dot gnu.org
2022-10-26 16:30 ` segher at gcc dot gnu.org [this message]
2022-10-26 19:17 ` iains at gcc dot gnu.org
2022-10-26 19:27 ` iains at gcc dot gnu.org
2022-10-26 19:32 ` iains at gcc dot gnu.org
2022-10-28 20:52 ` vital.had at gmail 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-93177-4-gsdePrgPUg@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).