public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/100703] New: __vector_pair and __vector_quad cannot be passed by reference
@ 2021-05-20 11:17 alexander.grund@tu-dresden.de
  2021-05-20 13:05 ` [Bug target/100703] " alexander.grund@tu-dresden.de
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: alexander.grund@tu-dresden.de @ 2021-05-20 11:17 UTC (permalink / raw)
  To: gcc-bugs

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)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug target/100703] __vector_pair and __vector_quad cannot be passed by reference
  2021-05-20 11:17 [Bug c++/100703] New: __vector_pair and __vector_quad cannot be passed by reference alexander.grund@tu-dresden.de
@ 2021-05-20 13:05 ` alexander.grund@tu-dresden.de
  2021-06-03  0:05 ` segher at gcc dot gnu.org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: alexander.grund@tu-dresden.de @ 2021-05-20 13:05 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Alexander Grund <alexander.grund@tu-dresden.de> ---
It goes further: Even the usual conversion rules for pointer types don't apply:

void foo(__vector_pair*){}
void bar(const __vector_pair*){}
int main(){
  __vector_pair p;
  foo(p); // works
  bar(p); // fails
}

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug target/100703] __vector_pair and __vector_quad cannot be passed by reference
  2021-05-20 11:17 [Bug c++/100703] New: __vector_pair and __vector_quad cannot be passed by reference alexander.grund@tu-dresden.de
  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
  3 siblings, 0 replies; 5+ messages in thread
From: segher at gcc dot gnu.org @ 2021-06-03  0:05 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
This compiles just fine for me, even with -O0.  Does this only happen with
some older version of the compiler?  Are some special flags needed?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug target/100703] __vector_pair and __vector_quad cannot be passed by reference
  2021-05-20 11:17 [Bug c++/100703] New: __vector_pair and __vector_quad cannot be passed by reference alexander.grund@tu-dresden.de
  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
  3 siblings, 0 replies; 5+ messages in thread
From: alexander.grund@tu-dresden.de @ 2021-06-03  7:01 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from Alexander Grund <alexander.grund@tu-dresden.de> ---
I found that this was fixed in 10.3 and 11.1 by
https://github.com/gcc-mirror/gcc/commit/e2882e76089cecdc268d0835c54cabfa80b5b0be

So yes only happens in 10.2. Thanks for checking that!

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug target/100703] __vector_pair and __vector_quad cannot be passed by reference
  2021-05-20 11:17 [Bug c++/100703] New: __vector_pair and __vector_quad cannot be passed by reference alexander.grund@tu-dresden.de
                   ` (2 preceding siblings ...)
  2021-06-03  7:01 ` alexander.grund@tu-dresden.de
@ 2021-06-03 13:15 ` wschmidt at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: wschmidt at gcc dot gnu.org @ 2021-06-03 13:15 UTC (permalink / raw)
  To: gcc-bugs

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

Bill Schmidt <wschmidt at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #4 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
So, already fixed.  Closing.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-06-03 13:15 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-20 11:17 [Bug c++/100703] New: __vector_pair and __vector_quad cannot be passed by reference alexander.grund@tu-dresden.de
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

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).