Simon Marlow wrote:
Here's a patch review.
Oh there is one other issue I keep forgetting about. LLVM requires that
all basic blocks end in a control flow statement. Cmm basic blocks have
this property for everything except the hand written cmm.
e.g rts/Apply.cmm has the code:
INFO_TABLE(
Simon Marlow wrote:
In fact, I'm surprised at how much there is here. The LLVM backend has
more in common with the native code generators than the C backend, but I
was expecting something closer to a straightforward pretty-printer. I
wonder if having a complete datatype for LLVM is really buying
Simon Marlow:
> On 22/02/2010 16:49, Simon Marlow wrote:
>> On 22/02/2010 12:34, Simon Marlow wrote:
>>
>>> I'm currently running some benchmarks to see how much impact turning off
>>> TNTC has on the -fasm backend.
>>
>> Here are the results on x86-64/Linux:
> [ snip ]
>> ---
Simon Marlow wrote:
> So, nofib programs are on average 4-5% slower, with a 6% increase in
> binary sizes (this is with -split-objs).
>
> What's interesting is that there are some outliers here: programs that
> go 12-17% slower without TNTC. Looking at David's thesis the results are
> quite differ
davidterei:
> On 24 February 2010 12:38, Don Stewart wrote:
> > David,
> >
> > Did you see my patch to fix the parsing of -optlo and friends?
> >
> > http://www.galois.com/~dons/add-new-llvm-code-generator-to-ghc_.dpatch
> >
> > Order of the flags appears to matter to GetOpt.
> >
>
> Great! Th
Build description = STABLE on x86_64-unknown-linux
(cam-04-unx.europe.corp.microsoft.com)
Build location= /64playpen/simonmar/nightly/STABLE-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-04-unx
Nightly build started on cam-04-unx at Wed Feb 24 19:10:01 GMT 20
Build description = HEAD on x86_64-unknown-linux
(cam-04-unx.europe.corp.microsoft.com)
Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx
Nightly build started on cam-04-unx at Wed Feb 24 19:00:01 GMT 2010.
**
On Wed, Feb 24, 2010 at 04:26:23PM +, Simon Peyton-Jones wrote:
> | > tags is the vim equivalent of TAGS.
> |
> | Unfortunately, on a case-insensitive filesystem, such as the defaults
> | on Windows and MacOS, there is no way to have both a 'tags' and a
> | 'TAGS' file.
>
> good point. Could
Build description = STABLE on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/STABLE
Build config file = /home/simonmar/nightly/site/msrc/conf-STABLE-cam-02-unx
Nightly build started on cam-02-unx at Wed Feb 24 18:10:01 GMT 2010.
checki
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Wed Feb 24 18:00:01 GMT 2010.
checking out
On 22/02/2010 16:49, Simon Marlow wrote:
On 22/02/2010 12:34, Simon Marlow wrote:
I'm currently running some benchmarks to see how much impact turning off
TNTC has on the -fasm backend.
Here are the results on x86-64/Linux:
[ snip ]
--
good point. Could we call them 'tags-emacs' and 'tags-vim'?
Simoin
| -Original Message-
| From: cvs-ghc-boun...@haskell.org [mailto:cvs-ghc-boun...@haskell.org] On
Behalf Of
| Malcolm Wallace
| Sent: 24 February 2010 16:03
| To: cvs-ghc@haskell.org
| Subject: Re: patch applied (ghc): Ma
tags is the vim equivalent of TAGS.
Unfortunately, on a case-insensitive filesystem, such as the defaults
on Windows and MacOS, there is no way to have both a 'tags' and a
'TAGS' file.
Regards,
Malcolm
___
Cvs-ghc mailing list
Cvs-ghc@has
On Wed, Feb 24, 2010 at 03:18:25PM +, Simon Peyton-Jones wrote:
> | It should make both a tags file for vim and a TAGS file for emacs. Maybe
> | I should have called the target something else, but I'm not sure what.
>
> Ah yes so it does. Thanks. What is 'tags' for?
tags is the vim equivale
| It should make both a tags file for vim and a TAGS file for emacs. Maybe
| I should have called the target something else, but I'm not sure what.
Ah yes so it does. Thanks. What is 'tags' for?
S
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://w
On 24 February 2010 12:38, Don Stewart wrote:
> David,
>
> Did you see my patch to fix the parsing of -optlo and friends?
>
> http://www.galois.com/~dons/add-new-llvm-code-generator-to-ghc_.dpatch
>
> Order of the flags appears to matter to GetOpt.
>
Great! Thanks for that. I remember fixing t
On Wed, Feb 24, 2010 at 11:57:51AM +, Simon Peyton-Jones wrote:
> Ian
>
> | Sun Feb 21 08:44:32 PST 2010 Ian Lynagh
> | * Make "make tags" work in the new build system
>
> Thanks. This does construct a file 'tags' in $(TOP), snippet below.
>
> Alas emacs says 'not a valid tags table'.
On 22 February 2010 23:34, Simon Marlow wrote:
> I presume the calling-convention changes can be made in an acceptable way,
> by defining a new calling convention rather than modifying the exisitng C
> one? Does LLVM allow new calling conventions to be defined dynamically,
> without patchig LLVM
Ian
| Sun Feb 21 08:44:32 PST 2010 Ian Lynagh
| * Make "make tags" work in the new build system
Thanks. This does construct a file 'tags' in $(TOP), snippet below.
Alas emacs says 'not a valid tags table'.
The old TAGS file I have looks like the second snippet below.
Any ideas?
Simon
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Tue Feb 23 18:00:02 GMT 2010.
checking out
20 matches
Mail list logo
