8000 ambiguity between _m128 and _m256 back again · Issue #358 · linbox-team/fflas-ffpack · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

ambiguity between _m128 and _m256 back again #358

New issue

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

Sign up for GitHub

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

Jump to bottom
Closed
ClementPernet opened this issue Dec 17, 2021 · 2 comments
Closed

ambiguity between _m128 and _m256 back again #358

ClementPernet opened this issue Dec 17, 2021 · 2 comments

Comments

@ClementPernet
Copy link
Member

https://github.com/linbox-team/fflas-ffpack/runs/4550785824?check_suite_focus=true#step:11:1632

raises an ambiguity between _m128 and _m256 register types
and the compiler suggests that -fabi-version=6 should fix it.

We already went down this way and #305 removed the use of this option for any gcc>=v5.
Remark that in this log, the compiler is marked as unknown.
(see https://github.com/linbox-team/fflas-ffpack/runs/4550785824?check_suite_focus=true#step:11:1499
I am not sure what's going on here, but the problem appears on many other builds, e.g. https://github.com/linbox-team/fflas-ffpack/runs/4550786736?check_suite_focus=true#step:11:3331
@cyrilbouvier
Copy link
Member
cyrilbouvier commented Dec 17, 2021 •
edited
Loading

In this case, https://github.com/linbox-team/fflas-ffpack/runs/4550785824?check_suite_focus=true#step:11:1632, the code runs on Ubuntu Trusty (14.04) which have gcc 4.8 as default compiler (according to https://launchpad.net/ubuntu/trusty/+package/gcc).
gcc < 5 is not supported anymore, the message in configure regarding 'unknown compiler' should be an error.

Edit: Same for https://github.com/linbox-team/fflas-ffpack/runs/4550786736?check_suite_focus=true#step:11:3331: it is a debian Jessie machine, which has gcc 4.9 by default (https://wiki.debian.org/DebianJessie)

@ClementPernet
Copy link
Member Author

Ok, thanks, I thought it was more subtle than that. For the record, I removed debain-jessie, ubuntu-trusty, linuxmint-17 and centos-7 from the list of target systems in 74a8226.
I guess we still need to have a cleaner behavior when gcc<5 is detected at configure time: exit error instead of printing a message and silently continuing the configuration.

@ClementPernet ClementPernet mentioned this issue Dec 23, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ClementPernet @cyrilbouvier
0