From: Ian Lance Taylor <ian@ai...> - 2012-04-19 00:57:06
Olly Betts <olly@...> writes:
> On 21 March 2012 11:35, <ianlancetaylor@...> wrote:
>> Revision: 12940
>> Add support for new features available in gccgo 4.7, notably calling
>> Entersyscall and Exitsyscall around calls to wrapped C/C++ code.
>> +<td>Generate code for gccgo 4.6. The default is set by the configure
>> + script.</td> This generates code that does not use some facilities
>> + that are only available in gccgo 4.7 and later.
> Wouldn't it be better if the default behaviour was fixed, rather than
> depending on what gccgo version (if any) happened to be installed when
> SWIG was built?
> As this is now the user will need to specify one of -gccgo-46 or -no-gccgo-46
> explicitly anyway in order to get reliable behaviour if their code is ever used
> with a different build of SWIG.
> It's also unhelpful to distros building binary packages as it means that
> rebuilding the swig package with a newer version of GCC could give a package
> which behaves differently.
I suppose I don't see it as a big problem if a distro builds a new SWIG
with a new gccgo and the new SWIG works with the new gccgo, even if that
means behaving differently than the earlier SWIG.
However, I don't feel particularly strongly about this. If the SWIG
developers prefer that SWIG always default to generating code for gccgo
4.7 and later, I can change it. Then anybody still using gccgo 4.6 will
have to use the command line option.
Get latest updates about Open Source Projects, Conferences and News.