Chris Quenelle <Chris.Quenelle at Sun.COM> wrote:
> Joerg Schilling wrote:
> > Chris Quenelle <Chris.Quenelle at Sun.COM> wrote:
> >
> >> It's likely that Sun Studio Next will have -xstrconst on by default.
> >> It's likely that the C compiler will transition to using the same
> >> syntax as the C++ compiler uses today. (-features=[no%]conststrings)
> >> Hopefully we will remember the -m64 lesson, and silently accept
> >> both options for at least one FCS release. This change has already
> >
> > -m64 needs much longer support if you like to allow people to write
> > portable
> > (across versions) build systems.
> >
> > It is different with Sun internal code that does not need to be portable at
> > all.
>
> I wasn't clear about what the -m64 lesson was. In Sun Studio 12 we wanted to
> switch our syntax from -xarch=v9 to -m64. We started warning about the
> old syntax right away, and that meant there was combination of options
> that would work without warnings on both Sun Studio 11 and Sun Studio 12.
> So it seems like "accept new and old with no warnings for one release" is
> a good policy when we want to transition option syntax.
OK, I was confusing old by new...
The important fact is that my makefiles use either -xarch=v9 or
-xarch=generic64 in order tp be compatible with older Sun compilers. Now with
Studio 12, people see hundereds of warnings.
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
schilling at fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
