lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2009Apr23.222224@mips.complang.tuwien.ac.at>
Date:	Thu, 23 Apr 2009 20:22:24 GMT
From:	anton@...s.complang.tuwien.ac.at (Anton Ertl)
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [rfc] built-in native compiler for Linux?

Ingo Molnar <mingo@...e.hu> writes:
> Furthermore, a lot of optimizations in GCC are driven by 
>SPECint and SPECfp benchmarketing, with little practical relevance 
>to 99% of the apps, including the kernel.

Right, and it's not just the kernel that has to work around GCC
breakage, it's also many apps (possibly all of them except SPEC
benchmarks, and the few 100% C99-compliant programs (probably none
with more than than 500 lines of code)).

So I guess a decent alternative to GCC would attract not just the
kernel people, but also many (most?) applications people.  Then GCC
would no longer be misused for ordinary applications or kernels and it
could focus on its true destiny: compiling SPEC benchmarks.

Whether to build such a compiler mostly from scratch as you suggest or
as a fork of GCC is up to whoever does it.  The GCC fork variant has
the advantage of having a lot of targets available already, but the
disadvantage of a large and complex code base.

- anton
-- 
M. Anton Ertl                    Some things have to be seen to be believed
anton@...s.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