New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
__attribute__((packed)) breaks intellisense #12248
Comments
@TracerDS The problem is caused by a failure to query your compiler, the logging Is that file supposed to end with an .exe? If you set C_Cpp.loggingLevel to "Debug", does the C/C++ pane logging show any more info on why querying the compiler is failing? |
Nope. The compiler doesnt have an extension (unix file type). |
@TracerDS Yes, we query the compiler for system defines and includes. Is the file executable on Windows? |
Nope. The compiler is not windows compatible. It is however fully WSL (unix) compatible (ELF executable)
I'll send info in a moment |
With
Diagnostics:
|
@TracerDS We're looking for the logging from the pane with name "C/C++". In particular, the logs related to the compiler querying that is failing. |
Okay, how to get the logs from it? |
@TracerDS The same way you got the other logging: |
|
@TracerDS The logging shows
Does your compiler support -std=c++23 and -std=c++2x? Does it support -m64 or are you using a different target argument? Can you try with 1.20.2 -- we made various fixed that could apply and the logging might be better. |
I changed it from c++23 to c++20 for my project. Hope it will make a difference
yes
When I compile my C++ files, this is the command I call in the Makefile:
Will try that later. I have changed my configuration a little bit, but it shouldnt matter much since the compiler doesnt change. Arch doesnt matter in this case; |
@TracerDS Sorry, earlier reference to Is there a reason you're using a compilerPath with The |
The files itself compile. There is no issue with the compilation process. Only intellisense is broken.
Yeah I will change that to i686 and try again.
Yeah it is supported. |
@TracerDS Our extension adds from flags to query the compiler that aren't used during normal building. It's possible your compiler might not support those flags or may output unexpected text, i.e. the args |
Some cannot be supported due to the nature of bare crosscompiler. Other than that, most flags are supported |
@TracerDS Can you try with |
Yes, it probably qualifies for that issue. |
In any case @sean-mcmanus is there a workaround for this issue yet? |
@TracerDS I'm not sure yet why the compiler query is failing. Does the compiler query not return any |
@TracerDS Temporarily setting the C_Cpp.loggingLevel to the hidden value of "7" may show more compiler querying logging (ignore the warnings about it not being a valid value), i.e. the entire query output. |
if you mean
Sure |
Sorry, its quite long
|
@TracerDS I'm looking for the compiler query logging. It looks like the logging you provided is after the compiler querying has already run. I'm also looking into if the lack of The logging would include stuff like but show more info. |
Thats all the info I got from the |
So... any solutions? |
@TracerDS Sorry, we've been pretty busy. We still need to look into what could be causing this. |
Environment
Bug Summary and Steps to Reproduce
Bug Summary:
__attribute__((packed))
causes syntax errors, but the code compiles just fine.It also causes
typedef struct
to not be recognized.Steps to reproduce:
Expected behavior:
__attribute__
keywordtypedef struct {} Struct;
as a Struct typeConfiguration and Logs
LSP logs:
Other Extensions
No response
Additional context
Related: #4787
I have WSL, VS2022 and MinGW installed.
I also have a crosscompiler installed that Im using in this project.
The text was updated successfully, but these errors were encountered: