Actions

icon Post
text/html Subscribe
text/html Unsubscribe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Cxx-abi] Re: [cxx-abi-dev] Question about guard variable typ es


  • To: "Nelson, Clark" <clark.nelson@xxxxxxxxx>, Martin v. Löwis <martin@xxxxxxxxxxx>, "cxx-abi-dev@xxxxxxxxxxxxxxxx" <cxx-abi-dev@xxxxxxxxxxxxxxxx>
  • Subject: RE: [Cxx-abi] Re: [cxx-abi-dev] Question about guard variable typ es
  • From: Mark Mitchell <mark@xxxxxxxxxxxxxxxx>
  • Date: Fri, 06 Dec 2002 09:29:44 -0800



--On Friday, December 06, 2002 09:11:18 AM -0800 "Nelson, Clark" <clark.nelson@xxxxxxxxx> wrote:

If we do what you suggest, G++ will have to change.  I'd
prefer just to
match G++; there's nothing particularly wrong with "long long" and
there aren't -- yet -- very many non-IPF implementations to
worry about.

In what way do you think G++ would have to change?

It won't -- if we change the ABI to say "long long".  Otherwise, it needs
to be changed to explicitly construct a 64-bit type.

Intel, HP?

I can tell that a question is being directed to Intel, but I don't know
what the question actually is. Could you spell it out please?

What type do you use for guard variables in 32-bit mode?  In 64-bit mode?

--
Mark Mitchell                mark@xxxxxxxxxxxxxxxx
CodeSourcery, LLC            http://www.codesourcery.com