[Open64-devel] patch for building Fortran frontend with FORTIFY_SOURCE checking

2010-11-21 Thread David Coakley
Recently I tried to build Open64 with gcc-4.5.1 and FORTIFY_SOURCE checking turned on. The Fortran frontend would not run at all because of a failing buffer overflow check that occurred during command-line processing. Although this failure turned out to be a false alarm, it was fairly easy to wor

[Open64-devel] r3406 - trunk/osprey/driver

2010-11-21 Thread svn
Author: dcoakley Date: 2010-11-22 02:08:09 -0500 (Mon, 22 Nov 2010) New Revision: 3406 Modified: trunk/osprey/driver/phases.c Log: Do not add linker rpath options when building the compiler's libraries. The rpath option is used to provide a default location for the compiler's shared libraries.

[Open64-devel] r3405 - trunk/osprey/be/cg

2010-11-21 Thread svn
Author: zhuqing Date: 2010-11-21 22:48:38 -0500 (Sun, 21 Nov 2010) New Revision: 3405 Modified: trunk/osprey/be/cg/cgemit.cxx Log: Fix "missing .setion bss" bug in cgemit when size is zero Test case: struct line { char a[0];}; static struct line line3; static struct line line4; static const ch

Re: [Open64-devel] review request for missing .setion .bss in cgemit

2010-11-21 Thread Gang Yu
Yes, it is now. Since the case is rarely seen in the app code, we'll re-evaluate to avoid the path, thx! Gang On Fri, Nov 19, 2010 at 10:48 PM, Chandrasekhar Murthy wrote: > Is the struct size 0 for the SL case too. > > Murthy > > -Original Message- > From: Sun Chan [mailto:sun.c...@gmai