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

1.8.1 release notes point to the wrong tarball/zip #7

Closed
ngrewe opened this issue Oct 9, 2015 · 5 comments
Closed

1.8.1 release notes point to the wrong tarball/zip #7

ngrewe opened this issue Oct 9, 2015 · 5 comments

Comments

@ngrewe
Copy link
Member

ngrewe commented Oct 9, 2015

Hi David,

I just noticed that links for the archives in the 1.8.1 release notes still point to the 1.8 release.

Cheers,

Niels

@davidchisnall
Copy link
Member

Ooops. I plan on tweaking the way we do memory allocation for blocks-as-imps soon (which will remove the need for mapping the page in two different places and simplify porting), so I'll push out a 1.8.2 release once that's done. Unfortunately, I can't fix them in 1.8.2 without regenerating the tarballs, which will break packaging.

@ngrewe
Copy link
Member Author

ngrewe commented Oct 9, 2015

I plan on tweaking the way we do memory allocation for blocks-as-imps soon (which will remove the need for mapping the page in two different places and simplify porting)

That sounds cool. I'm interested in seeing how that works in the presence of W^X policies…

@davidchisnall
Copy link
Member

It's quite simple (not sure what the performance impact will be - we'll use more TLB entries, but pollute the i-cache less). Rather than having each page contain data then trampoline code interleaved, we'll have one page of data followed by one page of the trampoline code. All of the ISAs that we care about can do loads with a 4KB displacement easily, so the two loads will be from pc-4KB.

@davidchisnall
Copy link
Member

Hmm, a release is long overdue. I think the latest commit should fix the alignment issues. Most of the changes in the current ANNOUNCE file were things I did last Christmas, so I'll aim to push out a new release once I've seen some evidence that things are working again.

@davidchisnall
Copy link
Member

Closing - it's a real issue, but I can't fix it without changing the hashes of the tarballs, which will break any downstream packages.

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

No branches or pull requests

2 participants