POV-Ray : Newsgroups : povray.programming : Making POVRAY "interface less" and "language agnostic"? : Re: Making POVRAY "interface less" and "language agnostic"? Server Time
26 Apr 2024 13:20:06 EDT (-0400)
  Re: Making POVRAY "interface less" and "language agnostic"?  
From: clipka
Date: 22 Dec 2012 12:02:18
Message: <50d5e79a@news.povray.org>
Am 22.12.2012 15:42, schrieb denis.beurive:

> The problem comes from the flag "-march", in the file "configure"?
>
> On MAC :
>
> -march=name
> This specifies the name of the target ARM architecture.  GCC uses this name to
> determine
> what kind of instructions it can emit when generating assembly code.  This
> option can be
> used in conjunction with or instead of the -mcpu= option.  Permissible names
> are: armv2,
> armv2a, armv3, armv3m, armv4, armv4t, armv5, armv5t, armv5te, armv6, armv6j,
> iwmmxt, ep9312.

The GCC documentation contains multiple hardware-specific sections, many 
of which have their own subsection on the "-march" flag. The one you 
quoted is for the ARM architecture; in the section on Intel 386 and AMD 
x86-64 you'll find something like:

------------------------------
-march=cpu-type
Generate instructions for the machine type cpu-type. The choices for 
cpu-type
are the same as for -mtune. Moreover, specifying -march=cpu-type implies
-mtune=cpu-type.
------------------------------

Best choice in your case should be "-march=native".


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.