On 1/26/2016 4:31 PM, Bernd Schmidt wrote:
On 01/27/2016 12:12 AM, David Wohlferd wrote:
I started by just commenting out the code in ix86_md_asm_adjust that
unconditionally clobbered the flags. I figured this would allow the
'normal' "cc" handling to occur. But apparently there is no 'normal'
I wanted to share a project we've been working on for sometime within
the context of Renjin,
a new interpreter for the R language running on the JVM.
We basically needed a way to compile C and Fortran code to JVM
classes, and for the last year or two we've been working on tool chain
that's compose
David Wohlferd wrote:
> On 1/26/2016 4:31 PM, Bernd Schmidt wrote:
> > On 01/27/2016 12:12 AM, David Wohlferd wrote:
> >> I started by just commenting out the code in ix86_md_asm_adjust that
> >> unconditionally clobbered the flags. I figured this would allow the
> >> 'normal' "cc" handling to occ
Hello,
I have write, open and read statements in a fortran program and compile as,
gfortran -c test.f90
and create a dll with
gfortran -shared test.dll -o test.o
I import this dll in C# with dllimport and call one of the routine. After
the call the program hangs on write(*,*) statement.
May I
On 02/01/2016 03:34 PM, Bertram, Alexander wrote:
> I wanted to share a project we've been working on for sometime within
> the context of Renjin,
> a new interpreter for the R language running on the JVM.
>
> We basically needed a way to compile C and Fortran code to JVM
> classes, and for the la
Hi,
Recently I tried to bootstrap gcc against new glibc but failed. What
I want to do is just bootstrap gcc against local version glibc other
than system one, because I can't update glibc in that system.
I tried this by configuring GCC using "--with-build-sysroot" or
"--with-sysroot" or both, but
"Bin.Cheng" writes:
> Seems to me Andrew was right in comment of PR69559, that we simply
> couldn't bootstrap GCC with sysroot.
The main use of sysroot is to build a cross compiler, which you cannot
bootstrap anyway.
> My question here is: If this is the case, how should I bootstrap a gcc
> aga
On Mon, Feb 1, 2016 at 6:08 PM, Andreas Schwab wrote:
> "Bin.Cheng" writes:
>
>> Seems to me Andrew was right in comment of PR69559, that we simply
>> couldn't bootstrap GCC with sysroot.
>
> The main use of sysroot is to build a cross compiler, which you cannot
> bootstrap anyway.
>
>> My questi
On 02/01/2016 12:07 PM, Bin.Cheng wrote:
On Mon, Feb 1, 2016 at 6:08 PM, Andreas Schwab wrote:
"Bin.Cheng" writes:
Seems to me Andrew was right in comment of PR69559, that we simply
couldn't bootstrap GCC with sysroot.
The main use of sysroot is to build a cross compiler, which you cannot
On 02/02/2016 01:58 AM, Ulrich Weigand wrote:
I think on many targets a clobber "cc" works because the backend
actually defines a register named "cc" to correspond to the flags.
Therefore the normal handling of clobbering named hard registers
catches this case as well.
Yes. C.f. Sparc ADDITION
On 01/02/16 12:34, Bertram, Alexander wrote:
I wanted to share a project we've been working on for sometime within
the context of Renjin,
a new interpreter for the R language running on the JVM.
We basically needed a way to compile C and Fortran code to JVM
classes, and for the last year or two
Thanks Mikhail and Manuel for the reactions!
Mikhail, thanks for the tip on xmalloc, will take a look if that can
help clean up the plugin code.
Manuel,
0) Yes, we hope to make it faster!
1) Initially coding within GCC would have been too intimidating, but I
think i've started to get a feel for
On 2/1/2016 6:58 AM, Ulrich Weigand wrote:
I think on many targets a clobber "cc" works because the backend
actually defines a register named "cc" to correspond to the flags.
Therefore the normal handling of clobbering named hard registers
catches this case as well.
This doesn't work on i386 bec
On 2/1/2016 12:40 PM, Richard Henderson wrote:
On 02/02/2016 01:58 AM, Ulrich Weigand wrote:
I think on many targets a clobber "cc" works because the backend
actually defines a register named "cc" to correspond to the flags.
Therefore the normal handling of clobbering named hard registers
catche
I have a question about the compatibility tests (gcc.dg/compat and
g++.dg/compat). Do they work with remote/simulator testing? I was
trying to run them with qemu and even though I am setting ALT_CC_UNDER_TEST
and ALT_CXX_UNDER_TEST it doesn't look like my alternative compiler
is ever getting run
15 matches
Mail list logo