Date: Thu, 15 Jan 2009 16:01:37 +0300 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: Roman Divacky <rdivacky@freebsd.org> Cc: Pegasus Mc Cleaft <ken@mthelicon.com>, FuLLBLaSTstorm <fullblaststorm@gmail.com>, freebsd-current@freebsd.org Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standardcompiler?) Message-ID: <f0UcTFwaZMH9mCkc5RJuLDoBmtA@HEwlnNW4tuDdZ1V6ihYwW3pQ/cw> In-Reply-To: <20090115122805.GA48561@freebsd.org> References: <496F0D1D.7080505@andric.com> <6c51dbb10901150344s409cd834p3cd8fae189e42a68@mail.gmail.com> <9225949D37F24E01AA5FC01169A256F2@PegaPegII> <20090115122805.GA48561@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thu, Jan 15, 2009 at 01:28:05PM +0100, Roman Divacky wrote:
> 2) llvm uses special "bytecode" that gets compiled into native machine
> code so technically speaking "classic" assembler is not needed for llvm/clang.
Hmm, what about assembly statements inside C sources or pure assembler
sources? May be my definition of a "classic" differs from yours, but
for we need assembler at least for the .S files. Do you mean that some
supplementary assembler should be added to the llvm/clang suite?
--
Eygene
_ ___ _.--. #
\`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard
/ ' ` , __.--' # to read the on-line manual
)/' _/ \ `-_, / # while single-stepping the kernel.
`-'" `"\_ ,_.-;_.-\_ ', fsc/as #
_.-'_./ {_.' ; / # -- FreeBSD Developers handbook
{_.-``-' {_/ #
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f0UcTFwaZMH9mCkc5RJuLDoBmtA>