| 1 |
>The GCC Page (http://gcc.gnu.org/gcc-3.2/changes.html) says it is |
| 2 |
>MultiVendor V3 compatible |
| 3 |
|
| 4 |
ABI = Application Binary Interface. What vendors of debuggers and |
| 5 |
other tools see when they work with the output of GCC. 3.2 is |
| 6 |
compatible with version 3 of the spec. |
| 7 |
|
| 8 |
>- does that mean that it's compatible (again) with 2.95? There |
| 9 |
>aren't any other changes listed on the page, so does that also |
| 10 |
>mean that no changes in code are required from 3.1 to 3.2 to compile? |
| 11 |
>Will this just mean going from 2.95 to 3.2 will be a matter of fixing |
| 12 |
>the ISO C/C++ standards, just as for going from 2.95 to 3.0? |
| 13 |
|
| 14 |
Anything that compiled with 3.x will compile without change with |
| 15 |
3.2. As stated, the only changes are to the ABI, what other tools |
| 16 |
interface with. |
| 17 |
|
| 18 |
Thus you would need the same changes to 2.95 code as you would for any |
| 19 |
of the other 3.x compilers. My experience has been that bringing the |
| 20 |
code into compliance with the ISO standards will fix any problems. |
| 21 |
|
| 22 |
|
| 23 |
_________________________________________________________________ |
| 24 |
MSN Photos is the easiest way to share and print your photos: |
| 25 |
http://photos.msn.com/support/worldwide.aspx |
Archives