Displaying 4 results from an estimated 4 matches for "_main__".
Did you mean:
__main__
2013 May 11
0
[LLVMdev] gcc 4.8.x dragonegg support
...as...
>
> % /sw/lib/gcc4.8/bin/gfortran -fplugin=/sw/lib/gcc4.8/lib/dragonegg.so -specs=/sw/lib/gcc4.8/lib/integrated-as.specs -O1 rnflow.f90 -o rnflow
> Undefined symbols for architecture x86_64:
> "_iroundf", referenced from:
> _cmpmat_ in ccaC6IRb.o
> _MAIN__ in ccaC6IRb.o
> ld: symbol(s) not found for architecture x86_64
> collect2: error: ld returned 1 exit status
>
> Jack
>
>>
>> Part of that patch has already been applied. I gather that Duncan
>> has been busy with conference organisation so it may take so...
2013 May 09
4
[LLVMdev] gcc 4.8.x dragonegg support
...d 1 exit status
and the second as...
% /sw/lib/gcc4.8/bin/gfortran -fplugin=/sw/lib/gcc4.8/lib/dragonegg.so -specs=/sw/lib/gcc4.8/lib/integrated-as.specs -O1 rnflow.f90 -o rnflow
Undefined symbols for architecture x86_64:
"_iroundf", referenced from:
_cmpmat_ in ccaC6IRb.o
_MAIN__ in ccaC6IRb.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status
Jack
>
> Part of that patch has already been applied. I gather that Duncan
> has been busy with conference organisation so it may take some time
> for him to review the...
2013 May 08
0
[LLVMdev] gcc 4.8.x dragonegg support
On Wed, May 08, 2013 at 09:25:55AM -0400, Jack Howarth wrote:
> Duncan,
> I was wondering if you plan on supporting the build of dragonegg under gcc 4.8.1svn
> for the llvm 3.3 release? Is the deprecation and poisoning of IDENT_ASM_OP too problematic
> to work around without some additional substitute being added in FSF gcc upstream?
Hi Jack,
There's a patch under review to
2013 May 08
3
[LLVMdev] gcc 4.8.x dragonegg support
Duncan,
I was wondering if you plan on supporting the build of dragonegg under gcc 4.8.1svn
for the llvm 3.3 release? Is the deprecation and poisoning of IDENT_ASM_OP too problematic
to work around without some additional substitute being added in FSF gcc upstream?
Jack