Mailman 3 December 2018 - pypy-dev

save the date: PyPy Sprint in Düsseldorf February 4-9, 2019
by Carl Friedrich Bolz-Tereick 26 Jan '19

26 Jan '19

Hi all, I'll do a more proper sprint announcement soon, but to give some advance warning, I am organizing a PyPy sprint at the Heinrich-Heine-Universität Düsseldorf from February 4-9, 2019 (both days inclusive). The last sprint we had there was in 2010 :-). Cheers, Carl Friedrich

3 3

Review for blog post
by Antonio Cuni 04 Jan '19

04 Jan '19

Hi, better to ask it here since I suspect that most people won't be much on irc during the next days: I wrote a blog post draft about the gc-disable branch which I have recently merged; it is available on extradoc: https://bitbucket.org/pypy/extradoc/src/extradoc/blog/draft/2018-12-gc-disa… Reviews, comments and remarks are welcome. I think I'd like to publish it after Christmas. ciao, Anto

4 4

PyPy Winter Sprint
by andy l 29 Dec '18

29 Dec '18

Would the winter sprint be suitable for a beginner to attend? I previously submitted a couple of bug fixes and would like to work towards making a larger contribution. Cheers, Andrew Lawrence

2 3

Call for Abstracts: Modern Language Runtimes, Ecosystems, and VMs (MoreVMs) 2019
by Edd Barrett 11 Dec '18

11 Dec '18

============================================================================ Call for Extended Abstracts: MoreVMs'19 3rd Workshop on Modern Language Runtimes, and Ecosystems Co-located with <Programming>'19 April 1st or 2nd, 2019, Genova, Italy https://2019.programming-conference.org/track/MoreVMs-2019 ============================================================================ Following two previous successful editions, the MoreVMs'19 workshop aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. This includes aspects such as reuse of language runtimes, modular implementation, language design and compilation strategies. By bringing together both researchers and practitioners, the workshop aims to enable a diverse discussion on how languages and runtimes are currently being utilized, and where they need to improve further. Relevant topics include, but are definitely not limited to, the following: - Extensible VM design (compiler- or interpreter-based VMs) - Reusable components (e.g. interpreters, garbage collectors, ...) - Static and dynamic compilation techniques - Techniques for targeting high-level languages such as JavaScript - Interoperability between languages - Tooling support (e.g. debugging, profiling, etc.) - Programming language development environments - Case studies of existing language implementation approaches - Language implementation challenges and trade-offs - Surveys and usage reports to understand usage in the wild - Ideas for more predictable performance - Ideas for how VMs could take advantage of new hardware features - Ideas for how we should build languages in the future Workshop Format and Submissions ------------------------------- We welcome presentation proposals in the form of extended abstracts (1 to 2 pages long) discussing experiences, work-in-progress, as well as future visions, from either an academic or industrial perspective. The extended abstracts, and if the speakers wish, their slides, will be published on the workshop's web site. Alternatively, the abstracts can be published as part of the companion of <Programming>'19 in the ACM DL. Publication in the ACM DL is conditional on the acceptance by the program committee. Please note that MoreVMs'19 is organized as an academic workshop, and as such, speakers will be required to register for the workshop. Author Instructions ------------------- Submissions should use the ACM Conference 'acmart' Format with the 'sigconf' option and with a font size of 9 point and the font family Libertine/Biolinum. All submissions should be in PDF format. If you use LaTeX or Word, please use the provided ACM acmart templates. Otherwise, please follow the ACM author instructions. If you are formatting your paper using Word, you may wish to use the provided Word template that supports this font size. Please include page numbers in your submission for review using the LaTeX command '\settopmatter{printfolios=true}' (see examples in template). Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. Submission Site: https://easychair.org/conferences/?conf=morevms19 Important Dates --------------- Extended abstract submissions: 2019-01-11 Author notification: 2019-02-10 Camera Ready: 2019-02-22 Workshop: 2019-04-01 or 2019-04-02 All deadlines are Anywhere on Earth (AoE), i.e. GMT/UTC-12:00 hour. Program Committee ----------------- Nicolas B. Pierron, Mozilla, France Walter Binder, University of Lugano, Switzerland Eduard-Mihai Burtescu, Lyken Software Solutions Vyacheslav Egorov, Google, Denmark Tony Hosking, Australian National University / Data61, Australia Christoph Kirsch, University of Salzburg, Austria Lun Liu, University of California at Los Angeles, USA Fabio Niephaus, Hasso Plattner Institute, Germany Luís Pina, George Mason University, USA Manuel Rigger, Johannes Kepler University Linz, Austria Jennifer B. Sartor, Ghent University, Belgium Andy Wingo, Igalia, S.L., France Organizers ---------- Edd Barrett, King's College London, UK Stefan Marr, University of Kent, UK Adam Welc, Uber Technologies, USA

1 0

Running a JIT in a Python interpreter
by Timothy Baldridge 07 Dec '18

07 Dec '18

I'm debugging a JIT that's aborting during tracing for some strange reason. I remember several years ago someone here pointed me to a file in the code repo that showed how to run a RPython JIT in interpreted mode, so you can place a breakpoint in the jit hooks. I remember this being a great help last time I had this problem. Does anyone remember where that code is? Thanks! Timothy

2 2

no list() support for <RangeRepr *>
by Timothy Baldridge 04 Dec '18

04 Dec '18

I have the following code in my interpreter, and I'm getting an error message I haven't seen before: @specialize.call_location() def assoc(self, *kws): new_dict = {} shape = self.get_shape() for k in shape.attr_list(): new_dict[k] = shape.getter_for(k).get_value(self) for idx in unrolling_iterable(range(0, len(kws), 2)): new_dict[kws[idx]] = kws[idx + 1] return DictStruct(new_dict) It's not efficient, but it's fairly simple, we allow for something like struct.assoc(k, v, k2, v2). Specialized by call location, so I assume the *kws size is known. The unrolling_iterable should then give us constant lookup on the input tuple. However I get this error during translation: [translation:ERROR] TyperError: no list() support for <RangeRepr * GcStruct range { start, stop }> .. (rpython.rlib.unroll:27)unrolling_iterable.__init__ .. block@6[self_0...] with 1 exits .. v134 = simple_call((type list), iterable_0) [translation] start debugger... > /home/tbaldrid/oss/pypy/rpython/rtyper/rmodel.py(176)rtype_bltn_list() -> raise TyperError('no list() support for %r' % self) I've never seen this error before...what should I be doing differently? Thanks! Timothy Baldridge

2 1