Skip to content

__int128 and "unsigned __int128" are not fundamental types #87

Open
@RomanYakovenko

Description

@RomanYakovenko

Hello.
I am using the following environment:
$ uname -a
Linux roman 4.10.0-30-generic #34-Ubuntu SMP Mon Jul 31 19:38:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a Description: Ubuntu 17.04
Release: 17.04
Codename: zesty
$ castxml --version pyplusplus/hg/default
castxml version 0.1-gd5934bd

CastXML project maintained and supported by Kitware (kitware.com).

clang version 3.8.1-9ubuntu1 (tags/RELEASE_381/final)
Target: x86_64-pc-linux-gnu
Thread model: posix

The following code was compiled:
void abc(int i, ...);

castxml generated the following xml file:

<GCC_XML version="0.9.0" cvs_revision="1.139">

























</GCC_XML>

As you can see __int128 and 'unsigned __int128' are fundamental types, while __int128_t and __uint128_t are just typedefs for them.

I think this should be fixed in cpptypes, but may be I am wrong. Did not tested the output in other environments. May be the fix is more complex.

Regards,
Roman

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions