Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while testing #390

Closed
antoscha opened this issue Jun 24, 2020 · 2 comments
Closed

Error while testing #390

antoscha opened this issue Jun 24, 2020 · 2 comments
Assignees
Milestone

Comments

@antoscha
Copy link

I'm not sure if it's related to the project, but I'm getting the following error at make tests:

In file included from matcopy.c:33:
/usr/include/f77blas.h:476:5: error: unknown type name ‘bfloat16’; did you mean ‘_Float16’?
  476 |     bfloat16 *, blasint *, bfloat16 *, blasint *, float *, float *, blasint *);
      |     ^~~~~~~~
      |     _Float16
/usr/include/f77blas.h:476:28: error: unknown type name ‘bfloat16’; did you mean ‘_Float16’?
  476 |     bfloat16 *, blasint *, bfloat16 *, blasint *, float *, float *, blasint *);
      |                            ^~~~~~~~
      |                            _Float16
make[1]: *** [Makefile:138: obj/matcopy-c.o] Error 1
@hfp hfp self-assigned this Jun 24, 2020
@hfp
Copy link
Collaborator

hfp commented Jun 24, 2020

I have investigate this and it looks like "bfloat16" is not defined in any of the headers of OpenBLAS. It is defined in the source tree, but not in the interface.

[openblas/include]$ grep bfloat *
f77blas.h:         bfloat16 *, blasint *, bfloat16 *, blasint *, float *, float *, blasint *);

So none of the files in that directory define that type and non of the includes contain such definition. The interface is either incomplete or assuming a compiler with a built-in type called "bfloat16".

hfp added a commit that referenced this issue Jun 24, 2020
@hfp hfp added this to the 1.16.1 milestone Jun 26, 2020
@hfp
Copy link
Collaborator

hfp commented Jun 26, 2020

The issue with OpenBLAS should be avoided in v1.16.1; feel free to reopen/create another issue if you encounter a problem. Thank you very much for your contribution and report!

@hfp hfp closed this as completed Jun 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants