I'm gonna start reading through the spectre paper in a few minutes but...
is this really the death knell for speculative execution on x86/64...? If
so, GHC getting patched is going to be pretty low on everyone's list of
priorities.
On Jan 4, 2018 6:36 AM, "Carter Schonwald"
wrote:
> The only imp
31 AM, Thomas Jakway wrote:
I'm on Ubuntu 16.10.
I ran git bisect:
--
e515c7f37be97e1c2ccc497ddd0a730e63ddfa82 is the first bad commit
commit e515c7f37be97e1c2ccc497ddd0a730e63ddfa82
Author: Moritz Angermann
Date: Sat Sep 30 09:31:12 2017 -0400
Allow libffi snapshot
PM, Ben Gamari wrote:
Thomas Jakway writes:
Anyone else getting linker errors?
This is after running
make clean && make distclean && find . -name "*.o" -type f -delete &&
find . -name "*.hi" -type f -delete
then
./boot && ./configure &&
Build flavor is devel2, of course.
On 10/03/2017 04:42 PM, Ben Gamari wrote:
Can you confirm which commit you are on?
On October 3, 2017 4:36:48 PM EDT, Thomas Jakway wrote:
Not sure. I ran `git submodule update --init --recursive` and git
status says everything's up to date.
Hm, so it's definitely not anything I changed. I just cloned and built
it and got the same problem (7109fa8157f3258912c947f28dab7617b5e5d281).
On 10/03/2017 04:42 PM, Ben Gamari wrote:
Can you confirm which commit you are on?
On October 3, 2017 4:36:48 PM EDT, Thomas Jakway wrote:
hich I did) or if
you're missing some newly required dependency.
John
On Tue, Oct 3, 2017 at 10:55 AM, Thomas Jakway <mailto:tjak...@nyu.edu>> wrote:
Anyone else getting linker errors?
/home/thomas/git/ghc-new/libraries/ghci/dist-install/build/libHSghci-8.3-ghc8.3
Anyone else getting linker errors?
/home/thomas/git/ghc-new/libraries/ghci/dist-install/build/libHSghci-8.3-ghc8.3.
20171003.so: error: undefined reference to 'ffi_type_uint64'
chmod +x inplace/bin/runghc
/home/thomas/git/ghc-new/libraries/ghci/dist-install/build/libHSghci-8.3-ghc8.3.
20171003.so
woops, meant to reply list
On 04/12/2017 11:29 AM, Thomas Jakway wrote:
This would go great with https://ghc.haskell.org/trac/ghc/ticket/13051
(which I have not abandoned by the way!)
On 04/12/2017 11:25 AM, Simon Peyton Jones via ghc-devs wrote:
Luke
Kavon Farvardin is here as an
If anyone has a free moment I'd appreciate feedback on D2903:
https://phabricator.haskell.org/D2903
-Thomas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Thanks very much, I'll give that a shot.
On 01/09/2017 08:12 AM, Simon Marlow wrote:
On 9 January 2017 at 04:51, Ben Gamari <mailto:b...@smart-cactus.org>> wrote:
Thomas Jakway mailto:tjak...@nyu.edu>> writes:
> I want to be able to load certain GHC modules
x27;t possible how would I get ghci to load
all of GHC in interpreted mode (intead of using -package ghc)?
Currently I'm using trace & friends to do printf-style debugging but
it's definitely not ideal.
-Thomas Jakway
__
out of
date and doesn't mention the NCG specifically. If anyone here familiar
with the backend would care to take a look I would very much appreciate it.
Thanks,
Thomas Jakway
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cg
ttps://github.com/ghc/ghc/blob/master/testsuite/tests/
> unboxedsums/unboxedsums_unit_tests.hs
> for an example.
>
> 2016-10-11 17:50 GMT-04:00 Thomas Jakway :
>
>> I read somewhere that fixing the graph register allocator would be a good
>> project so I thought I'd look
ng else and it'd be a good way to get my feet wet.
On 10/11/2016 02:13 PM, Ben Gamari wrote:
Thomas Jakway writes:
Can anyone point me to the register allocator tests (especially for the
graph register allocator)? Can't seem to find them and grepping doesn't
turn up much (pret
Can anyone point me to the register allocator tests (especially for the
graph register allocator)? Can't seem to find them and grepping doesn't
turn up much (pretty much just
testsuite/tests/codeGen/should_run/cgrun028.h).
___
ghc-devs mailing list
OK, makes sense, thanks.
On 10/09/2016 02:14 PM, Ben Gamari wrote:
Hi Thomas!
Thomas Jakway writes:
I was looking through compiler/nativeGen/X86/Instr.hs
<https://github.com/ghc/ghc/blob/master/compiler/nativeGen/X86/Instr.hs#L71>
and it's pretty hard not to notice the (hilariou
efore?
According to the comment there seems to be room for improvement. Sadly I
don't think x87 is going away any time soon.
-Thomas Jakway
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
of
these subtasks, writing a bytecode assembler, porting the RTS, etc.
could consume the whole summer if you're not careful.
I'd love to help out with this project!
Sincerely,
Thomas Jakway
---
Woops, after scrolling back through the emails it looks like someone
sent out the L
18 matches
Mail list logo