On May 31, 5:29 pm, James Dennett <james.denn...@gmail.com> wrote:
> On May 30, 11:06 am, Pete Becker <p...@versatilecoding.com> wrote:
>
>
>
> > wasti.r...@gmx.net wrote:
> > > On May 29, 4:32 pm, scarvenger <Felipe.Fari...@gmail.com> wrote:
> > >> Is there any interest in receiving a proposal for a Standard C++
> > >> Application Binary Interface? If not, why?
>
> > > Little interest, I'd guess. The reason is that any attempt to unify
> > > compilers would inevitably break all those that aren't following this
> > > very ABI already.
>
> > > On the other hand, there already is a semi-standard ABI that any
> > > compiler that wants can follow:
> > >http://www.codesourcery.com/public/cxx-abi/
>
> > Note that this link points to an ABI for Itanium processors. There are
> > other processors out there in the world, and that's the primary reason
> > for not standardizing an ABI: it's platform-specific, so it's not the
> > business of the C++ standards committee.
>
> I agree that WG21 shouldn't be in the business of standardizing
> platform ABIs, but the "Itanium ABI" is largely processor-independent,
> and with suitable adjustments is widely used on other processors.
>
> As for plans to update it to cope with C++0x, I know nothing.
>

The processor-independent "Common C++ ABI", which is based on the
Itanium ABI, is constantly being updated. You can track this on the
mailing list. I think the main issue is how to mangle the new
additions, especially lambdas.


--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

Is there any interest in receiving a proposal for a Standard C++
Application Binary Interface? If not, why?

--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

On May 29, 4:32 pm, scarvenger <Felipe.Fari...@gmail.com> wrote:
> Is there any interest in receiving a proposal for a Standard C++
> Application Binary Interface? If not, why?

Little interest, I'd guess. The reason is that any attempt to unify
compilers would inevitably break all those that aren't following this
very ABI already.

On the other hand, there already is a semi-standard ABI that any
compiler that wants can follow:
http://www.codesourcery.com/public/cxx-abi/

What did you have in mind precisely?

Sebastian


--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

scarvenger wrote:
>
> Is there any interest in receiving a proposal for a Standard C++
> Application Binary Interface? If not, why?
>


I doubt it. Why? We are already badly overloaded with work and an ABI
would be a very large amount more work (even assuming that it can be
done without efficiency cost)

--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

wasti.redl@gmx.net wrote:
> On May 29, 4:32 pm, scarvenger <Felipe.Fari...@gmail.com> wrote:
>> Is there any interest in receiving a proposal for a Standard C++
>> Application Binary Interface? If not, why?
>
> Little interest, I'd guess. The reason is that any attempt to unify
> compilers would inevitably break all those that aren't following this
> very ABI already.
>
> On the other hand, there already is a semi-standard ABI that any
> compiler that wants can follow:
> http://www.codesourcery.com/public/cxx-abi/
>

Note that this link points to an ABI for Itanium processors. There are
other processors out there in the world, and that's the primary reason
for not standardizing an ABI: it's platform-specific, so it's not the
business of the C++ standards committee.

--
    Pete
Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of
"The Standard C++ Library Extensions: a Tutorial and Reference"
(www.petebecker.com/tr1book)

[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]

On May 30, 11:06 am, Pete Becker <p...@versatilecoding.com> wrote:
> wasti.r...@gmx.net wrote:
> > On May 29, 4:32 pm, scarvenger <Felipe.Fari...@gmail.com> wrote:
> >> Is there any interest in receiving a proposal for a Standard C++
> >> Application Binary Interface? If not, why?
>
> > Little interest, I'd guess. The reason is that any attempt to unify
> > compilers would inevitably break all those that aren't following this
> > very ABI already.
>
> > On the other hand, there already is a semi-standard ABI that any
> > compiler that wants can follow:
> >http://www.codesourcery.com/public/cxx-abi/
>
> Note that this link points to an ABI for Itanium processors. There are
> other processors out there in the world, and that's the primary reason
> for not standardizing an ABI: it's platform-specific, so it's not the
> business of the C++ standards committee.

I agree that WG21 shouldn't be in the business of standardizing
platform ABIs, but the "Itanium ABI" is largely processor-independent,
and with suitable adjustments is widely used on other processors.

As for plans to update it to cope with C++0x, I know nothing.

-- James


--
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@netlab.cs.rpi.edu]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://www.comeaucomputing.com/csc/faq.html                      ]