Ticket #97 (new defect)

Opened 2 months ago

Last modified 12 hours ago

compiling for another target than the host platform is broken

Reported by:	lindquist	Assigned to:
Priority:	minor	Milestone:	Beta
Version:		Keywords:
Cc:

Description

right now we hardcode the target triple, i686-pc-linux-gnu etc.

this is fine for now since everybody using llvmdc match those triples, however it's wrong. the whole thing is part of autoconf and the config.guess script (for example) can be used to get you own.

we somehow need to get these into llvmdc when compiling it, this will affect cross compilation stuff etc, which should probably be rethought.

we might want to remove the -t/-m switches for selecting target os/cpu and somehow make this stuff part of the premake configuration. cross compilation is valuable but it should work correctly...

Change History

10/14/08 14:04:15 changed by ChristianK

isn't this fixed now?

10/17/08 06:28:01 changed by lindquist

for the host system part it is, but we need some way to add in a cross compilation target as well, or remove the -m and -t switches.

10/22/08 11:53:57 changed by lindquist

milestone deleted.

It might be nicer to parse the information out of the target triple, then have users provide just that. We could use the same code in mars.c to determine the default target.

10/28/08 13:07:42 changed by lindquist

milestone set to Beta.

the llvm targets parse the target triple when determining if they fit a module, we should just use the same parsing rules. this is an easy way to add cross compilation support in LDC, at least for the codegen part. assembling/linking is probably another issue...

12/01/08 11:31:41 changed by lindquist

priority changed from major to minor.

12/01/08 11:32:43 changed by lindquist

summary changed from need to fix system for providing the target triple to compiling for another target than the host platform is broken.

Ticket Navigation