[Haskell] Third call for draft papers for IFL 2020 (Implementation and Application of Functional Languages)
Hello, Please, find below the third call for draft papers for IFL 2020. Please forward these to anyone you think may be interested. Apologies for any duplicates you may receive. best regards, Jurriaan Hage Publicity Chair of IFL IFL 2020 32nd Symposium on Implementation and Application of Functional Languages venue: online 2nd - 4th September 2020 https://www.cs.kent.ac.uk/events/2020/ifl20/ ### Scope The goal of the IFL symposia is to bring together researchers actively engaged in the implementation and application of functional and function-based programming languages. IFL 2020 will be a venue for researchers to present and discuss new ideas and concepts, work in progress, and publication-ripe results related to the implementation and application of functional languages and function-based programming. Topics of interest to IFL include, but are not limited to: - language concepts - type systems, type checking, type inferencing - compilation techniques - staged compilation - run-time function specialisation - run-time code generation - partial evaluation - (abstract) interpretation - meta-programming - generic programming - automatic program generation - array processing - concurrent/parallel programming - concurrent/parallel program execution - embedded systems - web applications - (embedded) domain specific languages - security - novel memory management techniques - run-time profiling performance measurements - debugging and tracing - virtual/abstract machine architectures - validation, verification of functional programs - tools and programming techniques - (industrial) applications ### Post-symposium peer-review Following IFL tradition, IFL 2020 will use a post-symposium review process to produce the formal proceedings. Before the symposium authors submit draft papers. These draft papers will be screened by the program chair to make sure that they are within the scope of IFL. The draft papers will be made available to all participants at the symposium. Each draft paper is presented by one of the authors at the symposium. After the symposium every presenter is invited to submit a full paper, incorporating feedback from discussions at the symposium. Work submitted to IFL may not be simultaneously submitted to other venues; submissions must adhere to ACM SIGPLAN's republication policy. The program committee will evaluate these submissions according to their correctness, novelty, originality, relevance, significance, and clarity, and will thereby determine whether the paper is accepted or rejected for the formal proceedings. We plan to publish these proceedings in the International Conference Proceedings Series of the ACM Digital Library, as in previous years. ### Important dates Submission deadline of draft papers: 17 August 2020 Notification of acceptance for presentation: 19 August 2020 Registration deadline: 31 August 2020 IFL Symposium: 2-4 September 2020 Submission of papers for proceedings: 7 December 2020 Notification of acceptance:3 February 2021 Camera-ready version: 15 March 2021 ### Submission details All contributions must be written in English. Papers must use the ACM two columns conference format, which can be found at: http://www.acm.org/publications/proceedings-template ### Peter Landin Prize The Peter Landin Prize is awarded to the best paper presented at the symposium every year. The honoured article is selected by the program committee based on the submissions received for the formal review process. The prize carries a cash award equivalent to 150 Euros. ### Programme committee Kenichi Asai, Ochanomizu University, Japan Olaf Chitil, University of Kent, United Kingdom (chair) Martin Erwig, Oregon State University,United States Daniel Horpacsi, Eotvos Lorand University, Hungary Zhenjiang Hu, Peking University, China Hans-Wolfgang Loidl, Heriot-Watt University, United Kingdom Neil Mitchell, Facebook, UK Marco T. Morazan, Seton Hall University, United States Rinus Plasmeijer, Radboud University, Netherlands Colin Runciman, University of York, United Kingdom Mary Sheeran, Chalmers University of Technology, Sweden Josep Silva, Universitat Politecnica de Valencia, Spain Jurrien Stutterheim, Standard Chartered, Singapore Josef Svenningsson, Facebook, UK Peter Thiemann, University of Freiburg, Germany Kanae Tsushima, National Institute of Informatics, Japan. Marcos Viera, Universidad de la Republica, Montevideo, Uruguay Janis Voigtlander, University of Duisburg-Essen, Germany ### Virtual symposium Because of the Covid-19 pandemic, this year IFL 2020
Re: Linking completely statically
I was able to get static linking working recently using docker alpine images and ghcup to install GHC based on the musl library. The details are in my Stan fork [1]. This borrowed heavily from ShellCheck's static linking release system except it uses cabal v2-build instead of v1. [1] Script: https://github.com/TomMD/stan/blob/feature/basic-json-output/mkRelease.sh Dockerfile: https://github.com/TomMD/stan/blob/feature/basic-json-output/Dockerfile On Sun, Aug 9, 2020 at 5:51 AM Volker Wysk wrote: > Hi! > > I know of the command line argument "-static". But this only affects > the Haskell libraries. I want to link some programs completely > statically, no external libraries needed. > > When just linking with "-static" I still have those dynamically linked > things: > > desktop ~/bin $ ldd sicherung > linux-vdso.so.1 (0x7ffdab53f000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 > (0x7f3633da) > librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 > (0x7f3633d95000) > libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 > (0x7f3633d9) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 > (0x7f3633d8a000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x7f3633d67000) > libgmp.so.10 => /lib/x86_64-linux-gnu/libgmp.so.10 > (0x7f3633ce3000) > libatomic.so.1 => /lib/x86_64-linux-gnu/libatomic.so.1 > (0x7f3633cd7000) > libffi.so.7 => /lib/x86_64-linux-gnu/libffi.so.7 > (0x7f3633ccb000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 > (0x7f3633ad9000) > /lib64/ld-linux-x86-64.so.2 (0x7f3633f0c000) > > > Is it possible to link the remaining libraries statically too? > > Regards, > Volker > ___ > Glasgow-haskell-users mailing list > Glasgow-haskell-users@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users > ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
Re: Linking completely statically
Hi Volker, You may also want to check out ghc-musl project https://github.com/utdemir/ghc-musl which provides compiled docker images to build atatic executables for various ghc versions. Cheers, -- aycan > On Aug 11, 2020, at 5:59 AM, Volker Wysk wrote: > > Am Dienstag, den 11.08.2020, 10:26 +0200 schrieb Herrmann, Andreas: >> Hi Volker, > > Hi! > >>> Is it possible to link the remaining libraries statically too? >> >> Yes, it is possible to generate fully statically linked Haskell >> binaries. Though it requires a bit of setup. For example the GNU C >> library glibc is not really intended for fully static linking, but >> you can use musl as an alternative libc instead. >> >> Probably the easiest way is to use static-haskell-nix [1]. Usage >> instructions are available in the project README. See [2] if you're >> not familiar with Nix. > > This looks complicated, even though it is the easiest way. I've tried > to build it from the git sources, as well as from the latest release, > but that failed. I'd have to look into nix, which is new to me. > > Be it as it may, it isn't that important for me right now. > > But thank you very much for your tips. Maybe I'll be going back to them > later. > > > Cheers, > Volker > >> Recently, the Haskell extension to Bazel, rules_haskell, also gained >> the ability to generate fully statically linked binaries building on >> top of Nix, see [3]. >> >> Best, Andreas >> >> [1]: https://github.com/nh2/static-haskell-nix >> [2]: https://nixos.org/ >> [3]: >> https://rules-haskell.readthedocs.io/en/latest/haskell-use-cases.html#building-fully-statically-linked-binaries > > > ___ > Glasgow-haskell-users mailing list > Glasgow-haskell-users@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
Re: Linking completely statically
Am Dienstag, den 11.08.2020, 10:26 +0200 schrieb Herrmann, Andreas: > Hi Volker, Hi! > > Is it possible to link the remaining libraries statically too? > > Yes, it is possible to generate fully statically linked Haskell > binaries. Though it requires a bit of setup. For example the GNU C > library glibc is not really intended for fully static linking, but > you can use musl as an alternative libc instead. > > Probably the easiest way is to use static-haskell-nix [1]. Usage > instructions are available in the project README. See [2] if you're > not familiar with Nix. This looks complicated, even though it is the easiest way. I've tried to build it from the git sources, as well as from the latest release, but that failed. I'd have to look into nix, which is new to me. Be it as it may, it isn't that important for me right now. But thank you very much for your tips. Maybe I'll be going back to them later. Cheers, Volker > Recently, the Haskell extension to Bazel, rules_haskell, also gained > the ability to generate fully statically linked binaries building on > top of Nix, see [3]. > > Best, Andreas > > [1]: https://github.com/nh2/static-haskell-nix > [2]: https://nixos.org/ > [3]: > https://rules-haskell.readthedocs.io/en/latest/haskell-use-cases.html#building-fully-statically-linked-binaries signature.asc Description: This is a digitally signed message part ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
Re: Linking completely statically
Hi Volker, > Is it possible to link the remaining libraries statically too? > Yes, it is possible to generate fully statically linked Haskell binaries. Though it requires a bit of setup. For example the GNU C library glibc is not really intended for fully static linking, but you can use musl as an alternative libc instead. Probably the easiest way is to use static-haskell-nix [1]. Usage instructions are available in the project README. See [2] if you're not familiar with Nix. Recently, the Haskell extension to Bazel, rules_haskell, also gained the ability to generate fully statically linked binaries building on top of Nix, see [3]. Best, Andreas [1]: https://github.com/nh2/static-haskell-nix [2]: https://nixos.org/ [3]: https://rules-haskell.readthedocs.io/en/latest/haskell-use-cases.html#building-fully-statically-linked-binaries ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
