hi, sun & shin.
Could you please give a review for the following code?
I am sorry for that I have commited the code without any review. (r3301)
The following code is just a code format for GRA embedded by TARG_SL.
Thanks very much.
--- trunk/osprey/be/cg/gra_mon/gra_color.cxx2010-08-03 05:03
hi, sun.
No one reviewed. Just do a format work.
2010/8/4 Sun Chan
> who reviewed?
> Sun
>
> On Tue, Aug 3, 2010 at 8:11 PM, wrote:
> > Author: shenruifen
> > Date: 2010-08-03 23:11:36 -0400 (Tue, 03 Aug 2010)
> > New Revision: 3301
> >
> > Modified:
> > trunk/osprey/be/cg/gra_mon/gra_color.
Yonghong Yan wrote:
concerning IA64, is the software pipeliner from SGI included in open64?
No that wasn't open sourced.
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring the
who reviewed?
Sun
On Tue, Aug 3, 2010 at 8:11 PM, wrote:
> Author: shenruifen
> Date: 2010-08-03 23:11:36 -0400 (Tue, 03 Aug 2010)
> New Revision: 3301
>
> Modified:
> trunk/osprey/be/cg/gra_mon/gra_color.cxx
> trunk/osprey/be/cg/gra_mon/gra_create.cxx
> trunk/osprey/be/cg/gra_mon/gra_gran
On Tue, 2010-08-03 at 22:27 -0700, Sun Chan wrote:
> the swp from sgi is for Mips. Much work was done by ICT and Tsinghua
> to get swp work reasonably good for IA64. I don't know of blackbird
> from Reservoir lab. Can you elaborate?
i only get this information from their website, nothing in details
the swp from sgi is for Mips. Much work was done by ICT and Tsinghua
to get swp work reasonably good for IA64. I don't know of blackbird
from Reservoir lab. Can you elaborate?
The swp from SGI was not well tuned for IA64 (I guess I am the only
one involved in this swp through all the phases and tra
for embedded execution, PIE != PIC, otherwise, they are the same, no?
For a PIE relocatable, there is no need for dynamic relocation, that
is the job of linkers. If the shared.a is not compiled with PIC (or
PIE) it is wrong. A function being reentrant happen to be able to be
PIE is an accident (i.e
The checkin will affect the use of the library. I suspect the corectness of
using libopen64rt_shared.a for PIE executable, which the checkin works.
On Wed, Aug 4, 2010 at 12:01 PM, Sun Chan wrote:
> but this is a problem with the library itself, not the checkin.
> Sun
>
> On Tue, Aug 3, 2010 at
concerning IA64, is the software pipeliner from SGI included in open64?
I know the the blackbird from Reservoir lab has it. This is the big part
of the IA64 story.
--
Yonghong Yan
DH 3051
713-348-5860
ya...@rice.edu
On Tue, 2010-08-03 at 15:03 -0700, Shin-Ming Liu wrote:
> Besides HP and Univer
but this is a problem with the library itself, not the checkin.
Sun
On Tue, Aug 3, 2010 at 8:55 PM, Peng Yuan wrote:
> If libopen64rt_shared.a can be used for executable except for shared
> library, I'll support the checkin. Not perfect, but it can work for the
> current trunk. Otherwise we must
If libopen64rt_shared.a can be used for executable except for shared
library, I'll support the checkin. Not perfect, but it can work for the
current trunk. Otherwise we must notice the PIE issue.
I just explain the PIE linking. I don't konw the function of libopen64rt.a
and libopen64rt.a. Why doe
Author: shenruifen
Date: 2010-08-03 23:11:36 -0400 (Tue, 03 Aug 2010)
New Revision: 3301
Modified:
trunk/osprey/be/cg/gra_mon/gra_color.cxx
trunk/osprey/be/cg/gra_mon/gra_create.cxx
trunk/osprey/be/cg/gra_mon/gra_grant.cxx
trunk/osprey/be/cg/gra_mon/gra_split.cxx
Log:
Format GRA code e
Forgot to mention that I am not 100% sure if the ELF ABI is the same for
FreeBSD & Linux on IA64. So please find IA64 FreeBSD & IA64 Linux machines and
do the experiment.
Rayson
--- On Tue, 8/3/10, Rayson Ho wrote:
> a) gcc -c hello.c (on Linux)
> b) gcc hello.o (on Solaris, and in your case,
Hi Anton,
1) There is also an uncommitted Open64 port for Solaris & OpenSolaris, and I
believe most of the changes for FreeBSD would be very similar to the Solaris
port.
As an x86/x64 ELF object on Linux should be idential to the ELF object on
Solaris/OpenSolaris, I strongly believe that if yo
you answered my question.
Pls go ahead with the checkin
Sun
On Wed, Aug 4, 2010 at 7:04 AM, Steve Ellcey wrote:
> On Wed, 2010-08-04 at 06:52 +0800, Sun Chan wrote:
>> I suppose the same problem will occur for open64 internal flag -shared
>> sun
>
> I am not sure what you mean by the 'internal fl
On Wed, 2010-08-04 at 06:52 +0800, Sun Chan wrote:
> I suppose the same problem will occur for open64 internal flag -shared
> sun
I am not sure what you mean by the 'internal flag -shared'? Is that
something different than the user visible -shared flag used to create a
shared library? If you bui
I suppose the same problem will occur for open64 internal flag -shared
sun
On Wed, Aug 4, 2010 at 6:48 AM, Steve Ellcey wrote:
> This patch is my proposed fix for bug 577, The problem is that when
> linking a program using the -pie (-fPIE, -fpie) option to create a
> position independent executa
This patch is my proposed fix for bug 577, The problem is that when
linking a program using the -pie (-fPIE, -fpie) option to create a
position independent executable we link in libopen64rt.a which contains
non-PIC code and this causes us to get a link-time error.
My fix is to link in libopen64rt
And they have worked on ia64 + open64 extensively too
Sun
On Wed, Aug 4, 2010 at 6:03 AM, Shin-Ming Liu wrote:
> Besides HP and University of Houston, Tsinghua University in Beijing is very
> active in OpenMP development.
> - Shin
> On Tue, Aug 3, 2010 at 3:52 AM, Anton Shterenlikht
> wrote:
>>
Besides HP and University of Houston, Tsinghua University in Beijing is very
active in OpenMP development.
- Shin
On Tue, Aug 3, 2010 at 3:52 AM, Anton Shterenlikht wrote:
> Hi
>
> I'm a lecturer in Solid Mechanics with Mech
> Eng Dept at University of Bristol, UK.
> My research interests are in
Oh, U of Houston is another good partner choice. Extensive work on
openMP and open64
Sun
On Tue, Aug 3, 2010 at 9:47 PM, Sun Chan wrote:
> as far as I know, HP compiler team should be your natural partner.
> That team has extensive experience in ia64, and is the official
> compiler team inside HP
as far as I know, HP compiler team should be your natural partner.
That team has extensive experience in ia64, and is the official
compiler team inside HP for ia64 linux, I think. Tuning for ia64 needs
a lot of know how with the microarchitecture (having been part of the
ia64 compiler at Intel for
Hi
I'm a lecturer in Solid Mechanics with Mech
Eng Dept at University of Bristol, UK.
My research interests are in computational
mechanics.
I'm preparing a proposal to EPSRC (Engineering
and Physical Sciences Research Council - a major
UK government funding body for engineering,
including compute
23 matches
Mail list logo
