Dear Marc,
Thanks for the prompt reply. I am not an expert here, so I probably
don't know the correct solution for gcc. We are using std=c++11 to
maximise source compatibility for any users seeking to recompile our
code on whatever compiler/toolchain they have.
As to your suggestions for po
Snapshot gcc-6-20151115 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20151115/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
See
http://arstechnica.com/information-technology/2015/11/llvm-to-get-fortran-compiler-that-targets-parallel-gpus-in-clusters/
It is not entirely clear on what they plan to do.
Use gfortran via dragonegg?
Regards
Thomas
On Mon, Nov 16, 2015 at 12:04:06AM +0100, Thomas Koenig wrote:
> See
>
> http://arstechnica.com/information-technology/2015/11/llvm-to-get-fortran-compiler-that-targets-parallel-gpus-in-clusters/
>
> It is not entirely clear on what they plan to do.
>
> Use gfortran via dragonegg?
>
The 3 DOE
On 11/9/2015 1:32 AM, Segher Boessenkool wrote:
On Sun, Nov 08, 2015 at 04:10:01PM -0800, David Wohlferd wrote:
It seems like a doc update is what is needed to close PR24414 (Old-style
asms don't clobber memory).
What is needed to close the bug is to make the compiler work properly.
The quest
Status
==
The trunk is in Stage 3 now, which means it is open for general
bugfixing.
Patches posted early enough during Stage 1 and not yet fully reviewed
may still get in early in Stage 3. Please make sure to ping them
soon enough.
Quality Data
Priority # Change f
