Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

2016-10-18 Thread Ludovic Courtès
Hi Shea, Shea Levy skribis: > Unlike the traditional approach of installing system libraries into one > central location like /usr/{lib,include}, the nix package manager [1] > installs each package into it's own prefix > (e.g. /nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev). Moreover,

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

2016-10-18 Thread Shea Levy
Hey Ludo’, Amazing, more than a decade of close working with these tools and I never knew about C_INCLUDE_PATH et al! It looks like those will solve a huge portion of the problem. Will look at your gcc and clang patches as well, thank you! ~Shea Ludovic Courtès writes: > Hi Shea, > > Shea Lev

C++17 std::launder and aliasing

2016-10-18 Thread Jakub Jelinek
Hi! http://wg21.link/p0137 adds std::launder which is supposed to be some kind of aliasing optimization barrier. What is unclear to me is if we really need compiler support for that. I have unfortunately not found many examples: http://stackoverflow.com/questions/39382501/what-is-the-purpose-of-

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

2016-10-18 Thread Shea Levy
Hi Ludo’, Your patches look good! My biggest concern is how the ld wrapper behaves in the presence of response files. Have you tested that? Thanks, Shea Ludovic Courtès writes: > Hi Shea, > > Shea Levy skribis: > >> Unlike the traditional approach of installing system libraries into one >> cen

Re: C++17 std::launder and aliasing

2016-10-18 Thread Richard Biener
On Tue, Oct 18, 2016 at 1:06 PM, Jakub Jelinek wrote: > Hi! > > http://wg21.link/p0137 > adds std::launder which is supposed to be some kind of aliasing optimization > barrier. > > What is unclear to me is if we really need compiler support for that. > I have unfortunately not found many examples:

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

2016-10-18 Thread Ludovic Courtès
Hi! Shea Levy skribis: > Your patches look good! My biggest concern is how the ld wrapper behaves > in the presence of response files. Have you tested that? It surely doesn’t (yet?). However, GCC does not pass “@file” arguments when it invokes ‘ld’, and the bug report you mentioned¹ talks abou

Re: [cfe-dev] [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

2016-10-18 Thread Nathan Froyd
On Tue, Oct 18, 2016 at 8:59 AM, Ludovic Courtès via cfe-dev wrote: > Shea Levy skribis: > >> Your patches look good! My biggest concern is how the ld wrapper behaves >> in the presence of response files. Have you tested that? > > It surely doesn’t (yet?). > > However, GCC does not pass “@file” a

Re: Clear basic block flags before using BB_VISITED for OpenACC loops processing

2016-10-18 Thread Thomas Schwinge
Hi! On Mon, 17 Oct 2016 15:38:50 +0200, I wrote: > On Mon, 17 Oct 2016 14:08:44 +0200, Richard Biener > wrote: > > On Mon, Oct 17, 2016 at 1:47 PM, Thomas Schwinge > > wrote: > > > On Mon, 17 Oct 2016 13:22:17 +0200, Richard Biener > > > wrote: > > >> On Mon, Oct 17, 2016 at 11:38 AM, Thomas

gcc-5-20161018 is now available

2016-10-18 Thread gccadmin
Snapshot gcc-5-20161018 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/5-20161018/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 5 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5