#20926: C++11 workarounds
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-7.3
Component: packages: | Resolution:
standard |
Keywords: gcc6 c++11 c++14 | Merged in:
Authors: Volker Braun | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/c__11_workarounds | 86e6a4b21cb4a51c2aa9ed8d01b62239b8fdbd13
Dependencies: #20927 #20741 | Stopgaps:
#20738 |
-------------------------------------+-------------------------------------
Comment (by leif):
Replying to [comment:31 vbraun]:
> There is probably a bug in the Brial code path, this should be fixed on
the C++ level. But in another ticket.
Does this refer to the three segfaults / aborts in ptestlong you reported
[comment:27 above]? How did you get these?
\\
With Sage 7.3.beta7 (plus the branch here) and vanilla FSF GCC 6.1.0, GCC
configured to produce native code by default, but otherwise no `*FLAGS`
set, ptestlong passes for me (modulo the usual failure in one test due to
numeric noise and another GAP-related which nearly always fails in the
first place, but passes when rerun) on Linux x86_64 (Haswell-E).
--
Ticket URL: <https://trac.sagemath.org/ticket/20926#comment:34>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
