public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chip.kerchner at ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109501] vec_test_data_class defines missing
Date: Thu, 13 Apr 2023 13:47:57 +0000	[thread overview]
Message-ID: <bug-109501-4-bWsWp8Rkmt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109501-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Chip Kerchner <chip.kerchner at ibm dot com> ---
Here's a testcase

```
#include <altivec.h>
#include <stdio.h>

int main()
{
  __vector float p4f = { float(0), float(1), float(2), float(3) };
  __vector __bool int nan_selector = vec_test_data_class(p4f,
__VEC_CLASS_FP_NAN);

  return 0;
}
```

```
NAN_defines.cpp: In function ‘int main()’:
NAN_defines.cpp:7:63: error: ‘__VEC_CLASS_FP_NAN’ was not declared in this
scope
    7 |   __vector __bool int nan_selector = vec_test_data_class(p4f,
__VEC_CLASS_FP_NAN);
      |                                                              
^~~~~~~~~~~~~~~~~~
```

```
/opt/gcc-nightly/trunk/bin/g++ -O3 -mcpu=power9 NAN_defines.cpp

  parent reply	other threads:[~2023-04-13 13:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 13:30 [Bug c++/109501] New: " chip.kerchner at ibm dot com
2023-04-13 13:33 ` [Bug c++/109501] " chip.kerchner at ibm dot com
2023-04-13 13:34 ` chip.kerchner at ibm dot com
2023-04-13 13:37 ` [Bug target/109501] " pinskia at gcc dot gnu.org
2023-04-13 13:39 ` chip.kerchner at ibm dot com
2023-04-13 13:47 ` chip.kerchner at ibm dot com [this message]
2023-04-13 14:18 ` segher at gcc dot gnu.org
2023-04-13 14:21 ` segher at gcc dot gnu.org
2023-04-13 14:30 ` chip.kerchner at ibm dot com
2023-04-13 16:06 ` [Bug target/109501] rs6000: Add suggested defines for vec_test_data_class segher 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-109501-4-bWsWp8Rkmt@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).