[M3devel] moving to new target names, in Hudson?

[Jay K]

The old target names are still available.


I agree something like cm3 -version should be more useful.
Notice:
  gcc -dumpmachine
 
gcc -dumpspecs
 
gcc -dumpversion
 

gcc -print-search-dirs 


*However* notice that cm3 is *not* preconfigured/predisposed for any particular target.


It has a list of targets and it can handle any of them. The config file decides the target.
 In fact, neither cm3 nor the config files are particularly knowledable about targets.
  The config files vary a little in how they run the compiler or linker.
  cm3 varies mainly in word size, endianness, and jmpbuf size.
  All the real work of knowing about targets is buried in gcc.
  And a smattering of #ifdefs in C code. Some of which could be pushed to autoconf.


The old names confuse people -- you, for example.
They are inconsistent.
They don't specify processor architecture.


What pain did you all go through when FreeBSD changed to FreeBSD2 changed to FreeBSD3 changed to FreeBSD4?
Or LINUX to LINUXELF to LINUXLIBC6?
So long ago nobody remembers?
I used LINUXELF a little, built it, went away, came back and there was LINUXLIBC6. I had no code. It didn't matter to me.


 - Jay

----------------------------------------
> To: wagner at elegosoft.com
> Date: Mon, 19 Jul 2010 02:04:59 -0700
> From: mika at async.async.caltech.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] moving to new target names, in Hudson?
>
>
> Can I also add that changing the target names is going to require
> work---perhaps quite a bit of work---among users of CM3... now they will
> no longer match PM3, or a version of CM3 older than a particular, arbitrary
> date. All sorts of configuration and setup scripts will have to be fixed.
> I would hope this sort of thing would be done for a new version number
> or something else that is easily testable... I suppose you can grep through
> the output of cm3 -version. But m3build doesn't print the target, so the
> scripts really do become quite a bit more complicated....
>
> Mika
>
> Olaf Wagner writes:
> >Quoting Jay K :
> >
> >> Olaf, can I request that if/when you move Hudson to head, that you =20
> >> also switch to I386_LINUX, I386_FREEBSD, I386_NT,
> >> and whatever we decide for SPARC32_SOLARIS?
> >> I've mostly switched to them myself. It wasn't difficult. (I always =20
> >> say that).
> >
> >It will require a lot of manual work, compared to the more or less
> >automated transition I just made from release to current for all the
> >jobs. The target platform names are part of the jobs, and are also used
> >in various places in the build scripts, so that many things are likely
> >to break.
> >
> >My guess is that it will take some days for every target move given my
> >current attention pattern for cm3, i.e. have a look at how things work
> >out now and then between other work.
> >
> >Let's wait until all the jobs work again with their old target names,
> >
> >Olaf
> >
> >> I think for SPARC32_SOLARIS we should either have SPARC32_SOLARIS =20
> >> that is the equivalent of today's SOLsun.
> >> Effectively dropping SOLgnu.
> >>
> >>
> >> Or we also add SPARC32_SOLARIS_gcc, which is just a configuration =20
> >> file and not a target.
> >> This is like the "experiment" I did with NT386/NT386GNU, which I =20
> >> think I regret, except
> >> SPARC32_SOLARIS / SPARC32_SOLAROS_gcc are far far more similar than those.
> >> All their platform-specific code is identical. Their backend is =20
> >> identical. etc.
> >>
> >>
> >> A related option is SPARC32_SOLARIS_cc or SPARC32_SOLARIS_suncc, and =20
> >> SPARC32_SOLARIS_gcc.
> >> Config files.
> >> But the compiler only know about SPARC32_SOLARIS.
> >> Just putting the two config files more as peers, so to speak.
> >>
> >>
> >> The way I switched targets was probably doing a cross build.
> >> That is overkill. You can probably just export CM3_TARGET to the =20
> >> name you want.
> >> And maybe fiddle with shipping of cm3cg or settings its build_dir -- =20
> >> i.e. leave it as just host and host-target.
> >--=20
> >Olaf Wagner -- elego Software Solutions GmbH
> > Gustav-Meyer-Allee 25 / Geb=C3=A4ude 12, 13355 Berlin, Germa=
> >ny
> >phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> > http://www.elegosoft.com | Gesch=C3=A4ftsf=C3=BChrer: Olaf Wagner | Sitz=
> >: Berlin
> >Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194