[hpcdev-discuss] [Open64-devel] OpenSolaris open64 port - 1st round patch review

2009-03-03 Thread Jian-Xin Lai 
ld-new is based on gnu ld and used as the ipa linker. It's only used if IPA
is enabled. Open64 always use the system ld(or system gcc) as the final
linker by default.

2009/3/3 "C. Bergstr?m" 

> >> 2) The patch comments out building ld-new.  This needs to be fixed, but
> >> what's the best way to do this on OpenSolaris only?
> >>
> >
> > So are we planning to use the native Solaris linker??
> >
> I assume the linker included is just gnu ld?  If so there's numerous
> benefits to using sun ld.  Unless there's a compelling reason not to I
> say comment it out for Solaris and use sun ld by default.
>
>
>
> ./C
> - ?? -
>
>
>
> --
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> ___
> Open64-devel mailing list
> Open64-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/open64-devel
>



-- 
Regards,
Lai Jian-Xin
-- next part --
An HTML attachment was scrubbed...
URL:

[hpcdev-discuss] [Open64-devel] OpenSolaris open64 port - 1st round patch review

2009-03-06 Thread Jian-Xin Lai 
If you do not need to enable IPA, the whole ld-new and other IPA related
stuffs ( all files in osprey/ipa ) can be ignored.

If IPA is needed, the ld-new must be migrated because the system ld does not
know WHIRL related sections at all.
The ld-new ( osprey/cygnus ) is based on gnu binutils-2.16.1. I do know if
gnu ld is compatible with the OpenSolaris ld.
But it should not be trouble because the output of ld-new will be fed into
Open64 backend. Then the Open64 driver will
call the system ld to do the final linking.

2009/3/6 Rayson Ho 

> Jian-Xin:
>
> Is there anything modified in "ld-new"?? How is it different from the
> GNU linker??
>
> I assume the object files with IPA information (WHIRL sections?) need
> special treatment... but I am hoping that we can workaround the issues
> and use the system linker to reduce maintenance effort...
>
>
> Christopher:
>
> I very quickly went through the diff, most of the changes are #defines
> for solaris. Except a few places I need to further investigate I think
> most of the code is good!
>
> I have some questions:
>
> - is the diff against the open64 src tarball or from cvs HEAD??
>
> - are you able to get HelloWorld compiled yet??
>
> Rayson
>
> P.S. talking about Google summer of Code, I still need to see what we
> want for SGE: http://wiki.gridengine.info/wiki/index.php/GSoCIdeas
>
>
>
>
> On Tue, Mar 3, 2009 at 3:07 AM, Jian-Xin Lai  wrote:
> > ld-new is based on gnu ld and used as the ipa linker. It's only used if
> IPA
> > is enabled. Open64 always use the system ld(or system gcc) as the final
> > linker by default.
> >
> > 2009/3/3 "C. Bergstr?m" 
> >>
> >> >> 2) The patch comments out building ld-new.  This needs to be fixed,
> but
> >> >> what's the best way to do this on OpenSolaris only?
> >> >>
> >> >
> >> > So are we planning to use the native Solaris linker??
> >> >
> >> I assume the linker included is just gnu ld?  If so there's numerous
> >> benefits to using sun ld.  Unless there's a compelling reason not to I
> >> say comment it out for Solaris and use sun ld by default.
> >>
> >>
> >>
> >> ./C
> >> - ?? -
> >>
> >>
> >>
> --
> >> Open Source Business Conference (OSBC), March 24-25, 2009, San
> Francisco,
> >> CA
> >> -OSBC tackles the biggest issue in open source: Open Sourcing the
> >> Enterprise
> >> -Strategies to boost innovation and cut costs with open source
> >> participation
> >> -Receive a $600 discount off the registration fee with the source code:
> >> SFAD
> >> http://p.sf.net/sfu/XcvMzF8H
> >> ___
> >> Open64-devel mailing list
> >> Open64-devel at lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/open64-devel
> >
> >
> >
> > --
> > Regards,
> > Lai Jian-Xin
> >
>



-- 
Regards,
Lai Jian-Xin
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/hpcdev-discuss/attachments/20090306/d999ed0e/attachment.html>

[hpcdev-discuss] [Open64-devel] [OSUNIX-dev] Re: Porting open64 to solaris

