[m-dev.] 32-bit sources on 64-bit target
novalazy at gmail.com
Fri Mar 8 15:58:02 AEDT 2013
On Fri, 8 Mar 2013 15:03:19 +1100, Julien Fischer <jfischer at opturion.com> wrote:
> Hi Peter,
> On Fri, Mar 8, 2013 at 10:51 AM, Peter Wang <novalazy at gmail.com> wrote:
> > On Fri, 8 Mar 2013 00:38:58 +1100, Julien Fischer <jfischer at opturion.com> wrote:
> >> On Fri, Mar 8, 2013 at 12:17 AM, Paul Bone <paul at bone.id.au> wrote:
> >> > On Thu, Mar 07, 2013 at 06:00:24PM +1100, Julien Fischer wrote:
> >> >> On Thu, Mar 7, 2013 at 5:08 PM, Peter Wang <novalazy at gmail.com> wrote:
> >> >> > The compiler built from pre-generated sources WILL be installed.
> >> >> > For now, I can't think of why that would be a problem.
> >> >>
> >> >> It wouldn't be at the moment since the compiler (and other tools)
> >> >> are currently built with --mercury-linkage static. It would be a problem,
> >> >> if that were not the case.
> >> >>
> >> >
> >> > How much of a performance gain does unboxed floats and 3 tag bits represent
> >> > specifically for the compiler?
> > Suprisingly, significant: (default speedtest)
> > mercury_compile.01 average of 6 with ignore=1 10.00
> > mercury_compile.02 average of 6 with ignore=1 12.08
> That's quite a difference. Is mercury_compile.02 built directly from
> the source distribution
> C files.
> Providing 64-bit source distributions isn't really going to reduce the
> complexity of building Mercury from scratch, just shift it around a
More information about the developers