public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexander.grund@tu-dresden.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100703] New: __vector_pair and __vector_quad cannot be passed by reference
Date: Thu, 20 May 2021 11:17:16 +0000	[thread overview]
Message-ID: <bug-100703-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100703
           Summary: __vector_pair and __vector_quad cannot be passed by
                    reference
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: alexander.grund@tu-dresden.de
  Target Milestone: ---

The PowerPC intrinsic types __vector_pair and __vector_quad cannot be passed by
reference but only by pointer.

Reproducer code:

void ploadRhsMMA(__vector_pair&){}
int main(){
  __vector_pair p;
  ploadRhsMMA(p);
}

This creates an error "invalid conversion from type »* __vector_pair«"

This error looks wrong to me: Why wouldn't I be able to pass a type by
reference when I can pass it by pointer? GCC can handle both the same so it is
at least inconsistent.

Furthermore this breaks the commonly used assumption, that the following
functions can take any argument:

template<typename T>
void foo(T&&);
template<typename T>
void bar(const T&);

This now breaks for those intrinsics and a workaround is painful as everything
needs to be covnerted to pointers when those are part of an overload set (for
example)

             reply	other threads:[~2021-05-20 11:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 11:17 alexander.grund@tu-dresden.de [this message]
2021-05-20 13:05 ` [Bug target/100703] " alexander.grund@tu-dresden.de
2021-06-03  0:05 ` segher at gcc dot gnu.org
2021-06-03  7:01 ` alexander.grund@tu-dresden.de
2021-06-03 13:15 ` wschmidt 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-100703-4@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).