[Trilinos-Users] int, Thyra::Ordinal: Thyra::create_Comm, Teuchos::Comm incompatibility?

[Bartlett, Roscoe A]

Nico,

You are using the development version of Trilinos yes?

The change in ordinal types was made to auto support 64 bit on 64 bit machines after a long discussion (see https://software.sandia.gov/bugzilla/show_bug.cgi?id=4253).  However, this was a backward-compatibility breaking change so it has had its downsides.

I will add a configure-time argument to allow you to pick this type so you can do:

    -DTeuchos_ORDINAL_TYPE:STRING=int

where by default it is:

    -DTeuchos_ORDINAL_TYPE:STRING=ptrdiff_t

Add yourself to the bug and you will get an email when this is finished.

- Ross




From: trilinos-users-bounces at software.sandia.gov [mailto:trilinos-users-bounces at software.sandia.gov] On Behalf Of Nico Schlömer
Sent: Tuesday, December 08, 2009 8:50 AM
To: trilinos-users at software.sandia.gov
Subject: [Trilinos-Users] int, Thyra::Ordinal: Thyra::create_Comm, Teuchos::Comm incompatibility?

Hi,

I'm bumping into problems here on a machine where Thyra::Ordinal is "long int" instead of the (regular?) "int".

I'm specifically creating a Teuchos::Comm via Thyra::create_Comm, and get a Teuchos::Comm<long int>. I'm unsuccessful in instantiating a Tpetra::Map<long int> with this communicator, which is because the none of the Tpetra::Map is templated in it's Teuchos::Comm argument, but instead demand a Teuchos::Comm<int>.

Would it possibly make sense to change this for GlobalOrdinal, or is there another way for creating a Tpetra::Map out of a Thyra::create_Comm?

Cheers,
Nico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://software.sandia.gov/pipermail/trilinos-users/attachments/20091208/24558f87/attachment.html