[OT] LLVM Community Code of Conduct
Vladimir Panteleev via Digitalmars-d
digitalmars-d at puremagic.com
Mon Oct 19 13:47:53 PDT 2015
On Sunday, 18 October 2015 at 07:56:02 UTC, Iain Buclaw wrote:
> On 18 Oct 2015 9:45 am, "Vladimir Panteleev via Digitalmars-d"
> < digitalmars-d at puremagic.com> wrote:
>>
>> On Sunday, 18 October 2015 at 07:37:55 UTC, Iain Buclaw wrote:
>>>
>>> Essentially, the reason D has not been ported to X has
>>> nothing to do
> with lack of compiler support. A compiler can always be built
> to target X, and if that wasn't enough, there are many ready
> built packages available that target X.
>>>
>>> It is now your job as porters to fix up druntime to allow a
>>> library to
> be built by these compilers.
>>
>>
>> That's not very useful. LDC and GDC still include Phobos and
>> Druntime.
>>
>
> It is infinitely more useful than having no compiler at all to
> test porting changes.
That's not what I meant. Aside from the compiler, LDC and GDC
include the runtime, standard library, probably documentation
etc. They come as a complete package.
>> You're essentially saying that once LDC gets Android/iOS
>> support, GDC
> will automatically get it as well with no effort required from
> you?
>>
>
> In it's runtime? Correct - assuming no one invents any new
> predefined version conditions in the process. :-)
No, not just the runtime. Surely the runtime contains some
compiler/linker/toolchain-specific things... intrinsics, linker
scripts, section names, predefined versions, assembler syntax...
some of these might be platform/architecture-independent but
surely not all?
More information about the Digitalmars-d
mailing list