Thread overview | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
May 29, 2013 LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Without any bells and whistles, here is the first round of beta packages for the 0.11.0 release, scheduled for next weekend: http://d32gngvpvl2pi1.cloudfront.net/ldc2-0.11.0-beta1-linux-x86.tar.gz http://d32gngvpvl2pi1.cloudfront.net/ldc2-0.11.0-beta1-linux-x86.tar.xz http://d32gngvpvl2pi1.cloudfront.net/ldc2-0.11.0-beta1-linux-x86_64.tar.gz http://d32gngvpvl2pi1.cloudfront.net/ldc2-0.11.0-beta1-linux-x86_64.tar.xz http://d32gngvpvl2pi1.cloudfront.net/ldc2-0.11.0-beta1-mingw-x86.7z http://d32gngvpvl2pi1.cloudfront.net/ldc-0.11.0-beta1-src.tar.gz MD5 checksums: 75ce19ff7d57155d679a214a5f970213 ldc2-0.11.0-beta1-linux-x86.tar.gz 982903082dd7fe0b696d0268122ab724 ldc2-0.11.0-beta1-linux-x86.tar.xz b9de309f8910fbc151981dee7598e45d ldc2-0.11.0-beta1-linux-x86_64.tar.gz c7a9ede3297fe83b73d3aeec1cd00e46 ldc2-0.11.0-beta1-linux-x86_64.tar.xz c6e7815b0dc034f72c276a54e1aa28ce ldc2-0.11.0-beta1-mingw-x86.7z 01c291c6db3698144e833ee2b2bb7140 ldc-0.11.0-beta1-src.tar.gz The MinGW version is to be considered a preview/alpha/… version as there are known issues. It also requires a very recent mingw32-w64 snapshot, such as this one: http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/gcc-4.8-dw2-release/i686-w64-mingw32-gcc-dw2-4.8.0-win32_rubenvb.7z/download As previously discussed, there are no OS X packages at this point, as LLVM 3.2 doesn't pass the test suite (GitHub issue #362), and we hit a regression for the current 3.3 RC 1. But there is also an open issue on Linux: For some reason, the versions from the above packages fail on a test case from the DMD test suite: --- $ /build/work/ldc/bin/ldc2 -g runnable/ldc_github_176.d UNREACHABLE executed! 0 ldc2 0x0000000000fad8bf 1 ldc2 0x0000000000faf32a 2 libpthread.so.0 0x00007f1d201258f0 3 libc.so.6 0x00007f1d1f411b25 gsignal + 53 4 libc.so.6 0x00007f1d1f415670 abort + 384 5 ldc2 0x0000000000f9a664 llvm::llvm_unreachable_internal(char const*, char const*, unsigned int) + 356 6 ldc2 0x0000000000641c9e 7 ldc2 0x000000000064229c DtoDwarfLocalVariable(llvm::Value*, VarDeclaration*, llvm::ArrayRef<llvm::Value*>) + 220 8 ldc2 0x000000000063311d DtoVarDeclaration(VarDeclaration*) + 509 9 ldc2 0x0000000000633498 DtoDeclarationExp(Dsymbol*) + 312 10 ldc2 0x00000000006481b1 DeclarationExp::toElem(IRState*) + 65 11 ldc2 0x00000000006469fd Expression::toElemDtor(IRState*) + 77 12 ldc2 0x00000000006172ea ExpStatement::toIR(IRState*) + 74 13 ldc2 0x00000000006171ff CompoundStatement::toIR(IRState*) + 95 --- I tried to reproduce this with a local build, but didn't have any success so far. I am not convinced that this is a GCC miscompilation bug, though, as there is a mysterious occasional crash on the same file using the MinGW port. I'm pretty swamped in work right now, so if somebody wants to help with writing the release notes/announcement, I'd appreciate that very much. David |
May 29, 2013 Re: LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to David Nadlinger | 30-May-2013 00:50, David Nadlinger пишет: > Without any bells and whistles, here is the first round of beta packages > for the 0.11.0 release, scheduled for next weekend: > Cool. One thing that bothered my with LDC 0.10 (and I loved it anyway) is that oldish frontend didn't accept this new syntax: alias T = FancyTypeName!U; What is the 0.11 frontend state? -- Dmitry Olshansky |
May 29, 2013 Re: LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Dmitry Olshansky | On Wednesday, 29 May 2013 at 21:22:28 UTC, Dmitry Olshansky wrote:
> What is the 0.11 frontend state?
2.062. Should have written at least some release notes even for the beta, I guess. ;)
David
|
May 30, 2013 Re: LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to David Nadlinger | On Wednesday, 29 May 2013 at 21:16:15 UTC, David Nadlinger wrote:
> Without any bells and whistles, here is the first round of beta packages for the 0.11.0 release, scheduled for next weekend:
>
Great!
I also updated the Gentoo overlay. :-)
Kai
|
June 02, 2013 Re: LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to David Nadlinger | Too bugged, it's impossible to compile anything except hello world. Error: class perfontana.node.Node had semantic errors when compiling e = 0E689168, ty = 35 _error_ 0033E378 e = 0E689168, ty = 35 _error_ 0033E378 |
June 02, 2013 Re: LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Temtaime | On Sunday, 2 June 2013 at 08:33:28 UTC, Temtaime wrote:
> Too bugged, it's impossible to compile anything except hello world.
>
> Error: class perfontana.node.Node had semantic errors when compiling
> e = 0E689168, ty = 35
> _error_ 0033E378
> e = 0E689168, ty = 35
> _error_ 0033E378
Au contraire, it compiles all of my non-trivial projects…
No, seriously, we are obviously keen to hear about any problems, but this bug report is useless without any further details. Could you please provide the steps needed to reproduce this problem?
— David
|
June 02, 2013 Re: LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to David Nadlinger | I can not figure out the test case, project too large. Can you give me more information what that error can mean ? |
June 02, 2013 Re: LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Temtaime | On Sun, Jun 2, 2013 at 2:02 PM, Temtaime <temtaime@gmail.com> wrote: > Can you give me more information what that error can mean ? This error literally means that the DMD front-end handed off an invalid AST to our glue code (there is a value for which type->ty == Terror). In such cases, there should always be an actual error message before that, which stops the code from even reaching this stage. The absence of that is likely a bug in the frontend (or our copy of the frontend), but it's impossible to say what exactly is going on. For reducing the test case, I'd recommend to give DustMite [1] a try. You simply set up a test script grepping for that error message in the compiler output, and let it do its magic. At the end, your test case should have gone down to a manageable size. David [1] https://github.com/CyberShadow/DustMite |
June 02, 2013 Re: LDC 0.11.0 Beta 1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to David Nadlinger | I'm figured out testcase. It's too strange. http://dpaste.1azy.net/c3f8b2d9 |
Copyright © 1999-2021 by the D Language Foundation