Discuss DFP mangling was(Re: [cxx-abi-dev] C++0x: mangling of char16_t and char32_t)
Michael Wong
michaelw at ca.ibm.com
Tue Mar 25 19:38:35 UTC 2008
May be its time to have the discussion I have been suggesting.
In the interest of resolving this quickly to help Doug out, I am soliciting
folks who are interested in this DFP name mangling discussion. Some folks
that I am aware of are:
Dennis Handley
Prem Rao
Daveed Vandevoorde
ON IBM's side I will add several of our implementors of DFP to ensure we
get a fair hearing of all the issues.
I would like someone who represents GNU, so may be that should be Mark, who
can also work as arbitrator in case we need it. But the folks who
integrated the DFP branch are likely from the IBM Linux Technology Centre.
I am proposing we have a phone call this week or next. Due to the
cross-coast nature, I would suggest it in the afternoon so West coast
(where Dennis is) can join.
Lets say Thursday Mar 27, at 4-5 EST, or 1-2 PST. If this does not work, I
would propose next Monday, Mar 31 4-5 EST or 1-2 PST.
Can folks reply on their availability and I will set out a telecon number?
Thanks.
Michael Wong
XL C++ Compiler kernel Development
IBM Canada Ltd., C2/KD2/8200/MKM
8200 Warden Avenue
Markham, Ontario L6G 1C7
W:905-413-3283 F:905-413-4839
Boost test results
http://www-1.ibm.com/support/docview.wss?rs=2239&context=SSJT9L&uid=swg27006911
C/C++ Compilers Support Page
http://www.ibm.com/software/awdtools/ccompilers/support/
C/C++ Feature Request Interface
http://www.ibm.com/support/docview.wss?uid=swg27005811
XL Fortran Compiler Support Page
http://www.ibm.com/software/awdtools/fortran/xlfortran/support/
XL Fortran Feature Request Interface
http://www.ibm.com/support/docview.wss?uid=swg27005812
"Doug Gregor"
<doug.gregor at gmai
l.com> To
Michael Wong/Toronto/IBM at IBMCA
03/25/2008 02:38 cc
PM cxx-abi-dev at codesourcery.com
Subject
Re: [cxx-abi-dev] C++0x: mangling
of char16_t and char32_t
On Tue, Mar 25, 2008 at 2:13 PM, Michael Wong <michaelw at ca.ibm.com> wrote:
> I would prefer if we hold off using q for now, as it is in a contentious
> mode for one of the DFP manglings which I still have to discuss with
other
> C++ ABI members for an alternative:
> Currently IBM and I think GNU (but in 4.3) uses these for name mangling
of
> DFP builtin types:
> >> Decimal32: "p"
> >> Decimal64: "q"
> >> Decimal128: "r"
Ah, I remember this discussion. I don't think GCC has a mangling for
these yet, but if IBM is already using 'q' then we need to be careful
here.
> One of the issue is the same which is a wish for a more descriptive
> mangling. Others include whether we really care about interoperability
> given the different underlying representations, emulation modes vs
hardware
> modes issues.
It makes life easier for other tool vendors if name mangling is the
same across different compilers.
> So in summary, I would appreciate it if you would avoid this area until
we
> can settle this issue.
GCC recently received a patch that adds support for char16_t and
char32_t, so that forces the issue a bit.
- Doug
More information about the cxx-abi-dev
mailing list