[GHC] #1344: Overflow bug in hex character literals
#1344: Overflow bug in hex character literals
--+-
Reporter: simonmar | Owner:
Type: bug | Status: new
Priority: low | Milestone: _|_
Component: Compiler |Version: 6.6.1
Severity: minor| Keywords:
Difficulty: Easy (1 hr) | Os: Unknown
Testcase: | Architecture: Unknown
--+-
{{{
Prelude Hel\x6c000 World
interactive:1:7: lexical error in string/character literal at character
'c'
Prelude Hel\x6c World
Hel\NUL World
}}}
Two bugs really: the first error message gives a strange location, and the
second example is probably the result of an overflow somewhere.
--
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1344
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: binary distribution problem
On Wed, 2007-05-09 at 03:42 +0100, Frederik Eaton wrote: Hello, I found that the distribution at this URL http://haskell.org/ghc/dist/6.6.1/ghc-6.6.1-x86_64-unknown-linux.tar.bz2 failed to install. There were lots of no such file or directory errors during 'cp' invocations I think. The i386 version sems to work fine. Hope this isn't a mistake on my part. I found the opposite, that the i386 version had lots of errors with 'cp' invocations. It turned out that it was my fault as I was accidentally using the i386 .tar.tbz when the machine I was using was in fact an x86-64 running in 64bit mode. So check your uname -a, is it i686 or x86_64? That said, the failure mode in this case could be friendlier and less confusing. Duncan ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #1345: Wrong registry key created by Windows installer
#1345: Wrong registry key created by Windows installer
+---
Reporter: guest|Owner:
Type: bug | Status: new
Priority: lowest |Milestone:
Component: None | Version: 6.6.1
Severity: trivial | Resolution:
Keywords: | Difficulty: Unknown
Os: Windows | Testcase:
Architecture: Unknown |
+---
Comment (by neil):
Ian, in the installer I sent you the offending lines are:
Root: HKCU; Subkey: HKEY_CURRENT_USER\Software\Haskell\GHC\ghc-6.6.1;
ValueType: string; ValueName: InstallDir; ValueData: {app}
Root: HKCU; Subkey: HKEY_CURRENT_USER\Software\Haskell\GHC; ValueType:
string; ValueName: InstallDir; ValueData: {app}
Change by removing HKEY_CURRENT_USER from the Subkey.
--
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1345
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
[GHC] #1346: bootstrap from HC files
#1346: bootstrap from HC files ---+ Reporter: simonmar | Owner: Type: bug | Status: new Priority: high | Milestone: 6.8 Component: Build System |Version: 6.6.1 Severity: normal| Keywords: Difficulty: Moderate (1 day) | Os: Unknown Testcase:| Architecture: Unknown ---+ There's some work to do on 6.8 to ensure that we can still bootstrap from HC files. This will be slightly harder due to the new Cabal-based build system for libraries, and the solution will probably involve 'setup makefile' somewhere. Also we'll need to update the building guide to include the new instructions, whatever they may be. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1346 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #1345: Wrong registry key created by Windows installer
#1345: Wrong registry key created by Windows installer +--- Reporter: guest|Owner: Type: bug | Status: closed Priority: lowest |Milestone: Component: None | Version: 6.6.1 Severity: trivial | Resolution: fixed Keywords: | Difficulty: Unknown Os: Windows | Testcase: Architecture: Unknown | +--- Changes (by neil): * resolution: = fixed * status: new = closed Comment: Fixed - now the registry keys are created in the correct place, and are tidied up on uninstall. I have uploaded a new installer build, and sent Ian updated installer script files. Since these keys are not critical to anything, people using the old installer shouldn't have any problems - so no need to update. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/1345 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: binary distribution problem
Thanks Duncan, yes 'uname -a' shows i686. I was confused because the cpu is EM46T, I don't know why uname does not say x86_64. Yes, a better failure mode would indeed be helpful! Frederik On Wed, May 09, 2007 at 08:38:57AM +, Duncan Coutts wrote: On Wed, 2007-05-09 at 03:42 +0100, Frederik Eaton wrote: Hello, I found that the distribution at this URL http://haskell.org/ghc/dist/6.6.1/ghc-6.6.1-x86_64-unknown-linux.tar.bz2 failed to install. There were lots of no such file or directory errors during 'cp' invocations I think. The i386 version sems to work fine. Hope this isn't a mistake on my part. I found the opposite, that the i386 version had lots of errors with 'cp' invocations. It turned out that it was my fault as I was accidentally using the i386 .tar.tbz when the machine I was using was in fact an x86-64 running in 64bit mode. So check your uname -a, is it i686 or x86_64? That said, the failure mode in this case could be friendlier and less confusing. Duncan ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs -- http://ofb.net/~frederik/ ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: binary distribution problem
On Wed, May 09, 2007 at 11:34:37PM +0100, Frederik Eaton wrote: Thanks Duncan, yes 'uname -a' shows i686. I was confused because the cpu is EM46T, I don't know why uname does not say x86_64. Yes, a better failure mode would indeed be helpful! EM64T processors support an emulation mode for legacy 32-bit programs and operating systems. If you want to take advantage of the wider data path, you will need to install a EM64T aware version of your operating system. (While in theory it would be possible for a 32-bit os to support running 64-bit binaries, you may need to install the 'amd64' version of the kernel.) Stefan ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: binary distribution problem
On Wed, May 09, 2007 at 08:38:57AM +, Duncan Coutts wrote: On Wed, 2007-05-09 at 03:42 +0100, Frederik Eaton wrote: Hello, I found that the distribution at this URL http://haskell.org/ghc/dist/6.6.1/ghc-6.6.1-x86_64-unknown-linux.tar.bz2 failed to install. There were lots of no such file or directory errors during 'cp' invocations I think. The i386 version sems to work fine. Hope this isn't a mistake on my part. I found the opposite, that the i386 version had lots of errors with 'cp' invocations. It turned out that it was my fault as I was accidentally using the i386 .tar.tbz when the machine I was using was in fact an x86-64 running in 64bit mode. So check your uname -a, is it i686 or x86_64? the 32 bit version of ghc works just fine on x86_64 if you modify it to just pass '-m32' to all the tools. it would be nice if the driver script checked uname -a and passed -m32 or -m64 as appropriate, so you can trivially compile both 32 bit and 64 binaries on the same system. by running 'setarch' beforehand. also, ghc seems to produce noticibly faster 32 bit code than 64 bit code. John -- John Meacham - ⑆repetae.net⑆john⑈ ___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
