Send hpx-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.cct.lsu.edu/mailman/listinfo/hpx-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of hpx-devel digest..."
Today's Topics:
1. Deprecating compiler toolchains (Thomas Heller)
----------------------------------------------------------------------
Message: 1
Date: Thu, 13 Aug 2015 09:25:53 +0200
From: Thomas Heller <[email protected]>
Subject: [hpx-devel] Deprecating compiler toolchains
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi all,
I would like to probe users/developers about the possibility to
deprecate compiler toolchains and drop support for those.
The toolchains I have in mind are:
- GCC 4.6.x
- Intel Compiler version 13
- Intel Compilers with GCC 4.4.x as "base"
Rationale: We see more and compile errors only happening on those
toolchains as we continue to evolve our codebase towards more usage of
C++11. The continuous adaption of more and more C++11 is significantly
simplifying and improving our codebase.
Workarounds for those compilers become necessary which are sometimes
very time consuming and may even introduce slower code paths (for
example unique_ptr vs. shared_ptr).
Are there any objections? Does anybody absolutely rely on those toolchains?
Best regards,
Thomas
--
Thomas Heller
Friedrich-Alexander-Universit?t Erlangen-N?rnberg
Department Informatik - Lehrstuhl Rechnerarchitektur
Martensstr. 3
91058 Erlangen
Tel.: 09131/85-27018
Fax: 09131/85-27912
Email: [email protected]
------------------------------
_______________________________________________
hpx-devel mailing list
[email protected]
https://mail.cct.lsu.edu/mailman/listinfo/hpx-devel
End of hpx-devel Digest, Vol 23, Issue 2
****************************************
