On 2013-02-24 03:04, Adrian Chadd wrote:
Just curious about the OS detection - is the default platform
detection based on the currently running OS, or the cross-built target
OS?
eg, if I were cross-compiling FreeBSD on (say) haiku, which has
different CPU defaults, what would the default CPU out
Just curious about the OS detection - is the default platform
detection based on the currently running OS, or the cross-built target
OS?
eg, if I were cross-compiling FreeBSD on (say) haiku, which has
different CPU defaults, what would the default CPU output be?
Adrian
_
On 2013-02-23 21:18, Konstantin Belousov wrote:
...
Let me rephrase my question.
What is the processor targeted by the cc on i386, when no -march flag is
specified, for cc coming from clang, for both .c and .s files. Lets ignore
known bugs, like long nops or cmovs.
For i386 arch on FreeBSD, th
On Sat, Feb 23, 2013 at 12:58:14PM +0100, Dimitry Andric wrote:
> On 2013-02-23 00:53, Konstantin Belousov wrote:
> > On Fri, Feb 22, 2013 at 10:40:10PM +, Dimitry Andric wrote:
> ...
> >>This should fix the long nops that still occurred in crt*.o, and
> >>possibly other object files, i
On 2013-02-23 00:53, Konstantin Belousov wrote:
On Fri, Feb 22, 2013 at 10:40:10PM +, Dimitry Andric wrote:
...
This should fix the long nops that still occurred in crt*.o, and
possibly other object files, if the system was compiled for a CPU that
does not support those, such as Ge
On Fri, Feb 22, 2013 at 10:40:10PM +, Dimitry Andric wrote:
> Author: dim
> Date: Fri Feb 22 22:40:10 2013
> New Revision: 247166
> URL: http://svnweb.freebsd.org/changeset/base/247166
>
> Log:
> Pull in r172354 from upstream clang trunk:
>
> Refactor the x86 CPU name logic in the dri
Author: dim
Date: Fri Feb 22 22:40:10 2013
New Revision: 247166
URL: http://svnweb.freebsd.org/changeset/base/247166
Log:
Pull in r172354 from upstream clang trunk:
Refactor the x86 CPU name logic in the driver and pass -march and -mcpu
flag information down from the Clang driver into
