Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Semantic analysis support for Float128 (Unexpected typespec: CFloat128Type) #46

Closed
lambdageek opened this issue Feb 3, 2018 · 1 comment
Closed

Semantic analysis support for Float128 (Unexpected typespec: CFloat128Type) #46

lambdageek opened this issue Feb 3, 2018 · 1 comment

Comments

@lambdageek
Copy link

Right now if we run analyzeAST on a translation unit that uses 128 bit floats, we will die at tDirectType:

language-c/src/Language/C/Analysis/DeclAnalysis.hs

Line 269 in 3f348f5

TSNonBasic t -> astError node ("Unexpected typespec: " ++ show t)

with the message

Unexpected typespec: CFloat128Type (NodeInfo "/usr/include/stdlib.h": line 236, ...
@lambdageek lambdageek mentioned this issue Feb 3, 2018
Merged
@lambdageek
Copy link
Author

Fixed by #47 .

lambdageek added a commit to lambdageek/centrinel that referenced this issue Feb 23, 2018
@lambdageek
Bump language-c min version to 0.7.2
0a91270 
Pick up the fix for visq/language-c#46
(minimal __Float128 support for the semantic analysis modules)

This is needed on systems with recent glibcs that include prototypes for
128-bit float math functions.
lambdageek added a commit to lambdageek/centrinel that referenced this issue Feb 23, 2018
@lambdageek
(stack.yaml) switch to released language-c-0.7.2
6e23921 
Upstream picked up our fix for visq/language-c#46,
we don't need our own fork anymore.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lambdageek