2009-02-22 Thread Jian-Xin Lai 
For the first problem, we can ignore it at all.
HG is used by Pathscale Compiler as the version control tool. The HG related
stuffs are not removed while we merge the Open64 with Pathscale Compiler.

2009/2/22 Christopher Bergstr?m 

> On Thu, Jan 29, 2009 at 3:04 PM, John Martin 
> wrote:
> > C. Bergstr?m wrote:
> >>
> >>
> >> I just glanced at it, but looks like Elf32_Word and friends is
> undefined..
> >>
> >> ../include/elf_stuff.h:57:23: warning: sys/cdefs.h: No such file or
> >> directory
> >>
> >> pm me if you'd like access to the env to help or look around.
> >>
> >>
> > This is in the linux include directory.  Did you create a directory for
> > Solaris (.../osprey/sunos/include/...)?
> >
> >
>
> Hi John/everyone
>
> I don't understand the question about creating osprey/sunos/include/..
> but here's my env and exactly what I'm doing..
>
> gcc -v
> Using built-in specs.
> Target: i386-pc-solaris2.11
> Configured with: ./configure --prefix=/opt/gcc/gcc-4.4
> --with-as=/usr/local/src/usr/sfw/bin/gas --with-gnu-as
> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++
> --enable-shared --with-mpfr-include=/usr/include/mpfr
> --with-gmp-include=/usr/include/gmp LDFLAGS=-lgmp
> Thread model: posix
> gcc version 4.4.0 20090130 (experimental) (GCC)
> (Can I build open64 with gcc-4.4?)
>
> open64 trunk + http://pkg.osunix.org/open64/open64-opensolaris.diff
>
> gmake 'LDFLAGS=-L/opt/gcc/gcc-4.4/lib/amd64 -R/opt/gcc/gcc-4.4/lib/amd64'
>
> Here's a strange warning and the error..
>
> 1)
> gmake -C osprey/targx8664_x8664/driver
> abort: There is no Mercurial repository here (.hg not found)!
>
> 2)
> gmake[3]: Entering directory
> `/usr/local/src/open64/osprey/targx8664_x8664/be'
> C++
>  /usr/local/src/open64/osprey/targx8664_x8664/be/../../be/be/dra_mangle.cxx
> In file included from ../../be/cg/cg.h:46,
> from ../../be/be/dra_mangle.cxx:72:
> ../../be/region/region_util.h:63:53: error: preg_list.h: No such file
> or directory
> In file included from ../../be/cg/cg.h:46,
> from ../../be/be/dra_mangle.cxx:72:
> ../../be/region/region_util.h:231: error: ISO C++ forbids declaration
> of 'PREG_LIST' with no type
> ../../be/region/region_util.h:231: error: expected ';' before '*' token
> ../../be/region/region_util.h:232: error: ISO C++ forbids declaration
> of 'PREG_LIST' with no type
> ../../be/region/region_util.h:232: error: expected ';' before '*' token
> ../../be/region/region_util.h:237: error: ISO C++ forbids declaration
> of 'PREG_LIST' with no type
> ../../be/region/region_util.h:237: error: expected ';' before '*' token
> ../../be/region/region_util.h:238: error: ISO C++ forbids declaration
> of 'PREG_LIST' with no type
> ../../be/region/region_util.h:238: error: expected ';' before '*' token
> ../../be/region/region_util.h:520: warning: 'REGION_search_preg_set'
> initialized and declared 'extern'
> ../../be/region/region_util.h:520: error: 'PREG_LIST' was not declared
> in this scope
> ../../be/region/region_util.h:520: error: expected primary-expression
> before ',' token
> ../../be/region/region_util.h:520: error: expected primary-expression
> before ')' token
> ../../be/region/region_util.h:520: error: initializer expression list
> treated as compound expression
> gmake[3]: *** [dra_mangle.o] Error 1
>
> So why isn't preg_list.h being generated... /usr/xpg4/bin is ahead of
> /usr/bin in the path...
>
> Thanks..
>
> ./C
>
>
> --
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco,
> CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the
> Enterprise
> -Strategies to boost innovation and cut costs with open source
> participation
> -Receive a $600 discount off the registration fee with the source code:
> SFAD
> http://p.sf.net/sfu/XcvMzF8H
> ___
> Open64-devel mailing list
> Open64-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/open64-devel
>



-- 
Regards,
Lai Jian-Xin
-- next part --
An HTML attachment was scrubbed...
URL: