microsoft / microsoft/vscode-cpptools

Leverage compiler system defines to determine types and sizes for IntelliSense

Open
#7,355 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Request internal Language Service
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Various type and sizes are essentially hard-coded per IntelliSense mode. Some are passed in based on a static file (such as __SIZE_TYPE__ and __PTRDIFF_TYPE in linux.gcc.x64.json). Some are hard-coded in the IntelliSense parser, based on the compiler and architecture (IntelliSense mode).

gcc/clang compilers will output types and sizes when queried, such as:

c:\msys64\mingw64\bin>gcc.exe -x c++ -E -dM nul | findstr /i SIZEOF
#define __SIZEOF_FLOAT80__ 16
#define __SIZEOF_LONG__ 4
#define __SIZEOF_LONG_DOUBLE__ 16
#define __SIZEOF_FLOAT__ 4
#define __SIZEOF_SIZE_T__ 8
#define __SIZEOF_WINT_T__ 2
#define __SIZEOF_POINTER__ 8
#define __SIZEOF_PTRDIFF_T__ 8
#define __SIZEOF_INT__ 4
#define __SIZEOF_FLOAT128__ 16
#define __SIZEOF_SHORT__ 2
#define __SIZEOF_INT128__ 16
#define __SIZEOF_WCHAR_T__ 2
#define __SIZEOF_DOUBLE__ 8
#define __SIZEOF_LONG_LONG__ 8

c:\msys64\mingw64\bin>gcc.exe -x c++ -E -dM nul | findstr /i long
#define __UINTMAX_TYPE__ long long unsigned int
#define __SIZEOF_LONG__ 4
#define __SIZEOF_LONG_DOUBLE__ 16
#define __LONG_LONG_MAX__ 0x7fffffffffffffffLL
#define __LONG_LONG_WIDTH__ 64
#define __INT_FAST64_TYPE__ long long int
#define __SIZE_TYPE__ long long unsigned int
#define __UINT_LEAST64_TYPE__ long long unsigned int
#define __LONG_MAX__ 0x7fffffffL
#define __INT_LEAST64_TYPE__ long long int
#define __GCC_ATOMIC_LONG_LOCK_FREE 2
#define __INTPTR_TYPE__ long long int
#define __UINT_FAST64_TYPE__ long long unsigned int
#define __INT64_TYPE__ long long int
#define __UINT64_TYPE__ long long unsigned int
#define __LONG_WIDTH__ 32
#define __INTMAX_TYPE__ long long int
#define __PTRDIFF_TYPE__ long long int
#define __UINTPTR_TYPE__ long long unsigned int
#define __SIZEOF_LONG_LONG__ 8
#define __GCC_ATOMIC_LLONG_LOCK_FREE 2

It's possible that different versions or flavors of the same compiler will output different values for these, even for the same architecture.

For example, both MinGW x64 and cygwin x64 are associated with the windows-gcc-x64 IntelliSense mode, but use different sizes for long.

D:\cygwin64\bin>gcc.exe -x c++ -E -dM /dev/null | findstr /i x86
#define __x86_64 1

D:\cygwin64\bin>gcc.exe -x c++ -E -dM /dev/null | findstr /i SIZEOF_LONG
#define __SIZEOF_LONG__ 8


c:\msys64\mingw64\bin>gcc.exe -x c++ -E -dM nul | findstr /i x86
#define __x86_64 1

c:\msys64\mingw64\bin>gcc.exe -x c++ -E -dM nul | findstr /i SIZEOF_LONG
#define __SIZEOF_LONG__ 4

Some gcc ports to Windows follow Windows conventions for types and sizes, and some use Linux conventions.

To improve compatibility between different versions and flavors of gcc compilers, we could use the queried system defines from the compiler to correct types and sizes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Begin by tracing the IntelliSense parser's hard-coded type and size handling and the compiler-query path, using the shown gcc -E -dM commands as the reference behavior. Done means compiler-reported defines can correct types and sizes across differing GCC ports and versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
compilers, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.