#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:37 vbraun]:
 > Imho it depends on whether the compiler or the source is at fault. In
 the case of Singular I don't think its a compiler bug. So it most likely
 won't go away with gcc 7...

 Well, it goes away with GCC < 6.x, and we shouldn't throw arbitrary
 options at `$CXX`, which might -- for example -- be `clang`.  (Most parts
 of Sage did build with the latter, at least a while ago.  `clang` accepts
 a couple of GCC options, but spits out warnings for others it doesn't, and
 I wouldn't rely on the latter, i.e. wouldn't risk breaking something which
 previously worked, for no reason.)

--
Ticket URL: <https://trac.sagemath.org/ticket/20926#comment:38>
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.

Reply via email to