Re: GCC 4.01 RC1 Available

2005-06-11 Thread Richard Sandiford
Mark Mitchell <[EMAIL PROTECTED]> writes:
> The GCC 4.0.1 RC1 prerelease is available here:
>
>   ftp://gcc.gnu.org/pub/gcc/prerelease-4.0.1-20050607/

Some mips-elf results:

   http://gcc.gnu.org/ml/gcc-testresults/2005-06/msg00692.html

which are the same as for 4.0.0.

Richard


Re: Problems with collect2 on hpux

2005-06-11 Thread John David Anglin
> The strange behaviour I'm seeing is that if I link my shared libraries 
> with -Wl,+s, then some of them work fine and find all of their libraries 
> based on the SHLIB_PATH settings.  However, some of my libraries find 
> everything *except* libstdc++.sl from the SHLIB_PATH  - these libraries 
> only load if I put libstdc++.sl in the exact same location it was in when 
> I built the library in the first place. 

The fundamental problem is the HP linker hardcodes paths into binaries.
This affects the way libtool does links and to a lesser extent the
prefix processing used by GCC.  When using the SOM linker, GCC always
strips dotdots from paths.  The downside of this is it causes problems
moving GCC after installation.

> My suspicion is that when collect2 relinks things it's not using the +s 
> flag, and that is causing the behaviour I'm seeing...

As far as I'm aware, collect2 doesn't strip linker options.  You can
see more details about the link process using -Wl,-debug and -Wl,-v.

The chatr program can show and change the dynamic path search.  It
also shows the library list.  If recall correctly, libraries linked
using -l have their full path hardcoded.  For example,

-bash-2.05b$ chatr libstdc++.sl
libstdc++.sl:
 shared library
 shared library dynamic path search:
 SHLIB_PATH disabled  second
 embedded path  enabled   first  /opt/gnu/gcc/gcc-3.4.4/lib
 internal name:
 libstdc++.sl.6
 shared library list:
 dynamic   /usr/lib/libm.2
 dynamic   /xxx/gnu/gcc-3.3/objdir/gcc/libgcc_s.sl
 dynamic   /usr/lib/libc.2

It's not very nice that the shared library list for libstdc++.sl
includes libgcc_s.sl in the GCC build directory.  I believe that the
HP dynamic loader first looks for it there.  If that doesn't work,
it strips off the basename of the library and tries the dynamic
search path.

The above is an example why executables and shared libraries need
to be relinked when installed on this target.  The problem with
libgcc_s.sl is that it isn't a "libtool" library.  As a result,
libtool doesn't know how to properly generate the dependencies for the
link used during installation (i.e., generate the correct sequence
of -L options).

Dave
-- 
J. David Anglin  [EMAIL PROTECTED]
National Research Council of Canada  (613) 990-0752 (FAX: 952-6602)


gcc-4.1-20050611 is now available

2005-06-11 Thread gccadmin
Snapshot gcc-4.1-20050611 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20050611/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 4.1 CVS branch
with the following options:  -D2005-06-11 17:43 UTC

You'll find:

gcc-4.1-20050611.tar.bz2  Complete GCC (includes all of below)

gcc-core-4.1-20050611.tar.bz2 C front end and core compiler

gcc-ada-4.1-20050611.tar.bz2  Ada front end and runtime

gcc-fortran-4.1-20050611.tar.bz2  Fortran front end and runtime

gcc-g++-4.1-20050611.tar.bz2  C++ front end and runtime

gcc-java-4.1-20050611.tar.bz2 Java front end and runtime

gcc-objc-4.1-20050611.tar.bz2 Objective-C front end and runtime

gcc-testsuite-4.1-20050611.tar.bz2The GCC testsuite

Diffs from 4.1-20050604 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-4.1
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.


Help ! Memory allocating problems

2005-06-11 Thread Virender Kashyap

Hi,
   I am working on a small implementation in gcc-code. I declare some
data structures, using GTY(()) tag ..and allocate elements using 
ggc_alloc_cleared function.

To free data, i use ggc_free function.
  The problem is that many a times i get strange memory allocation 
segfaults in xcalloc/xmalloc. In case i don't free any allocated memory, 
things work fine most of the times.
  What could be the problem above. Also what is the correct method 
of allocating and dealloction of data/arrays in gcc ?
 Please help as i am already bugged by these errors :(, and this 
is urgent for my project.


Thanks and Regards,
Virender