Changes between Initial Version and Version 22 of Ticket #10252


Ignore:
Timestamp:
11/24/10 02:16:54 (10 years ago)
Author:
leif
Comment:

Replying to leif:

Just for the record: I'll upload a new spkg that also fixes this issue at #5847 (hopefully) soon...

Did so...

Setting this ticket to "needs review" too, can be closed as duplicate when #5847 gets a positive review / merged.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10252

    • Property Cc zimmerma dimpase leif mhansen added
    • Property Priority changed from blocker to major
    • Property Status changed from new to needs_review
    • Property Report Upstream changed from N/A to Fixed upstream, but not in a stable release.
  • Ticket #10252 – Description

    initial v22  
    3434
    3535This is probably because Sage's CFLAGS overrides ecm's CFLAGS.  I think the easiest solution is simply not set any CFLAGS in ecm's {{{spkg-install}}}.  Since ecm really wants to optimize for a particular machine, I think the fact that ecm's CFLAGS are not used has also bad consequences for speed.
     36
     37----
     38
     39Actually an upstream bug... (And not setting `CFLAGS` or `CC` is not an option. There are different ways to let the compiler produce processor-specific optimized code. Note that this anyway doesn't affect optimized assembly code, which ECM also comes with.)
     40
     41'''New spkg (ecm-6.3.p2) fixing this''' (including the upstream patch) '''at #5847.'''