- Yhc - Haskell.org

buildbot failure in macosx_x86
by andrewjwilkinsonw＠gmail.com 13 Jul '06

13 Jul '06

The Buildbot has detected a failed build of macosx_x86. Full details are available at: http://www.indiegigs.co.uk:8010/macosx_x86/builds/2 Buildbot URL: http://www.indiegigs.co.uk:8010/ Build Reason: Build Source Stamp: HEAD Blamelist: Andrew BUILD FAILED: failed shell_2 sincerely, -The Buildbot

1 0

buildbot failure in macosx_x86
by aw＠cs.york.ac.uk 13 Jul '06

13 Jul '06

The Buildbot has detected a failed build of macosx_x86. Full details are available at: http://www.indiegigs.co.uk:8010/macosx_x86/builds/1 Buildbot URL: http://www.indiegigs.co.uk:8010/ Build Reason: Build Source Stamp: HEAD Blamelist: Andrew BUILD FAILED: failed shell_2 sincerely, -The Buildbot

1 0

buildbot failure in windows
by aw＠cs.york.ac.uk 13 Jul '06

13 Jul '06

The Buildbot has detected a failed build of windows. Full details are available at: http://www.indiegigs.co.uk:8010/windows/builds/17 Buildbot URL: http://www.indiegigs.co.uk:8010/ Build Reason: Build Source Stamp: HEAD Blamelist: Andrew BUILD FAILED: failed shell_2 sincerely, -The Buildbot

1 0

buildbot failure in macosx_x86
by aw＠cs.york.ac.uk 13 Jul '06

13 Jul '06

The Buildbot has detected a failed build of macosx_x86. Full details are available at: http://www.indiegigs.co.uk:8010/macosx_x86/builds/0 Buildbot URL: http://www.indiegigs.co.uk:8010/ Build Reason: Build Source Stamp: HEAD Blamelist: Andrew BUILD FAILED: failed shell_2 sincerely, -The Buildbot

1 0

Buildbot
by Andrew Wilkinson 10 Jul '06

10 Jul '06

Hi, I know Neil is quite keen on providing things like nightly builds of YHC rather than people having to know how to use Darcs/scons to get access to YHC. As one step towards this goal I'm happy to donate to the Yhc project a build bot server. Simply visit http://www.indiegigs.co.uk:8010/ to get see how changes to the main YHC source tree effect a number of platforms. Currently this number is one, and it's a Gentoo machine so it fails on the configure step because of libffi. I will also set up my home AMD64 machine to run as a buildbot slave. Anyone willing to set up a Windows or MacOS X slave please contact me :-) Currently the master triggers a build every hour however I intend to monitor the Darcs RSS feed and trigger builds directly off that. Once that is implemented I will, if everyone agrees that this is a good idea, set up the build bot to email errors/warnings from the builds to this list. Regards, Andrew Wilkinson

2 1

hugs + Yhc, or similar...
by Isaac 09 Jul '06

09 Jul '06

Warning: Potentially useless (but then again potentially interesting or useful) musing ahead It occured to me that if we're going to be compilable with GHC and Yhc, we might as well eventually make sure to work with other Haskell implementations as well, like hugs. Of course running Yhc under hugs normally would be a bit stupid because of the speed. And I realized that, since portable Yhc bytecode of Yhc can be distributed, self-compiling Yhc using hugs would not be necessary for bootstrapping from no initial haskell implementation (Hugs is written in C, not haskell as most haskell implementations are) (either way requires that the Yhc-bytecode interpreter be compilable; I'm assuming it's in C). However there are some interesting properties of such a thing: * Every additional compiler Yhc works with helps ensures the code's portability/standardness. * It works for someone who really wants to compile things only from their original sources. Likewise, it helps to cure the property of a program only being defined in terms of itself (and fixability if it's buggy). All known Haskell implementations directly depend at some point on a C implementation, which is probably written in C, so there's no getting around that (although C-- looks interesting; GHC still has a substantial RTS(run-time system) written in C I believe, but jhc deliberately doesn't). Of course this is irrelevant in practice, as gcc and ghc are both heavily tested and have versions that work quite well enough. * Understandability, related to how much it is defined in terms of itself (to someone who knows C and good programming but can't understand natural-language explanations for some mysterious reason).I presume that C-running-Haskell is still a higher level than C-running-Yhc-bytecode, and thus more comprehensible. Now, as to the "mysterious reason": maybe this "someone" is a powerful computer analysing (parts of) a computer system. Perhaps for bugs or properties of it. Perhaps it's some Martians, some space-aliens, some automated code audits, whatever. To me, all this stuff (in part deliberately) sounds like science fiction that could come true in some years. Actually, it could be a paranoid human looking through all code for actions it takes that are undesired (rather than (or in addition to!) using the system's security measures well). Any thoughts? (Any mistaken assumptions?) Basically the summary is: practically useless, but cool. Isaac

2 1

Error building on Windows
by Neil Mitchell 06 Jul '06

06 Jul '06

Hi, I have problems when building yhc under Windows at home: Getting dependencies for depends\filepath\System\FilePath.hs. ghc -i./src/compiler98 -idepends/cpphs -idepends/filepath -c depends\filepath\Sy stem\FilePath.hs -o depends\filepath\System\FilePath.obj Getting dependencies for src\compiler98\Bind.obj. Getting dependencies for src\compiler98\Bind.hs. ... Getting dependencies for src\compiler98\Make.lhs. Getting dependencies for src\compiler98\Derive\Eval.hs. scons: *** [Errno 2] No such file or directory: 'src\\compiler98\\Bind.obj' scons: building terminated because of errors. It shouldn't be getting dependancies for a .obj, then it fails later on. With a scons clean I still get this bug. Thanks Neil

2 1

Yhc .hi format docs
by Robert Dockins 30 Jun '06

30 Jun '06

Is there any documentation/dev notes/anything helpful having to do with the Yhc interface file format? I couldn't find anything on the wiki and trying to read the code for the parser and printer made my head hurt. They're both written in a style that's a little, uh... less than transparent. Rob Dockins Speak softly and drive a Sherman tank. Laugh hard; it's a long way to the bank. -- TMBG

7 10

Bytecode API 0.2
by Robert Dockins 30 Jun '06

30 Jun '06

Fellow Haskellers, The Yhc Bytecode API version 0.2 is now avaliable for general consumption. The changes from version 0.1 are fairly minor: -- Use "Yhc" rather than "YHC" namespace -- rename physical bytecode constructors to use *_W8 rather than *_u8 -- change license to LGPL The project homepage is at: http://www.eecs.tufts.edu/~rdocki01/yhc-bytecode.html From here you can find docs, tarballs and the darcs repository. Enjoy. -- Rob Dockins Talk softly and drive a Sherman tank. Laugh hard, it's a long way to the bank. -- TMBG

1 0

_apply1 goes missing
by Neil Mitchell 25 Jun '06

25 Jun '06

Hi, I have a sample piece of code: --- module HeadReverse where main x = head (reverse x) --- Which currently when compiled with a Yhc from a few weeks ago generates the core: --- module HeadReverse where HeadReverse.main v139 = (Prelude.head ((Prelude.reverse) v139)) --- But I have a cached copy of it, which gives: --- HeadReverse.main v196 = Prelude.head (YHC.Internal._apply1 Prelude.reverse v196) -- The cached copy probably comes from about two months ago - was there any change committed that changes this behaviour intentionally? Which is the correct behaviour? Thanks Neil

2 1