Lines Matching refs:compilers
24 * Interoperation:: Problems using GCC with other compilers,
66 together with other compilers or with the assemblers, linkers,
72 compilers, so the object files compiled by GCC cannot be used with object
82 provided from other compilers---but the programs would then crash when
334 K&R compilers allow comments to cross over an inclusion boundary
345 In some other C compilers, an @code{extern} declaration affects all the
485 compilers.
693 Other C++ compilers may not correctly implement the standard behavior.
694 As a result, when you switch to @command{g++} from one of these compilers,
818 Note that some compilers (including G++ versions prior to 3.4) get these
819 examples wrong and accept above code without an error. Those compilers
864 Code like this may run successfully under some other compilers,
865 particularly obsolete cfront-based compilers that delete temporaries
982 compilers. And it doesn't seem very important, given that you can get
1028 were to support by default the same dialect as the other compilers on
1070 standard. This is illogical. The standard is a standard for compilers
1072 compilers such as plain @command{gcc}. Whatever the ISO C standard says