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.

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

Move to new LLVM version #110

Closed
PeterMatula opened this issue Jan 29, 2018 · 7 comments
Closed

Move to new LLVM version #110

PeterMatula opened this issue Jan 29, 2018 · 7 comments

Comments

@PeterMatula
Copy link
Collaborator

Version of LLVM we use is pretty old (3.9.1). We should move to the new LLVM sooner rather than later.

@MerovingianByte
Copy link

Wouldn't it be possible to talk to the LLVM guys to provide more options to disable optimizations and stuff so that retdec can use vanilla LLVM instead of hacking it? Maybe it would save time in the long run. I mean, I'm just curious, not my business.

@s3rvac
Copy link
Member

s3rvac commented Feb 17, 2018

@MerovingianByte Frankly speaking, I do not see this as realistic. We have many changes throughout the entire codebase, and their conditional inclusion would seriously clutter the code. Never say never, though :-).

@s3rvac
Copy link
Member

s3rvac commented Mar 8, 2018

LLVM 6.0 is out.

@s3rvac
Copy link
Member

s3rvac commented Sep 20, 2018

LLVM 7.0 is out.

@s3rvac
Copy link
Member

s3rvac commented Mar 20, 2019

LLVM 8.0 is out.

@sskras
Copy link

sskras commented Apr 24, 2019

Are other changes not linked to this commit?

@PeterMatula
Copy link
Collaborator Author

This was fixed by merging llvm-8 branch in llvm repo: avast/llvm@82632c5
and in retdec repo: 7a2018b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants